Sage 200

NS90: Migrate:

Sage 200 to NetSuite

Sage 200 to NetSuite, from items and lot-tracked assemblies to balances.

NS90: Migrate extracts Sage 200 straight from SQL Server, maps items, bills of materials and suppliers to NetSuite, and loads balances and open transactions with period-by-period proof.

Plan my Sage 200 migration

See Support Data

Source

Sage 200 on SQL Server

EXTRACTION

Read-only SQL Server, or a SQL Server backup we restore

Manufacturing data

13 supported

DATA DOMAINS

Sage 200 migration with lot-tracked assemblies and BOMs

WHY NOW

Jul 31, 2025

Last date to request a licence extension key for older Sage 200 Professional versions

Older perpetual Sage 200 versions now need a move to subscription to keep running, and each release is supported for about three years. If you're facing an upgrade anyway, NS90 makes NetSuite the alternative.

Source: Sage UK Knowledgebase (UK Sage 200 Professional)

// Supported Data Domains

13 Sage 200 data domains, mapped field by field to NetSuite

Domains with solid dots have a proven field-level mapping from Sage 200 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

ARCUST

Item

ICITEM (inventory, assembly, lot-numbered)

Bill of materials

PEBMHD · PEBMDT

Vendor

APVEND

Supplier item

ICSUPL

Transaction

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

Sales order

Sales orders

Credit memo

AR credits

Vendor bill

AP invoices

Work order

Production orders

Invoice

AR invoices

Purchase order

Purchase orders

Vendor credit

AP credits

Balances & files

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

Trial balance

GL by period

Choose your depth

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

Available

What to plan for on Prophet 21

The Sage 200 details that make or break a migration

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

Fast extraction, slow mapping

A full Sage 200 SQL extract takes a few hours. The real work is mapping your new chart of accounts, item types and terms, so we start there first.

Vendors, then items, then the rest

Loads run in dependency order: vendors and terms, then items and bills of materials, then transactions.

Item types decided per item

Inventory, assembly, lot-numbered assembly and other-charge items are classified with you and loaded to the matching NetSuite item type.

New values in sheets, not live tables

Mapping inputs such as new GL accounts, classes or product lines are collected in sheets, so they don't change between extracts.

Fiscal calendar re-based

If you're moving from an October year-end to a calendar year, history is re-based so each period lands in the right NetSuite period.

Replenishment set on purpose

Reorder points or planning settings are agreed per item before load, so purchasing works on day one.

BOM revisions named consistently

Bills of materials load with a consistent revision naming convention, so engineering changes stay traceable.

GTINs and aliases kept

Barcodes and item aliases carry across, so warehouse and customer references still match.

Vendor terms harmonized

Payment terms are compared and mapped before vendors load.

Legacy codes kept

Legacy vendor and item codes are stored in NetSuite fields for search.

Unmapped GLs caught early

Accounts without a mapping are listed before trial balances load.

Parallel item workstreams

Assemblies, lot-numbered assemblies and BOMs load in parallel once items are validated.

How NS90: Migrate works

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