How to migrate from Sage 50 to Acumatica
To migrate a client from Sage 50 to Acumatica with superglue's AI agent, connect the client's Sage 50 company or upload its exports, and give superglue access to the client's Acumatica account. superglue assesses the data in minutes, plans every phase, recommends an answer to each decision, and runs a trial load that reconciles to the cent before cutover. You review, decide and sign off with the client.
This guide covers Sage 50 US, formerly Peachtree.
What are the steps to migrate from Sage 50 to Acumatica?
Migrating from Sage 50 to Acumatica takes six steps: connect both systems, assess the data, plan every phase, decide the mapping, run a trial load and cut over. Each load repeats exactly what you tested, and every write waits for your approval.
- 01
Connect Sage 50 and Acumatica
Connect the client's Sage 50 company read-only through the Sage 50 ODBC driver, or upload the standard exports. superglue writes nothing. The client then gives superglue access to Acumatica.
- 02
Assess the Sage 50 data
In minutes, superglue counts every record, finds the open items and lists the data issues with examples. You know the size of the migration before you quote it.
- 03
Plan every phase
superglue drafts the plan from discovery to cutover, with tasks, owners and the Sage 50 specifics already in it.
- 04
Decide the mapping
superglue brings each decision below with a recommendation from the client's own data. You confirm or change each answer, and the client signs the mapping.
- 05
Run the trial load
superglue loads an Acumatica test tenant and compares it with Sage 50: the trial balance per period, the open receivables and payables per customer and vendor, and the inventory value. superglue explains every difference before cutover.
- 06
Cut over
At cutover, superglue loads the final data with the same steps as the trial load, and you sign the reconciliation with the client.
How do you get the data out of Sage 50?
- The client sets a data access password in Sage 50, and the superglue gateway reads the company on a computer with Sage 50 installed. The standard exports work too.
- Ask whether old years were purged. Purged transactions are gone, so those years move as balances.
- Sage 50 keeps each company in its own folder, so ask for every company in scope.
The client installs the superglue gateway once: Connecting to on-prem systems
What needs to be configured in Acumatica?
The client adds an API user and a connected application for superglue. superglue configures Acumatica and loads the data through that access, in an Acumatica test tenant first, in this order:
- 01
The features the client licenses, such as subaccounts, multicurrency and projects.
- 02
The subaccount structure, companies and branches, and the chart of accounts.
- 03
The financial year and its periods, opened for every migration date.
- 04
Cash accounts, credit terms, taxes and numbering, then the preferences and classes of each module.
- 05
Customers, vendors and items, then the opening balances and the open items.
Access setup for the client: Acumatica configuration guide
What moves from Sage 50 to Acumatica?
| In Sage 50 | In Acumatica |
|---|---|
| Chart of accounts | GL accounts |
| Departments in the account IDs | Subaccount segments and branches |
| Customers | Customers and customer classes |
| Jobs, phases and cost codes (Premium and higher) | Projects and project tasks |
| Vendors | Vendors and vendor classes |
| Inventory items | Stock and non-stock items |
| Cash accounts | Cash accounts |
Open items
Open invoices and credit memos, open purchases and vendor credits, open sales and purchase orders, and inventory on hand with its cost.
Open items load as AR and AP documents with their original numbers, dates and due dates, in an open financial period, so the aging in Acumatica matches on day one.
History
Sage 50 keeps every transaction that was not purged. superglue reads all of them and reports how far back the detail goes.
History loads as journal transactions per financial period, account and subaccount.
Which decisions do you make when you migrate from Sage 50 to Acumatica?
- 01
How do Sage 50 account IDs become accounts and subaccounts?
Acumatica already separates the account from the subaccount, so the department part of a Sage 50 account ID maps to a subaccount segment.
superglue splits each account ID and proposes the subaccount structure, with only the segments the client reports on.
- 02
Where do Sage 50 jobs go?
Acumatica projects have tasks, and the cost codes feature tracks budgets by cost code.
superglue maps jobs to projects, phases to project tasks and Sage 50 cost codes to Acumatica cost codes.
- 03
Which companies and branches does the client need?
In Acumatica, a company can have several branches. Branches drive balances, reports and access rights.
superglue recommends one company for each legal company in Sage 50, and branches only where the client reports per site.
- 04
Which classes carry the defaults?
Customer and vendor classes set the accounts, terms and other defaults for every record in them, and item classes set the units, the valuation method and the posting class.
superglue proposes classes from the groups the client already uses, so each record gets its defaults from its class.
- 05
How much history moves?
Most clients need the open items plus one to two years of monthly balances in Acumatica, and older years as yearly balances. The client keeps the older detail in an archive.
superglue recommends two years of monthly balances per account, and full transaction detail only where the client needs to look into single transactions.
What are the common challenges when you migrate from Sage 50 to Acumatica?
Purged transactions leave gaps in the history
Sage 50 lets users purge old transactions, and the detail of those years is gone. superglue reports the first year with full detail, and moves the earlier years as balances.
Expect the chart of accounts to shrink
Many Sage 50 companies repeat each account per department, such as 6100-01 and 6100-02, so the chart often shrinks a lot once departments become dimensions. Show the client the new chart early, because their reports change with it.
Reported years still change
Sage 50 keeps two fiscal years open, and clients post into the earlier year after its figures were reported. superglue compares each reported year with the approved trial balance before the history moves.
Multi-company clients need an intercompany plan
Clients with several companies keep one company folder for each, with intercompany balances between them. Agree early which companies merge, which become entities, and how the intercompany balances settle. superglue reads every company and matches the intercompany balances.
Brief the controller on equity accounts
Acumatica has no equity account type, so equity accounts are set up as liability accounts and shown as equity on the balance sheet. Controllers who read the account list often ask about it, so explain it before they see it.
Finish the preferences before the first trial load
Acumatica does not load the records of a module until that module's preferences are complete. Put the preferences in the configuration plan ahead of the first trial load.
superglue also runs the rest of the Acumatica project. See the Acumatica implementation
Frequently asked questions
Which data moves from Sage 50 to Acumatica?
The chart of accounts, customers, vendors and items, the open items, and as much history as the client needs. The mapping table on this page shows where each record lands in Acumatica.
Does superglue write to Acumatica without my approval?
No. superglue only reads Sage 50. Before any write to Acumatica, it shows the target, the connection and a transformed sample, and waits for your approval.
How do I know the migration is complete?
superglue reconciles the trial load and the final load against Sage 50: the trial balance per period, the open receivables and payables per customer and vendor, and the inventory value. You get a reconciliation report to sign with the client.
What happens when I start this migration?
You sign up and connect the client's systems. If you want to see a full migration run first, superglue can set up Pinecrest Supply, a sample client.
Start your Sage 50 to Acumatica migration
Sign up and connect the client's systems, or let superglue set up Pinecrest Supply, a sample client, to see a full migration run first.