How to migrate from Sage 100 to NetSuite
To migrate a client from Sage 100 to NetSuite with superglue's AI agent, connect the client's Sage 100 data, 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 100 to NetSuite?
Migrating from Sage 100 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 100 and NetSuite
Connect Sage 100 read-only through its ODBC driver, or through the SQL Server database on Sage 100 Premium. superglue writes nothing. The client then gives superglue access to NetSuite.
- 02
Assess the Sage 100 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 100 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 100: 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 100?
- The superglue gateway runs on a computer with Sage 100 installed and reads with a Sage 100 user. Sage 100 Premium can also be read straight from SQL Server.
- When superglue reads through the Sage 100 business objects, each session uses a user license while it runs, so superglue signs out after each task and the client keeps working.
- Ask which third-party enhancements the client uses, because they keep data in their own tables.
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 100 to NetSuite?
| In Sage 100 | In NetSuite |
|---|---|
| General ledger accounts | Accounts |
| Account segments such as division and department | Departments, classes and locations |
| Customers by AR division | Customers |
| Jobs | Projects |
| Vendors by AP division | Vendors |
| Items and product lines | Items |
| Bank codes | Bank accounts |
Open items
Open invoices, credit memos and unapplied cash, open AP invoices, open sales and purchase orders, and inventory on hand per warehouse.
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 100 keeps history as long as the retention settings allow. superglue reads all of it and reports the first complete year.
History loads as journal entries per month, account and segment.
Which decisions do you make when you migrate from Sage 100 to NetSuite?
- 01
Where do Sage 100 account segments go?
NetSuite keeps one account and puts departments, classes and locations on the transaction, or on each line when per-line segments are turned on.
superglue splits each account into the main account and NetSuite segments, usually departments or classes.
- 02
Where do product lines go?
Sage 100 product lines set the accounts for their items. In NetSuite, each item holds its own accounts: inventory items have income, cost of goods sold and asset accounts, and other items have income and expense accounts.
superglue sets the accounts on each NetSuite item from its product line, and proposes a class for product lines the client reports on.
- 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 100, 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 100 to NetSuite?
The AR division is part of the customer number
The same company can exist as 01-ACME and 02-ACME, with separate balances. superglue finds these pairs and proposes one customer, with the division kept for reporting.
Product lines decide the accounts
Each product line holds the sales, cost of goods sold and inventory accounts for its items. superglue maps the product lines to the account defaults in the new system, so postings stay the same.
Enhancements add their own tables
Third-party enhancements add fields and tables that the standard exports miss. superglue reads the whole database and lists the extra data, so you decide what moves.
Registers that were not updated sit outside the general ledger
Sales journals and AP invoice registers that were entered but not updated do not appear in the general ledger. superglue lists them before each load.
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 100 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 100. 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 100: 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 100 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.