Systems and records
Sage 100 and Sage 300 history: archiving before a cloud ERP move
By SourceX Editorial · Updated
Short answer
Before a cloud ERP move, carry forward only the Sage 100 or Sage 300 data the new system needs to run: open items, balances, masters and summarized sales history. Archive the full transaction history, including invoice lines, purchase receipts, inventory movements and order notes, in a readable, documented copy. Test that archive before Sage is switched off.
Key takeaways
- Carry the working set into the new ERP and keep the full Sage transaction history in an archive outside it.
- Invoice line history, purchase receipts, inventory transactions and order comments are the records distributors most often lose.
- Extract tables with their keys and a data dictionary, not only printed reports.
- Retention needs set by your accountant and counsel decide how long the archive stays readable, not the migration budget.
- Retired Sage history can have value beyond retention when orders, returns and exceptions stay linked, so keep those links intact in the archive.
Carry the working set, archive the full record#
The working set is what a cloud ERP needs to run on day one: open receivables and payables, open sales and purchase orders, general ledger balances, and clean customer, vendor and item masters. The full record is everything Sage 100 or Sage 300 has accumulated, and it belongs in an archive that does not depend on the old server staying alive.
Converting years of detailed transactions into a new ERP is slow, costly and often unnecessary, because new systems post differently and old documents rarely map cleanly. Many distributors load summarized history for comparison reports, such as sales by customer and item by period, and leave line-level detail in the archive.
Many long-time users still call Sage 100 by its older MAS 90 name, and many Sage 300 sites have run for years with add-ons and customizations. Those add-ons often hold the records people forget, such as warehouse scans, EDI documents or custom pricing tables. Check the current support status of your Sage version and add-ons with your Sage partner too: an older version nearing the end of support is a reason to finish the archive early rather than leave it until the server is due for retirement.
What to carry and what to archive, by module#
For each Sage module, carry open items, balances and masters into the new ERP and archive the closed transaction detail in full. A single module-by-module table keeps finance, operations and IT working from the same list, and each row should name an owner who signs off the decision before conversion scripts are written.
| Sage module or area | Carry into the new ERP | Archive in full |
|---|---|---|
| General ledger | Opening balances and summarized periods for comparison | Full journal and posting detail |
| Accounts receivable | Open invoices, credit memos and customer masters | Paid invoice history, cash receipts and statements |
| Accounts payable | Open invoices and vendor masters | Paid invoice and check history, including information-return detail |
| Sales orders and invoice history | Open orders and summarized sales by customer and item | Invoice lines with prices, discounts, overrides and comments |
| Purchase orders and receipts | Open purchase orders | Receipt history, vendor lead times and landed cost detail |
| Inventory management | Item masters, quantities and costs on hand, open lots and serials | Inventory transactions, adjustments and lot or serial trails |
| Returns and credits | Open return authorizations | Closed returns with reasons and dispositions |
| Bank reconciliation | Unreconciled items | Reconciliation history |
| Add-ons and custom tables | Only what new processes still need | All tables, with notes on their purpose |
History that distributors underestimate#
Distributors most often underestimate the history that explains why something happened rather than what was posted. Invoice totals survive any migration; the line-level prices, overrides and comments that show how a customer was quoted often do not.
These records matter for pricing reviews, customer disputes and warranty claims long after go-live. They are also the operational records with the most structure for analysis, because each one ties a request to a decision and an outcome.
- Sales history by customer and item, including price overrides and special pricing records.
- Order and invoice comments, where customer service notes shortages, substitutions and delivery issues.
- Return authorizations with reason codes, inspection notes and credit decisions.
- Purchase receipts showing vendor lead times, partial shipments and backorders.
- Lot and serial history for traceability and recall questions.
- Scanned documents and attachments linked to orders, receipts and vendor invoices.
How to extract an archive you can read later#
An archive you can read later is a set of tables with keys, a description of what each field means, and a way to search it without Sage running. Depending on edition and version, Sage 100 stores data in its own file format or in Microsoft SQL Server, and Sage 300 commonly runs on SQL Server, so ask your Sage partner which extraction route fits your installation.
Load the extracted tables into a simple reporting database or a governed file store, and write down how to query them. An archive that only one departing employee understands is not an archive.
- Step 1: freeze a final period and run the standard year-end and aging reports to PDF.
- Step 2: export every table you will archive to CSV, or take a database backup for SQL-based installations.
- Step 3: keep primary keys and document numbers in every file so lines join back to headers.
- Step 4: capture a data dictionary or file layout, including user-defined fields and code lists.
- Step 5: download attachments and keep a map from each file to its document number.
- Step 6: check row counts and control totals against Sage reports before the server is retired.
How long the archive must stay readable#
The archive has to stay readable for the longest of your retention periods, and your accountant and counsel set those periods, not the migration plan. Tax filings, audits, lender requirements, customer disputes, warranty terms and product traceability each run on their own clock.
Record each period in a retention schedule, and name who holds the archive and who may grant access. When a period ends, delete on purpose and keep a note of what was removed.
| Need | Records it relies on | Who sets the period |
|---|---|---|
| Tax and audit support | General ledger detail, payables and receivables history, sales tax records | Outside accountant |
| Customer disputes and collections | Invoice lines, statements, proof of delivery, credits | Controller with counsel |
| Warranty and product traceability | Lot and serial history, receipts, returns | Operations and quality leads |
| Pricing and margin review | Sales history with overrides and costs | Sales and finance leaders |
Illustrative: an industrial distributor moves off Sage 100#
Illustrative: a fictional distributor of fasteners and fittings has run Sage 100 with a warehouse scanning add-on for many years. It is moving to a cloud ERP, and the controller wants a clean start without losing the history that sales and purchasing rely on.
The team carries open orders, open receivables and payables, item and customer masters, and sales summarized by customer, item and month. It archives every invoice line, purchase receipt, inventory transaction and return authorization into a reporting database, along with the scanning add-on's tables and a field-by-field data dictionary.
After go-live, a large customer questions the price charged on an old contract item. The answer comes quickly from the archived invoice lines and order comments, not from a restored server. The old Sage license is retired once the first audit on the new system is complete.
Archive cost or asset: how SourceX looks at retired ERP history#
Retired ERP history is usually treated as a storage cost, but linked order, return and exception records can also be licensable operational data. AI developers building tools for distribution look for examples of how real orders were priced, fulfilled, delayed and corrected, which is what invoice lines, receipts and return notes record.
The SourceX Enterprise Data Value Framework, a SourceX methodology rather than an industry standard, rates records on drivers such as domain expertise, human-generated signal, scale, recency, data cleanliness and rights, while preparation cost and privacy burden reduce net value. Any license leaves ownership with the distributor, because records are licensed for a defined use rather than sold. The first fit check asks only for descriptions, such as which Sage edition ran, how many years the archive spans and which modules were in use.
Frequently asked questions
Can we keep Sage running read-only after go-live?
Yes, for a period, but a read-only Sage installation still needs a supported operating system, security patches, backups, someone who can run its reports and a license that still permits use. Check your Sage license or subscription terms before you stop paying. Many distributors keep it until the first year-end close and audit are complete, then rely on the extracted archive.
Should we convert historical invoices into the new ERP as transactions?
Usually not in detail. Posting old invoices as live transactions can disturb balances, tax reports and costing in the new system. Load summarized history for comparison reporting instead, and keep the original line detail in the archive, where it can be queried without touching the books.
How do we archive several Sage 300 company databases?
Archive each company database separately, with its own backup and data dictionary, and record which legal entity each belongs to. Keep intercompany and consolidation reports for every closed period, because rebuilding consolidations from separate archives later is slow and error-prone.
Who should have access to the archive?
Give read access to the people who answer questions from it: receivables and payables staff, the controller, auditors on request, and sales leaders for pricing history. Keep access logged and limited, because invoice and customer records include confidential pricing and terms.
Does the data dictionary matter if we have the tables?
Yes. Sage table and field names are often abbreviated, and user-defined fields carry meanings only your team knows. Without a dictionary, a future analyst may misread a status code or join tables incorrectly. Capture field descriptions, code lists and custom field purposes before the people who set them up move on.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.