How to migrate from Sage 300 to Sage Intacct
To migrate a client from Sage 300 to Sage Intacct with superglue's AI agent, connect the client's Sage 300 database, and give superglue access to the client's Sage Intacct 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 Sage Intacct?
Migrating from Sage 300 to Sage Intacct 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 Sage Intacct
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 Sage Intacct.
- 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 a Sage Intacct sandbox or implementation company 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 Sage Intacct?
The client authorizes the superglue sender ID in Sage Intacct and adds a user for superglue. superglue configures Sage Intacct and loads the data through that access, in a Sage Intacct sandbox or implementation company first, in this order:
- 01
Multi-entity, the base currencies and the first fiscal month. Base currencies and the first fiscal month can change only before transactions exist.
- 02
The configuration of each module, such as General Ledger, Accounts Payable and Accounts Receivable, and the names of terms and dimensions.
- 03
Entities, locations, departments and the other dimensions.
- 04
The chart of accounts and the journals.
- 05
Customers, vendors and items, then the opening balances and the open items.
Access setup for the client: Sage Intacct configuration guide
What moves from Sage 300 to Sage Intacct?
| In Sage 300 | In Sage Intacct |
|---|---|
| Chart of accounts | GL accounts |
| Account segments such as division and region | Dimensions such as departments, locations and classes |
| Customers and customer groups | Customers |
| Contracts and projects | Projects |
| Vendors and vendor groups | Vendors |
| Items and item categories | Items |
| Bank codes | Checking and credit card 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 invoices and AP bills with their original numbers, dates and due dates, so the aging in Sage Intacct 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 summary journal entries per month, account and dimension.
Which decisions do you make when you migrate from Sage 300 to Sage Intacct?
- 01
Where do Sage 300 account segments go?
Sage 300 account numbers can have up to ten segments in Sage 300 Premium, four in Advanced and three in Standard, and different account structures can apply to different accounts.
superglue maps the account segment to Sage Intacct accounts and proposes a dimension for each other segment in use.
- 02
Which optional fields become dimensions?
Sage Intacct dimensions work on the transactions they are set up for, and every report can filter and group by them. Optional fields that only describe a record fit custom fields.
superglue recommends dimensions for optional fields used on transactions, and custom fields for the rest.
- 03
Which companies become entities, and which become locations?
In Sage Intacct, an entity has its own books, tax and bank accounts. A location only adds a reporting value.
superglue recommends one entity for each legal company in Sage 300, and locations for the sites inside a company.
- 04
Which records are shared across entities?
Customers, vendors and items can live at the top level and be shared, or belong to one entity.
superglue recommends shared customers and vendors, so each company appears once and intercompany reporting stays clean.
- 05
How much history moves?
Most clients need the open items plus one to two years of monthly balances in Sage Intacct, 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 Sage Intacct?
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.
Plan module configuration as its own workstream
In Sage Intacct, the settings of General Ledger, Accounts Payable and the other modules cannot be imported like data. Unless the partner starts from a template company, they are set by hand, screen by screen. superglue sets them and checks every value, so the configuration is ready when the data is.
Agree user-defined dimensions with the person who reports on them
A user-defined dimension stays in Sage Intacct once it holds data. Add only the ones the client will report on, and get each one agreed before the first load.
superglue also runs the rest of the Sage Intacct project. See the Sage Intacct implementation
Frequently asked questions
Which data moves from Sage 300 to Sage Intacct?
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 Sage Intacct.
Does superglue write to Sage Intacct without my approval?
No. superglue only reads Sage 300. Before any write to Sage Intacct, 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 Sage Intacct 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.