ERP discovery questionnaire: questions that reveal data history

An ERP discovery questionnaire should cover entities, go-live year, legacy systems, migration scope, archive and export plans, and approvals. This copy-ready template covers all of that and adds two closing questions that show whether the client's records could suit a SourceX data licensing introduction.

When to use this ERP discovery questionnaire

Use it in the first discovery call or the pre-kickoff survey of an ERP selection or implementation, and in the same sitting you will learn most of what you need to decide whether the client fits a SourceX introduction. Sections one to five are questions ERP consultants already ask. Section six adds two more that show whether the client's records could be worth a licensing review.

Copy the blocks below into your discovery template and edit the wording to match your methodology. The referral opportunities for ERP consultants page explains where an introduction fits next to your implementation work.

Section 1: Company and entities

The headcount question is the first screen. A company needs 50+ full-time employees at peak (contractors excluded) for a SourceX introduction, and the peak counts, not today's number.

Section 2: Years live and system history

Section 3: Legacy systems and integrations

If the client is moving from spreadsheets or small-business accounting software, the QuickBooks to NetSuite migration guide covers which historical data to carry across.

Section 4: Archive, retention and export plans

Section 5: Process and approvals

Section 6: Two fit questions for a SourceX introduction

These two sit at the end of discovery, framed as housekeeping about the old system.

The first tells you whether records will survive. The second surfaces red flags, since data already licensed for AI training is a reason to stop. If both answers look promising, the network opportunity finder and the who qualifies page help you decide whether to raise it.

How to read the answers

Answer you hearWhat it signalsWhat to do
Two or more ERPs over a decade, archives keptLong history with records preservedRaise the introduction after the project scope is signed
Large company, but history left behind at migrationRecords may be gone or hard to exportNote it; if an export is still possible, flag it before cutover
Operations run through email and a chat tool, not the ERPRecords live elsewhereAsk which systems hold the real workflow
Entities mostly owned by a parent or clientsRights may sit with someone elseDo not introduce until rights are clear
Under 50 full-time employees at peakBelow the baselineDo not introduce
Receiver, trustee or assignee controls assetsApprovals needed firstPause until they are involved

How to bring it up without derailing the project

Wait until scope and fees are agreed. Then say it in one breath.

Follow up once, in writing, a week or two later. If the client says no, stop. Keep it separate from implementation billing. Note that ERP resale margins and referral rewards are different instruments; ERP referral fees vs data licensing referral rewards sets out the difference. The additional revenue streams for MSPs guide also covers how to sequence it. A CRM-side counterpart is in the CRM discovery questions and a records-preservation view in the Salesforce data archiving guide.

What never to include

  • Any request to see, copy or describe actual ledger entries, customer lists or employee records for SourceX purposes.
  • Promises of payment or typed reward amounts. Say only that partners can earn a share of SourceX's fee after a deal is completed and paid, and that no reward is guaranteed.
  • Pressure to decide before cutover. The introduction should never delay a project.

Next step

Add Section 6 to your next discovery template. When a client answers yes to both, register as a partner and make the introduction, or point the owner to sourcex.si/apply with your referral link.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Buyer selects and paysThe buyer selects and pays for the data and SourceX receives its fee.
  4. Step 4You get your rewardYour share of SourceX fees becomes payable.

Common questions

How long should an ERP discovery questionnaire be?

Long enough to scope the project, short enough that the client finishes it. Most consultants split it across a kickoff call and a pre-read form. The six sections here are a starting point: entities, years live, legacy systems, archive plans, approvals and two fit questions. Trim sections that your methodology already covers elsewhere.

Why ask about legacy systems and archives during ERP discovery?

Because cutover decisions about old systems are irreversible. Whether history is migrated, summarized or abandoned affects reporting, audit access and the value of the old records. Asking early lets you plan exports before a platform license lapses, which helps the client whatever they later decide about licensing.

Do the two SourceX questions create a conflict with my client work?

They should not, if you keep the introduction separate from your project fees and disclose any reward to the client. Check your engagement letter and any rules that apply to you. Partners only introduce and share basic fit information; the client deals directly with SourceX.

Which ERP clients are worth introducing to SourceX?

US companies with 50+ full-time employees at peak (contractors excluded), several years of documented operations, rights to license the data, and an authorized sponsor such as the owner, CEO or CFO. Records spread across many systems, and long histories including archived systems, make a company stronger.

Can a client with a retired or acquired ERP still qualify?

Yes, if the data still exists. A company that is still operating, has been acquired or has wound down can qualify when the records survive and the rights are clear. If archives were deleted or nobody can export the data, it will not work.

Free resources

By SourceX Partnerships Team · Published 2026-10-09 · Updated 2026-10-09

Know a US company with valuable proprietary data?

Become a referral partner from anywhere we support, get your link and introduce an owner or authorized decision-maker.

Refer a company →

I own a business

Explore licensing your company's data to AI developers worldwide. Start a short assessment; no uploads needed.

Start an assessment