Dynamics GP

NS90: Migrate:

Microsoft Dynamics GP to NetSuite

Leave Dynamics GP. Keep every company, account and year you need.

NS90: Migrate reads your GP company databases directly, maps each one to a NetSuite subsidiary, rebuilds your chart of accounts as NetSuite segments, and proves every period ties out before you go live.

Plan my Dynamics GP migration

See Support Data

Source

Microsoft Dynamics GP (on-prem or hosted SQL Server)

EXTRACTION

Read-only SQL against each company database, or a restored SQL Server backup

DATA DOMAINS

18 supported

DELIVERED

6 GP migrations, plus a GP subscription-billing add-on

Depth

Options 2, 3 and 4

WHY NOW

Dec 31, 2029

Microsoft ends Dynamics GP product support, tax and regulatory updates

Security patches continue until April 30, 2031, and Microsoft is steering GP customers toward Business Central. Starting the NetSuite move now leaves time for a clean chart of accounts and a validated history, instead of a rushed cutover against a support deadline.

Source: Microsoft Dynamics GP lifecycle announcement

// Supported Data Domains

18 Dynamics GP data domains, mapped field by field to NetSuite

Every domain has a proven field-level mapping from Dynamics GP 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

RM00101

Contact

RM00102 · PM00300

Fixed asset

FA00100

Vendor

PM00200

Item

IV00101

Subscription & price plan

Binary Stream add-on

Transaction

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

Sales order

SOP10100 · SOP30200

Credit memo

RM20101

Purchase order

POP10100 · POP30100

Vendor credit

PM20000 · PM30200

Journal entry

GL20000 · GL30000

Invoice

RM20101 · RM30101

Customer payment

RM20101 · RM30101

Vendor bill

PM20000 · PM30200

Vendor payment

PM20000 · PM30200

Inventory quantity

IV quantities

Balances & files

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

Trial balance

GL30000 · GL00100

File attachments

Document links

Choose your depth

Bring as much Dynamics GP 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 Dynamics GP 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 2 Dynamics GP projects

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 3 Dynamics GP projects

What we’ve learned on Dynamics GP projects

The Dynamics GP details that make or break a migration

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

Every company database is its own source

GP keeps one SQL database per company plus a DYNAMICS system database. We catalog each company, map it to a NetSuite subsidiary first, and catch customer and vendor IDs that repeat across companies before they become duplicates.

Account index, not account number

GP transactions store an account index (ACTINDX). We resolve it through GL00105 into a harmonized chart of accounts, and refresh that crosswalk before every delta load so new month-end accounts never fall out.

Open, history and unposted tables

GP splits data into work, open and history tables. We read the right one per domain: open year from GL20000, prior years from GL30000, open AR from RM20101, open AP from PM20000 without voided documents.

Bill-in-advance documents

Unposted SOP documents can represent revenue already invoiced in advance. We identify them and load them so nothing is billed twice after go-live.

Wide tables over slow links

GP tables can run to about 400 columns, and extraction over VPN can time out. When it does, we work from a restored SQL Server backup instead of the live server.

Volume-aware loading

Above roughly 100,000 to 200,000 transaction headers we plan parallel load threads with SuiteCloud Plus. One GP client loaded 110,000 journal entries in about six hours.

Add-ons come along

Binary Stream subscription billing data such as billing accounts, price plans and subscriptions is mapped to NetSuite SuiteBilling records and loaded through REST.

Multicurrency and foreign companies

Companies kept in USD but reporting in CAD or SGD get their trial balances converted and reconciled per currency, and scoped explicitly up front.

Open AP without double counting

Open items post against an opening-balance entry that is then reversed, so open AP and the trial balance never count the same dollar twice.

Snapshot, then dedupe again

Master data changes between test cycles. With input from the customer, we re-run deduplication on a fresh snapshot about a week before go-live.

A golden GP mapping

Every GP project starts from our standard field-level mapping. Client-specific fields sit alongside it, never inside it.

History in NSAW, detail on demand

Closed GP history can live in NetSuite Analytics Warehouse with drill-down from NetSuite balances, keeping NetSuite lean without losing audit detail.

Attachments stay linked

Document attachments from GP add-ons are moved to your document store and linked back to the NetSuite record.

GP stores some dates as text

Some GP date fields are stored as text, and record relationships are enforced by the application rather than the database. We validate every join before load.

How NS90: Migrate works

The Dynamics GP details that make or break a migration

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