Sage 300

NS90: Migrate:

Sage 300 to NetSuite

Sage 300 to NetSuite, with every company, segment and fund intact.

NS90: Migrate reads each Sage 300 company database read-only, decomposes your segmented accounts into NetSuite accounts and segments, and loads the history you choose with period-by-period proof.

Plan my Sage 300 migration

See Support Data

Source

Sage 300 (formerly Accpac) on SQL Server

EXTRACTION

Read-only SQL Server or a database backup, one database per company

Data domains

14 supported

DELIVERED

Sage 300 migration for a nonprofit with statistical ledger

WHY NOW

Sep 2026

Sage 300 2024 support ended when the 2027 release shipped

Sage supports only the current Sage 300 release and the two before it, so every annual release retires another version. If an upgrade is due, NetSuite OneWorld replaces separate company databases and inter-company tools with one system.

Source: Sage Knowledgebase, Sage 300 product lifecycle

// Supported Data Domains

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

Domains with solid dots have a proven field-level mapping from Sage 300 to NetSuite. Hollow markers are domains we scope per project, using mappings proven on other source systems.

Master data

Transaction

Balances & files

Master data

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

Customer

ARCUS

Contact

ARCUS · APVEN contacts

Vendor

APVEN

Item

ICITEM

Transaction

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

Invoice

ARIBH · ARIBD

Customer payment

ARPJH · ARPJD

Vendor credit

APIBH · APIBD

Journal entry

GLJEH · GLJED

Purchase order

POPORH1 · POPORL

Credit memo

ARIBH · ARIBD

Vendor bill

APIBH · APIBD

Vendor payment

APPJH · APPJD

Statistical journal

Statistical company database

Balances & files

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

Trial balance

GLJEH · GLJED by fiscal period

Choose your depth

Bring as much Sage 300 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.

Available

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.

Available

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 300 project

What we’ve learned on Sage 300 projects

The Sage 300 details that make or break a migration

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

One database per company

Sage 300 keeps each company in its own SQL Server database, plus a system database. We extract each read-only and merge them into NetSuite subsidiaries in one pass.

Segments, not strings

Account and cost-center segments are split into NetSuite accounts plus department, class and location, never carried as one long string.

Every nonprofit segment on every line

Restriction, functional expense, revenue stream and grant segments are mapped on invoices, bills, journals and trial balances alike, and sample GL strings are checked before client review.

Statistical ledgers come too

Non-financial counts, like meals served, load as NetSuite statistical journals so metrics and financials stay together.

Refresh from production, then extract

Test databases go stale. We refresh from production right before each extract and check the latest transaction date before loading.

International characters, safely

Names with accents or special characters are landed with character-length sizing, so nothing truncates on the way in.

Payments inside the window

Payments whose invoice or bill falls before the history window are either filtered or loaded with their documents, as agreed in the plan.

IDs locked until go-live

Customer and vendor IDs are frozen through cutover. Renames and merges happen after go-live, so transactions always find their records.

Vendor types decided

Sage 300 doesn't flag individuals vs companies; we classify vendors before load.

Payments to the right bank account

Customer payments are mapped to the actual deposit account, not a default clearing account.

Accounts valid for each transaction

Bills coded to bank or AR accounts are remapped before load.

Every cost center mapped

Unmapped cost centers are caught before journals load.

How NS90: Migrate works

From Sage 300 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.