How to export all data from Sage X3 and decide what history to keep

What should you keep when you export all data from Sage X3?

Keep three layers: the transactional history the finance team needs, the configuration that explains it, and a metadata inventory of everything you leave behind. A full-history migration is rarely the right default, but a deliberate archive decision is, and that decision is also the moment to notice which clients hold long, connected X3 records.

This guide is for ERP consultants running X3 migrations, and for anyone supporting a move from Sage 100 or Sage 300 to NetSuite or another cloud ERP. It covers how to decide the history window, where the remainder is archived, and how to flag a manufacturing or distribution client for a licensing conversation without touching its data yourself.

What do you need before you start?

Settle these items in the first week of the project, not at cutover.

• A named data owner at the client, usually the controller or CFO, who can approve what is migrated, archived or retired.
• A list of X3 folders, legislations and sites in use, including old test or legacy folders that still hold history.
• The client's own record retention obligations, confirmed by its accountant or counsel. This guide does not set them.
• Admin access for a client employee, so that exports are run by the company and not by the consultant.
• A decision on whether the old X3 environment stays available read-only after go-live, and for how long.

How do you decide how much history migrates?

Use the three-bucket rule: migrate what operations need daily, archive what audit and reference need, and inventory what is left.

1. Open items and balances always migrate: open orders, open purchase and sales documents, inventory on hand, fixed asset registers, opening balances.
2. Recent closed history usually migrates for reporting continuity. Your client's finance team decides the window, commonly tied to comparative reporting and covenant needs.
3. Older closed history goes to a read-only archive: a reporting database, flat-file extracts by table, or a retained X3 instance.
4. Configuration and master data (chart of accounts, item masters, bills of material, routings, customer and supplier masters) are exported with their change dates, because they explain why old transactions look the way they do.

How do you run the export step by step?

Treat the export as a repeatable procedure with sign-off at each step.

1. Ask the client admin to list every X3 folder and the first and last posting date in each.
2. Export master data and configuration tables first, with row counts recorded.
3. Export transactional tables by fiscal year so a reviewer can reconcile each year against the trial balance.
4. Export attachments and linked documents separately and record where they are stored.
5. Reconcile row counts and control totals against the source before anything is archived or switched off.
6. Record the result in a one-page archive register: table or module, years covered, storage location, owner, retention decision.

The same register works for clients coming off older Sage products. A Sage 100 or Sage 300 environment tends to have fewer folders but more customizations, so ask about custom fields and add-on modules early. If your client is in construction rather than manufacturing, the pattern differs; see the guide on Sage 300 CRE and Vista construction accounting histories.

Which mistakes do consultants make most often?

Documents scattered across file shares need the same care; a client that stored scans and spreadsheets in a sync tool should see the Dropbox Business shared folder histories brief, and project tracking sheets are covered under Smartsheet project and PMO histories.

How does the archive decision connect to a licensing review?

The archive register is the same artifact a licensing review starts from. A manufacturing or distribution client with ten or more years of X3 history, connected to CRM, email, support and engineering records, may be a candidate for an introduction.

Look for the following during discovery, without opening any records:

• 50+ full-time employees at peak (contractors excluded) and several years of documented operations.
• Records across many systems, not only the ERP: email, Slack or Teams, CRM, finance, support, engineering and operations.
• A sponsor who can decide: the owner, CEO, CFO or an authorized representative.
• Clear rights: the company created the records and no client or supplier contract blocks licensing.
• Willingness to consider an exclusive AI-training license for an agreed term.

Records that mostly belong to customers or suppliers, or that are largely consumer personal data, are a poor fit. Read the who qualifies page for the full baseline.

What does the consultant actually do, and what do they never do?

Your part ends at the introduction and a few fit facts: headcount, years of operation, systems in use. The company then works directly with SourceX on its data inventory, price, terms, redaction rules and delivery. Confidential records stay with the company, and nothing is delivered without an executed agreement and the company's authorization. The data inventory builder helps a client list systems and years without exposing content. More on the role is in the guide for ERP consultants.

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, and no reward is guaranteed. The reward is a share of SourceX's fee and never reduces what the company receives. Check your own firm's policies on referral fees and client disclosure first.

When should you skip it?

Skip the introduction when the client has fewer than 50 full-time employees at peak, when archives were already deleted, when a trustee or assignee controls the assets, or when the owner will not consider an exclusive license. Wound-down or acquired companies can still qualify if the data still exists, so a retired X3 instance is worth a conversation before it is decommissioned.

Next step

Add an archive register to your next X3 statement of work. If a client looks like a fit, register as a partner and make the introduction, or have the sponsor apply at sourcex.si/apply. For a different ledger pattern, see the notes on keeping Xero records after a business ceases and the Zoho CRM history brief.