Sage 100

NS90: Migrate:

Sage 100 to NetSuite

From Sage 100 to NetSuite, every company, division and bill of materials.

NS90: Migrate handles each Sage 100 edition on its own terms, merges one database per company into NetSuite subsidiaries, and rebuilds divisions, segments, BOMs and tax so your first NetSuite close looks like your last Sage close.

Plan my Sage 100 migration

See Support Data

Source

Sage 100 Standard, Advanced and Premium (formerly MAS 90/200)

EXTRACTION

ProvideX ODBC, or SQL Server for Premium

DATA DOMAINS

14 supported, including BOMs

DELIVERED

4 Sage 100 migrations, up to 27 company databases

Depth

Options 2, 3 and 4

WHY NOW

3

Sage 100 versions under support at any time: the current release and the two before it

With Sage 100 2026 released, 2023 has retired, and each annual release pushes another version out of support. If an upgrade is due anyway, moving to NetSuite gives you consolidation, SuiteTax and real-time reporting instead of another upgrade cycle.

Source: Sage 100 product lifecycle policy

// Supported Data Domains

14 Sage 100 data domains, mapped field by field to NetSuite

Every domain has a proven field-level mapping from Sage 100 to NetSuite, with the legacy source object shown so your team can check coverage against its own data.

Master data

Transaction

Balances & files

Master data

Customers, vendors, items and the records every transaction depends on.

Customer

AR_Customer

Contact

AR_CustomerContact · AP_VendorContact

Bill of materials

BM_BillHeader · BM_BillDetail

Vendor

AP_Vendor

Item

CI_Item

Transaction

Sales, purchasing, banking and inventory transactions, with the reference numbers your team knows.

Sales order

SO_SalesOrderHeader

Credit memo

AR_OpenInvoice

Purchase order

PO_PurchaseOrderHeader

Vendor credit

AP_OpenInvoice

Invoice

AR_OpenInvoice · AR_InvoiceHistoryHeader

Customer payment

AR_CashReceiptsHistory

Vendor bill

AP_OpenInvoice · AP_InvoiceHistoryHeader

Vendor payment

AP_CheckHistoryDetail

Balances & files

Period balances for reconciliation, and the documents attached to your records.

Trial balance

GL_DetailPosting

Choose your depth

Bring as much Sage 100 history as your business needs

Trial balances are part of every option. Pick how much transaction detail lives in NetSuite and how much stays reportable in NetSuite Analytics Warehouse.

Option 1

Balances

Trial balances only

Monthly trial balances by account and segment loaded to NetSuite. Fastest path to a clean opening position.

Available

Option 2

Balances + drill-down

Trial balances in NetSuite, detail in NSAW

Trial balances in NetSuite with transaction-level drill-down to legacy detail in NetSuite Analytics Warehouse.

Chosen on 1 Sage 100 project

Option 3

Open items + history

Masters and open transactions in NetSuite, history in NSAW

Customers, vendors, items and open AR/AP/orders in NetSuite. Every closed transaction stays reportable in NSAW.

Chosen on 1 Sage 100 project

Option 4

Full history

Open and closed transactions in NetSuite

The years you choose of closed and open transactions in NetSuite, with automated trial-balance true-up by period.

Chosen on 1 Sage 100 project

What we’ve learned on Sage 100 projects

The Sage 100 details that make or break a migration

These come from real NS90 Sage 100 projects. Each is already built into our standard Sage 100 mapping, so you don’t discover it at UAT.

Every edition is different

Standard and Advanced store data in ProvideX and are read through a throttled, sequential ODBC stream that avoids driver timeouts and data-type errors. Premium runs on SQL Server and is extracted with SQL.

One database per company

Sage 100 creates a database per company code. We have extracted and merged up to 27 company databases for a single client, each mapped to a NetSuite subsidiary.

Open vs. history by balance, not by type

Sage history types don't always say whether a document is still open. We classify by the balance itself, so open credits and invoices are never missed.

Keys that don't collide

Invoice numbers repeat across vendors and AR/AP divisions. We build NetSuite external IDs from the full composite key: division, vendor and document.

Divisions and segments

Main account, sub-account segments and AR/AP divisions are flattened into NetSuite accounts plus department, class and location.

Bills of materials and units

BOMs, revisions, location-specific BOMs and units of measure are harmonized before items load, so assemblies build on day one.

Tax that recalculates correctly

Sage tax schedules and classes map to NetSuite tax codes, SuiteTax or Avalara, and are tested on open sales documents.

Long balance history

Trial balances going back to 2016 are loaded by period and reconciled to Sage GL detail posting, with bulk journal approval built into the plan.

Throttled streaming for ProvideX

ProvideX ODBC can time out on large tables. Sequential streaming extraction avoids timeouts and data-type errors.

Negative invoices are credits

Any invoice type with a negative amount becomes a credit memo in NetSuite, whatever Sage calls it.

Returns as positive amounts

NetSuite needs positive amounts on returns, so return and credit lines are converted consistently.

How NS90: Migrate works

From Sage 100 to a reconciled NetSuite in six steps

Every step runs on NS90 Migrate, MHI’s cloud-native migration engine on NSIP and NSAW. It handles extraction, landing, harmonization, parallel loading and trial-balance validation as repeatable jobs, so each rehearsal and the final delta pull run the same way.