Acumatica data export: what records show how work was done?
A mature Acumatica tenant holds connected orders, approvals, inventory moves, service cases and project changes. Those workflow trails with outcomes are what AI buyers value. Partners note only metadata, never export or describe records, and check history length, modules, admin access and rights.
What does an Acumatica instance hold that is worth noticing?
A mature Acumatica tenant holds years of sales orders, purchase orders, approvals, inventory movements, project records and service cases in one connected database. For a referral partner, the point is not the software but the shape of the history: orders that move through approval, change, fulfillment and invoicing leave a trail of decisions with outcomes.
This page gives ERP consultants and CFOs a metadata-level view. It does not describe exporting anything, and partners never handle the records themselves.
Which Acumatica records show how work was done?
| Area | Typical records | Why AI buyers may value it |
|---|---|---|
| Distribution | Sales orders, shipments, backorders, returns, pricing overrides | Multi-step order workflows with exceptions and resolutions |
| Purchasing | Requisitions, purchase orders, receipts, approval chains | Approval logic and who decided what |
| Manufacturing | Production orders, bills of material changes, scrap and rework | Process variation and outcomes |
| Field service | Service cases, appointments, parts used, warranty claims | Case handling from open to close |
| Projects | Budgets, change orders, time and expense approvals | Scope changes tied to decisions |
| Finance | Journal approvals, period-close tasks, adjustments | Controls and exception handling |
Value rises when these modules are linked, because one customer issue can be followed from quote to service case to credit memo.
How far back does the history usually go?
It goes back to go-live and any data migrated at that time, so a company on the platform for six or seven years often has six or seven years of connected transactions. Earlier history may sit in a prior ERP or in spreadsheets. The SAP Business One and Epicor Kinetic briefs describe the same question for those platforms. Ask the sponsor when the system went live and what came across.
What are the export and retention realities?
Keep this generic and confirm with the company's administrator. Retention depends on how the tenant was configured, whether archiving was enabled, and what the subscription or hosting agreement says. Before an introduction, a partner only needs to know whether someone at the company can run exports and who that person is. Never ask for the records themselves.
Related decisions come up around disposal. If the company is trimming old data, point the CFO to the pre-disposal review checklist first.
The 5-question Acumatica spot check
- How long has the tenant been live, and was history migrated in?
- Which modules are in use beyond finance: distribution, service, projects, manufacturing?
- Do approvals run in the system, or by email outside it?
- Who administers it, and can they run exports?
- Do the records mainly belong to the company, or to customers who supplied specs and pricing under confidentiality?
A yes on the first four and the right answer on the fifth puts the company in good shape to run through the company fit checker.
Which companies on Acumatica tend to fit?
Acumatica clients are often in industries SourceX favors: wholesale distribution, light manufacturing, construction, professional services and technology resellers. The wholesale distribution page covers the records that matter most there. The baseline is still 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.
What are the common pitfalls?
| Pitfall | Why it matters | What to do |
|---|---|---|
| Customer-supplied pricing or specs in orders | May be confidential to the customer | Ask counsel to review contract terms before any license |
| Personal data in contact and employee fields | De-identification and redaction rules apply | Agreed with the company before any work begins |
| Implementation partner holds admin rights | Company cannot export alone | Identify who has access now |
| Records already licensed | Exclusivity conflict | Ask early |
| Customized fields nobody documents | Slows inventory | Capture a field list in the data inventory |
The data inventory worksheet approach helps the company list systems and records. Consultants who run implementations can raise this at a post-go-live review or an upgrade.
How does an Acumatica client move from conversation to introduction?
- At a post-go-live review or upgrade planning session, you ask the five spot-check questions and hear the answers.
- If they hold, you send the owner or CFO your referral link, or submit the referral form with basic company details only.
- SourceX then runs its own qualification on size, history, data breadth and rights.
- The company's administrator and SourceX list modules and years of history in a data inventory. Nothing is exported by you.
- Price and terms are agreed, and nothing binds until the company signs.
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. The reward is paid only after the buyer pays and SourceX receives its fee; an introduction, meeting or signed agreement alone does not trigger payment, and no reward is guaranteed. It is never deducted from what the company receives. Check your own firm's rules on referral fees before registering, and see the year-end planning guide for a natural moment to raise the topic. ERP consultants can start from the ERP consultant page.
What should a consultant avoid saying?
Avoid promising that a particular module, customization or number of years will lead to a deal. SourceX qualifies each company on its own facts, and buyers decide what they want. Avoid asking the client to send screens, reports or sample records, because partners never handle confidential records. And avoid describing any export procedure as simple: the company's administrator and SourceX agree the approach during the inventory, and the company authorizes everything before delivery.
Next step
Pick one Acumatica client with six or more years of history and run the spot check above. If it holds, register as a partner and make the introduction, or have the owner apply at sourcex.si/apply. The who qualifies page lists the full baseline.
- Step 1Share your linkSend your personal link to a company you know.
- Step 2Company appliesThe company applies itself at /apply.
- Step 3Buyer selects and paysThe buyer selects and pays for the data and SourceX receives its fee.
- Step 4You get your rewardYour share of SourceX fees becomes payable.
Common questions
Does a company need to be on Acumatica for years to qualify?
There is no system-specific rule. The baseline is 50+ full-time employees at peak, several years of documented operations, rights to license and an authorized sponsor. A longer history in Acumatica or a predecessor system simply gives buyers more connected workflow evidence.
Can a partner see or export Acumatica data to check fit?
No. Partners give basic fit information only and never export, upload or describe confidential records. The company completes a data inventory with SourceX after qualification, and nothing is delivered without an executed agreement and the company's authorization.
Are customer orders in Acumatica the company's data to license?
Often partly. Orders and invoices are the company's own business records, but customer-supplied specifications, pricing agreements or confidential terms may be restricted by contract. Counsel should review customer contracts and the rights question before any license is agreed.
What if the company moved to Acumatica from another ERP?
Earlier history may sit in the old system or an archive. Archived systems can help if the data still exists and someone can export it. Ask the sponsor what was migrated and what was left behind.
Does the implementation partner own the data?
The implementation partner typically administers the system, but the records are the company's under normal arrangements. Check the services agreement. If the partner holds the only admin access, the company should arrange export capability.
Related pages
- Referral opportunities for ERP consultants
- Year-end tax planning meeting checklist, and when to raise a possible data license
- Wholesale distribution companies: which operating records can be licensed
- Records disposal checklist: what to review before deleting old company records
- Epicor Kinetic historical data: what manufacturing records matter?
- SAP Business One: which records show how a company works?
Free resources
- Cash flow calculator — A 12-month cash forecast with shortfalls highlighted.
- Referral earnings calculator — Hypothetical partner earnings with the per-company cap.
- Cash conversion cycle calculator — DIO, DSO, DPO and the cash conversion cycle.
- All free tools · MCP resource center
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