How to migrate from Sage 300 to Acumatica
To migrate a client from Sage 300 to Acumatica with superglue's AI agent, connect the client's Sage 300 database, 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.
What are the steps to migrate from Sage 300 to Acumatica?
Migrating from Sage 300 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 300 and Acumatica
Connect the Sage 300 company database on SQL Server read-only, or upload the client's exports. superglue writes nothing. The client then gives superglue access to Acumatica.
- 02
Assess the Sage 300 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 300 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 300: 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 300?
- superglue reads the company database on SQL Server through the superglue gateway, or uses the Sage 300 Web API with a dedicated Sage 300 user.
- Each company is its own database, so list every company in scope and how the companies trade with each other.
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 300 to Acumatica?
| In Sage 300 | In Acumatica |
|---|---|
| Chart of accounts | GL accounts |
| Account segments such as division and region | Subaccount segments and branches |
| Customers and customer groups | Customers and customer classes |
| Contracts and projects | Projects and project tasks |
| Vendors and vendor groups | Vendors and vendor classes |
| Items and item categories | Stock and non-stock items |
| Bank codes | Cash accounts |
Open items
Open invoices, debit and credit notes and prepayments, open AP invoices, open orders, and inventory on hand per location.
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 300 keeps posted transactions per fiscal period. superglue reads every year and reports where the detail was cleared.
History loads as journal transactions per financial period, account and subaccount.
Which decisions do you make when you migrate from Sage 300 to Acumatica?
- 01
How do Sage 300 account segments become subaccounts?
Acumatica has one account and a segmented subaccount. Sage 300 segments other than the account map to subaccount segments.
superglue proposes the subaccount structure from the segments in use, so the client's reports keep their layout.
- 02
Where do Sage 300 account sets go?
In Acumatica, customer, vendor and item classes and posting classes set the control accounts that Sage 300 account sets hold.
superglue proposes one class for each account set in use, with the same control accounts.
- 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 300, 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 300 to Acumatica?
Account sets hold the control accounts
AR, AP and inventory account sets decide which control accounts each record posts to. superglue maps each account set to the defaults in the new system and checks that every subledger agrees with its control account.
Optional fields carry reporting values
Clients keep region, salesperson or cost center in optional fields. superglue lists each optional field with its use, and proposes where each one goes in the new system.
Unposted batches hide real invoices and payments
Batches that were entered but never posted are missing from the trial balance, yet they often hold real invoices and payments. Ask the client to post or delete them before each extract. superglue lists them, so nothing goes missing at cutover.
Multi-company clients need an intercompany plan
Clients with several companies keep one database 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 300 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 300. 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 300: 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 300 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.