# ERP vendor selection referral opportunity | SourceX

Canonical: https://refer.sourcex.si/guides/moment-vendor-selection-erp-selection-advisors
Last updated: 2026-11-04

A clean-data migration usually carries master data and open transactions into the new ERP, and leaves behind the record of how exceptions were decided: price overrides, credit-hold releases, three-way-match variances accepted, write-offs with reason codes. During vendor selection, ask which of those operational decisions would vanish if only clean data moved. If the answer is "years of them" and the company is eligible, introduce its owner to SourceX, with the reward disclosed.

## Which operational decisions would vanish from a clean-data migration?

The ones recorded on closed transactions. A clean scope is built for the new system to run on day one, so it favors current customers, items, vendors, open orders and opening balances. The approval note on a 2020 credit memo, the reason a buyer accepted a short shipment, the override that released a held order: these sit on closed documents and are rarely mapped, because the new system does not need them to operate.

That is a sound project choice. It also means the selection advisor is the last person who sees the full landscape before the decision is made. The [software selection consultant page](/for/software-selection-consultant) explains why that early view matters; this page is about the one question to add to it.

Dated platform events make the question practical. Microsoft has announced the end of support for Dynamics GP, with security updates available until April 30, 2031. SAP lists mainstream maintenance for SAP ERP 6.0 enhancement packages 6 to 8 through the end of 2027, with optional extended maintenance until the end of 2030 at a premium. Selections driven by events like these often decide data scope early.

Legal retention is not a guide to what will be kept. The IRS generally suggests keeping records for three years and employment tax records for at least four. A company may hold ten years of exception history and be under no duty to keep most of it, which is why the decision about where it goes deserves an owner.

### The decision inventory (evidence asset)

Illustrative. A 310-person industrial distributor is choosing between two cloud ERPs. Its proposed migration scope is "clean data plus two years of closed invoices." The advisor walks the controller through five exception types and records the answers only.

| Exception decision | Where it is recorded in the legacy ERP | Carried by the clean scope? | Years held | Who can speak for it |
|---|---|---|---|---|
| Price override on a sales order | Order line with override reason code | No, closed orders excluded | 11 | Sales operations manager |
| Credit-hold release | Hold log with approver and note | No | 9 | Credit manager |
| Three-way-match variance accepted | AP variance record with approver | Two years only | 11 | Controller |
| Customer return authorized outside policy | RMA with exception flag and comment | No | 8 | Customer service lead |
| Bad-debt write-off | Journal entry with reason code and memo | Summary balances only | 11 | CFO |

Reading the inventory: roughly a decade of decisions, each with a reason and an approver, would remain only in the old system. The client now has a scope decision to make, and the owner has something concrete to consider if they want an introduction. Neither the advisor nor the client needs to extract a single record to know this. For the archiving choices themselves, see [legacy ERP data archiving](/guides/legacy-erp-data-archiving).

### Why legacy exception records get overlooked

Selection workshops ask what the business must do in future, and data workshops ask what must be converted. Exception history falls between them: not a future requirement, not a conversion requirement. The [ERP discovery questionnaire](/resources/erp-discovery-questionnaire) can carry one extra line for it.

## How do you ask about it without slowing the selection?

Ask once, at metadata level, and keep it apart from vendor scoring. The exact question is: **"Which operational decisions would vanish from a clean-data migration?"** It belongs in the data-scope conversation, which the selection already includes, so it adds minutes rather than a workstream.

If the answer points to years of exception history, four follow-ups are enough:

1. **What:** which exception types carry a reason code, note or approver (overrides, holds, variances, returns, write-offs)?
2. **How much and how long:** rough volumes per year and the earliest year held.
3. **Which system:** the legacy ERP's plain-text name, any satellite tools that hold approvals, and whether the old system stays read-only after go-live.
4. **Who owns it:** the company outright, or do customer and supplier contracts limit reuse of transaction records?

Stay there. Partners never ask for exports, reports, screenshots or logins, and the answers fit on half a page of notes. Whether the history is worth anything to anyone is a question for a SourceX review, not for the selection team.

## Reward disclosure and owner permission

Raise the licensing option with the owner, CEO or CFO, not with the project team, and disclose the reward before they answer. Then let them decide, and keep the decision out of your vendor recommendation.

A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details. Record that you said it, and the owner's answer.

If the owner opts in, the introduction is short: the exception history in plain words (types and years, from the decision inventory), the authorized contact, and a line saying no data has been shared. If the owner declines, the decision inventory still did useful work: the client now knows where its exception history goes when the old ERP is switched off.

## Does the company qualify, and who decides?

The company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.

- **Records that exist:** exception types and years from the decision inventory.
- **Who owns them:** the company, subject to contract limits the owner identifies.
- **Who can authorize:** the CEO, who in an owner-run company is usually the owner; the CFO or project sponsor can prepare the case.
- **Unknown until SourceX reviews it:** SourceX's current data needs, rights review outcome, scope, price and any reward.

Sign the Channel Partner Agreement before submitting. The first valid introduction within the 90-day window is credited when the company submits a verified application, one partner per company. The [ERP consultants page](/for/erp-consultants) and the [NetSuite project guide](/guides/how-erp-consultants-spot-referral-opportunities-during-netsuite-projects) cover later project phases; the [network opportunity finder](/tools/network-opportunity-finder) helps list clients in selection now. Payment mechanics are on [/rewards](/rewards), other roles on the [partner hub](/for).

## Go deeper on ERP vendor selection

- [Vendor selection meeting agenda](/resources/vendor-selection-meeting-agenda): a timed 15-minute owner meeting to hold after the shortlist is set and before migration scope is signed.
- [Vendor selection archive context checklist](/resources/vendor-selection-archive-context-checklist): a checklist of the scope sign-off, read-only and decommissioning dates to confirm before the migration scope is fixed.
- [Vendor selection introduction email](/resources/vendor-selection-introduction-email): an email template for introducing the owner to SourceX, with the reward disclosure written in.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If the decision inventory shows years of exception history and the owner opted in, [register as a partner](/register), check the company against [who qualifies](/who-qualifies), and read the [program terms](/terms) before the scope is signed.

## Sources

- https://refer.sourcex.si/terms
- https://www.microsoft.com/en-us/dynamics-365/blog/it-professional/2024/09/25/announcing-end-of-support-for-dynamics-gp/
- https://support.sap.com/en/offerings-programs/strategy.html
- https://www.irs.gov/businesses/small-businesses-self-employed/how-long-should-i-keep-records
