Sage 100 to cloud ERP: keeping a distributor's sales history

What sales history stays behind in a Sage 100 move?#

In most Sage 100 moves, the sales history that stays behind is the closed detail: invoice lines, shipped sales orders, credit memos and the salesperson and pricing data attached to them. Migration projects focus on what the new system must have at go-live: open documents, current masters and opening balances.

That choice is reasonable for go-live and costly later. Detailed sales history answers questions the new ERP cannot: what a customer paid for an item over time, which credits followed which shipments, how margins moved by product line, and what lapsed customers used to buy.

Whether the target is NetSuite, Acumatica, Business Central or another cloud ERP, the migration partner will usually scope any history load separately. Ask early what is included, because a summary load and a line-level load are very different deliverables with different costs.

Why the CFO should own the history decision#

The CFO should own the history decision because most questions that depend on old sales detail are financial: margin analysis, rebate claims, customer pricing disputes, commission questions, audits, lender reviews and buyer diligence. Operations and IT plan the cutover; finance knows which past questions still need answers.

Finance also inherits the questions nobody plans for. A customer disputes a price from an old contract, a supplier audits a rebate claim, or a tax authority asks for support behind exempt sales. Each answer depends on invoice lines, customer records and documents that only the old system holds unless they were exported.

Record retention sits with finance as well. Tax, labor and contract obligations may require keeping certain records after the system changes. For example, the Department of Labor's FLSA recordkeeping fact sheet says employers must preserve sales and purchase records for at least three years. Confirm the requirements with your tax advisor and make sure the archive itself, not just a printed report, meets them.

How much sales history to load into the new ERP#

How much sales history to load into the new ERP depends on who needs it inside the system every day. Sales reps comparing a customer's purchases with last season need some history on screen; finance answering an audit question usually does not, as long as the archive is reliable.

Most distributors land on the second or third option below and keep everything else in the archive. Whatever you choose, write it down with the date range, so nobody later assumes the new ERP holds more than it does.

History-keep checklist before cutover#

A history-keep checklist names every table or report to export, the date range, the format and the person who verified it. Work through it with the Sage partner and the controller well before the cutover weekend, not after it.

• 1Invoice history, header and line detail, with quantity, unit price, extended price, unit cost and salesperson.
• 2Sales order history, including cancelled and lost orders where they were kept.
• 3Credit memos and returns with reason codes and the original invoice reference.
• 4Customer master, including inactive customers, ship-to addresses, terms and price levels.
• 5Item master, including discontinued items, units of measure, primary vendors and product lines.
• 6Pricing records: price levels and customer or contract pricing, with effective dates.
• 7Commission and salesperson assignment history, if commissions were calculated in Sage.
• 8General ledger detail for the same periods, used to reconcile the exports.
• 9An ID crosswalk for any renumbered customers, items or salespeople.

Which export formats keep the history usable?#

The export format that keeps history usable is one a future analyst can open without Sage 100 and join without guesswork. In practice that means flat files per table with keys intact, backed by a complete copy of the original data for reference.

Reconcile every export before decommissioning. Totals by month and by customer from the exported invoice lines should match Sage 100 reports and the general ledger, and the reconciliation workbook should be saved alongside the files.

Keeping old and new IDs connected#

Old and new IDs stay connected only if someone builds and keeps a crosswalk table. Migrations are a common time to renumber customers, merge duplicate accounts and rename item codes, and each of those changes breaks the link between sales history and the new system unless it is mapped.

Keep the crosswalk as a simple file with the old ID, the new ID, the change date and the reason, and store it with the archive. When a merged customer appears twice in history, the crosswalk is the only record that the two accounts are the same business.

Illustrative: an irrigation supply distributor keeps its seasons#

Illustrative: a fictional distributor of irrigation and landscape supplies has run Sage 100 for many years and sells heavily in spring and early summer. Its migration partner proposed loading open documents, active customers and items, and nothing else into the new cloud ERP.

The CFO chose summarized sales by customer, item and month inside the new ERP, so branch managers could compare seasons, and kept line-level invoices, credits and price levels in a CSV archive reconciled to monthly revenue. Because item codes were being changed to match supplier part numbers, the team built a crosswalk first.

After go-live, reps used the summaries to plan preseason orders with contractors, and finance answered a supplier rebate audit from the archived invoice lines. The same archive later gave a forecasting project several full seasons of demand by item and branch.

What a licensing review looks for in archived sales history#

A licensing review looks for sales history that shows decisions and outcomes, not just totals: invoice lines tied to price overrides, credits with reasons, returns and notes. SourceX begins with a fit check that uses descriptions only, such as systems, date ranges, record families and known restrictions, so nothing leaves the company at that point.

When a distributor decides to go further, the rights step concentrates on customer pricing confidentiality and supplier agreements, and preparation strips customer identities. For a package that goes ahead, the SourceX Evidence Packet documents provenance back to the Sage archive, the licensing rights confirmed, permitted use, the privacy record for customer data and the distributor's release authorization.