Epicor Prophet 21 data export: which distributor records can be licensed?

Which Prophet 21 records show real distributor workflow depth?

The records that matter in Epicor Prophet 21 (P21) are the ones that show a sale moving from quote to order to return, with a person's note or decision attached at each step. A distributor with years of connected quote, order, purchasing and RMA history, and someone who can still export it, is worth a closer look.

P21 is a common ERP for wholesale distribution. That makes it a useful signal for ERP consultants, controllers and PE operating teams: if the company runs P21, the system of record for how it quotes, sources, ships and handles problems is probably one database with a long history. Whether that history can be licensed depends on rights, not on the software.

This page covers the system side. For the consultant's role, see referral opportunities for ERP consultants.

What does a P21 database typically hold?

Module names and exports vary by version and configuration, so treat the table as a conversation guide rather than a spec.

Free-text notes and RMA reasons are the most distinctive items. Structured order lines are common across ERPs; a decade of counter and inside-sales notes tied to outcomes is not.

Which distributors fit, and which do not?

Screen for the company before the system. The baseline is a US business with 50+ full-time employees at peak (contractors excluded), several years of documented operations, rights to license the data and an authorized sponsor.

Good signals on a P21 distributor:

• Inside sales and purchasing teams that work from the ERP all day, so notes are rich.
• More than one data source around it: email, a CRM, a support or EDI mailbox, shared drives.
• An older instance or archived company database that was never purged.
• A leader who has been through a migration and still has the old exports.

Weak signals: a recent go-live with only a year of history, heavy use of a separate system where the real decisions live, or order notes that mainly contain customer personal details.

What rights questions come up with distributor data?

The company's own operating records are the target. Customer and supplier information needs care.

• Customer terms. Some customer agreements and supplier contracts restrict use of pricing, part numbers or program data. Someone at the company should read them before scoping.
• Individuals. Contact names, phone numbers and emails inside order notes may need to be removed or masked. Redaction rules are agreed with the company before any work begins.
• Vendor and OEM agreements. Line cards and rebate programs sometimes carry confidentiality terms.
• Third-party content. Product descriptions or images supplied by manufacturers may not be the distributor's to license.

If most of the value sits in pricing that belongs to customers or manufacturers under restrictive terms, the opportunity may shrink or fail. The sister page on which industries are a poor fit explains the pattern.

When is an upgrade or migration the moment to raise it?

Moments when the system is about to change are the strongest triggers, because records are cheapest to preserve before the old database is turned off.

Raising it at the planning stage costs nothing: the ask is simply to keep a complete export instead of trimming history. The Autotask PSA ticket history page describes the same move for an MSP.

How does the introduction work without touching the database?

You never export, upload or describe records. Your job is the introduction.

1. Ask the CFO, owner or president whether they would consider a one-time payment for an exclusive AI-training license on an agreed term.
2. Send your referral link, or submit the company through the referral form.
3. SourceX screens size, history, data breadth and rights.
4. The company completes a data inventory, listing each system, its years of history and what can be exported. The data inventory builder helps frame this.
5. Price and terms are agreed. Nothing is binding until the company signs.
6. Buyers review, and once the company is deal-ready they typically respond within about two weeks.
7. Data is delivered only after an executed agreement and the company's authorization. The company is paid, and your reward is paid after SourceX receives its fee.

What to say to a distributor's controller

Run a preliminary screen with the company fit checker, which needs no contact details.

How rewards work for ERP partners

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company. Rewards become payable only after the buyer pays and SourceX receives its fee; no reward is guaranteed, and the reward is never deducted from what the company receives. If you are an implementation partner, check your own client contracts on referral compensation and disclose the arrangement. Details are in the program terms and on the rewards page.

When not to raise it

• The company has fewer than 50 full-time employees at peak.
• The ERP was installed recently and older systems were deleted.
• The data is mostly customer personal information.
• Nobody can run a database export.

See the full who qualifies baseline.

Next step

Pick one P21 distributor in your client list, run it through the fit checker, and if it passes, register as a partner. The company can also apply directly at sourcex.si/apply through your referral link.