How to migrate from Sage 300 to NetSuite
To migrate a client from Sage 300 to NetSuite with superglue's AI agent, connect the client's Sage 300 database, and give superglue access to the client's NetSuite 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 NetSuite?
Migrating from Sage 300 to NetSuite 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 NetSuite
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 NetSuite.
- 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 NetSuite sandbox account 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 NetSuite?
The client turns on the SuiteCloud features and adds an integration record for superglue. superglue configures NetSuite and loads the data through that access, in a NetSuite sandbox account first, in this order:
- 01
Subsidiaries and their base currencies.
- 02
Accounting preferences and periods.
- 03
The chart of accounts, then departments, classes and locations.
- 04
Custom fields, records, segments, forms and workflows, and SuiteScript where the design needs it.
- 05
Customers, vendors, contacts and items, then the opening balances and the open items.
Access setup for the client: NetSuite configuration guide
What moves from Sage 300 to NetSuite?
| In Sage 300 | In NetSuite |
|---|---|
| Chart of accounts | Accounts |
| Account segments such as division and region | Departments, classes and locations |
| Customers and customer groups | Customers |
| Contracts and projects | Projects |
| Vendors and vendor groups | Vendors |
| Items and item categories | Items |
| Bank codes | Bank 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 invoices, credit memos, vendor bills and vendor credits with their original numbers and dates, so the aging in NetSuite 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 entries per month, account and segment.
Which decisions do you make when you migrate from Sage 300 to NetSuite?
- 01
Where do Sage 300 account segments go?
NetSuite keeps one account and offers departments, classes, locations and custom segments for the rest.
superglue maps each segment in use to a standard NetSuite segment, and proposes a custom segment only where the standard ones are taken.
- 02
Which optional fields become segments?
NetSuite custom segments work on transactions and in reports. Optional fields that only describe a record fit custom fields.
superglue recommends custom segments for optional fields used on transactions, and custom fields for the rest.
- 03
How many subsidiaries does the client need?
In NetSuite OneWorld, subsidiaries set the currency, the tax and which customers and vendors each company can use. Changing them after go-live means reworking master data.
superglue recommends one subsidiary for each legal company in Sage 300, decided before any master data loads.
- 04
Which item types do the items become?
NetSuite separates inventory, non-inventory, service, other charge, kit and assembly items. Non-inventory and service items can be for sale, for purchase or for resale.
superglue proposes the type for each item from how the client bought and sold it.
- 05
How much history moves?
Most clients need the open items plus one to two years of monthly balances in NetSuite, 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 NetSuite?
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.
Lock the subsidiary structure before the first load
The currency of a NetSuite subsidiary is fixed once its first transaction is saved, so a late change means a new subsidiary and a reload. Get the structure signed in the design phase.
Plan the sandbox around refreshes
A sandbox refresh replaces everything in the sandbox, including your configuration. superglue keeps the configuration and applies it again, so a refresh does not cost you the setup work.
superglue also runs the rest of the NetSuite project. See the NetSuite implementation
Frequently asked questions
Which data moves from Sage 300 to NetSuite?
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 NetSuite.
Does superglue write to NetSuite without my approval?
No. superglue only reads Sage 300. Before any write to NetSuite, 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 NetSuite 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.