GP Dynamics GP → NetSuite

Move Dynamics GP to NetSuite before support ends

Microsoft ends support for Dynamics GP (Great Plains) on December 31, 2029. We move your companies, customers, vendors, items, open balances and full history into NetSuite, and check every record against GP before you go live.

Book a GP migration call Get a migration plan
Full history, not summaries
Every record checked against GP
Sandbox rehearsal before go-live
Trial Balance Comparison Reconciled

73

Periods

73

Reconciled

0

Discrepancies

Ties out
PeriodSourceDestVar
  • Jun 48,200.00 48,200.00 $0.00
  • Jul 51,940.00 51,940.00 $0.00
  • Aug 47,310.00 47,310.00 $0.00
  • Sep 52,008.00 52,008.00 $0.00

GP support ends in

1,147 days

Announced Sep 2024 Dec 31, 2029

Security patches end Apr 30, 2031 · Microsoft

The deadline

Microsoft's timeline for Dynamics GP.

Microsoft announced the end of support in September 2024, then moved the date to December 31, 2029 so GP customers can meet payroll and tax obligations for the full year. A migration needs a rehearsal and a reconciliation before go-live, so plan the cutover well ahead of that date.

Dynamics GP end of life: what each date changes
Plan your cutover Book a call

  1. Sep 25, 2024

    End of support announced

    Microsoft sets the date and points GP customers to Business Central.

  2. Apr 1, 2026

    Closed to new customers

    The last day new customers could license GP.

  3. Dec 31, 2029

    Support ends

    No more product updates, tax and regulatory updates, or technical support.

  4. Apr 30, 2031

    Security patches end

    Hosted GP licensing (SPLA) is also expected to end.

Sources (Microsoft): GP lifecycle, end of support, GP and SL migration options

Your options

Two ways off Dynamics GP.

Microsoft points GP customers to Dynamics 365 Business Central. If NetSuite is on your list, this is how the history comes across.

Microsoft's path

Business Central, with Microsoft's migration tool

  • General ledger history arrives as summary transactions
  • Detailed history only as an optional snapshot, kept in separate tables
  • Microsoft's recommended path for GP customers

Source: Microsoft Learn, migrate Dynamics GP data to the cloud

With SuiteMigration

NetSuite, with every record checked

  • The original invoices, bills and payments, as native NetSuite records
  • Every record checked against GP, with a report you can sign off
  • A full rehearsal in a NetSuite sandbox before go-live
  • Every GP company as a subsidiary of one NetSuite OneWorld account
Book a GP migration call
What you get

See every record land before you go live.

Every migration ends with these reports. Shown here for our sample company: 4,127 customers and 217,359 transactions.

Push Result Report Production
Customers 4,127

100% success

Vendors 2,340

100% success

Items 487

100% success

Employees 52

100% success

Invoices 124,812

100% success

Bills 85,541

100% success

Push result: every record and its status in production.
Per-Record Audit All matched
TypeRecordAmountStatus
  • Customer Acme Manufacturing Co. 12,400.00 ✓
  • Vendor Staples Business Advantage 1,280.50 ✓
  • Bill BILL-2291 980.00 ✓
  • Invoice INV-10482 3,650.00 ✓
  • Payment PMT-5537 3,650.00 ✓
Records audited 217,359 / 217,359
Per-record audit: each record checked against the source.
Get a migration plan
What moves

Every GP module has a home in NetSuite.

Customers, vendors, items, open balances and history come across as NetSuite records. Customizations and custom reports don't move. Plan to rebuild them in NetSuite or retire them.

Map your GP setup with us
In Dynamics GP In NetSuite

  • General Ledger

    Chart of accounts and segments

    Accounts, departments, classes and locations

  • General Ledger

    Open and historical years

    The original transactions

  • Receivables Management

    Customers and open invoices

    Customers and open invoices

  • Payables Management

    Vendors and open bills

    Vendors and open bills

  • Inventory Control

    Items

    Inventory, non-inventory and service items

  • Sales and Purchase Order Processing

    Open orders

    Sales orders and purchase orders

  • Fixed Asset Management

    Asset records

    Fixed Assets Management

  • Multicurrency Management

    Currencies and exchange rates

    Multiple currencies

  • Company databases

    Each GP company

    A subsidiary in NetSuite OneWorld

The process

Four steps from GP to NetSuite.

  1. 01

    Plan

    We agree which companies, records and years move, and a cutover date with room before 2029.

  2. 02

    Map

    We map your GP accounts, segments and records to your NetSuite setup.

  3. 03

    Rehearse

    Everything loads into a NetSuite sandbox first, so problems surface there.

  4. 04

    Check and go live

    We check every record against GP, then load production at your cutover.

Get a migration plan Book a call
Customer story · QuickBooks Online to NetSuite

30 QuickBooks files. One NetSuite instance. No spreadsheet marathon.

Vista Partners moved a venture capital client's 30+ investment entities into a single NetSuite instance with SuiteMigration. Many GP companies to one NetSuite account is the same kind of consolidation.

Read the story

FAQ

Dynamics GP to NetSuite migration: common questions

Quick answers to what finance teams ask first.

On December 31, 2029. After that, Microsoft provides no product updates, no tax or regulatory updates and no technical support. Security patches continue, only if needed, until April 30, 2031. Microsoft first announced September 30, 2029, then moved the date so GP customers can meet payroll and tax obligations for the full year.
Product updates, tax and regulatory updates and technical support stop after December 31, 2029. Security patches stop after April 30, 2031, the same day Microsoft expects GP licensed through hosting providers (SPLA) to end. A business still on GP after that runs it unsupported and unpatched.
Microsoft recommends its own Dynamics 365 Business Central and provides a cloud migration tool for it. That tool brings general ledger history across as summary transactions. Detailed history comes only as an optional snapshot kept in separate tables. If you're also looking at NetSuite, compare the two on consolidation across your companies, the history you want to keep, and the full cost over several years, migration included.
GP companies usually become subsidiaries. The chart of accounts and its segments, customers, vendors, items, open receivables and payables, open orders, fixed assets, currencies and as much general ledger history as you choose all have a home in NetSuite. Customizations and custom reports don't move. Plan to rebuild them in NetSuite or retire them.
Yes. History can come across as the original transactions, with their customers, vendors and items, or as one journal entry per account per period. Detail takes longer to load and check, but it means you don't keep GP running just to look things up after Microsoft stops patching it.
In NetSuite OneWorld your GP companies become subsidiaries of one account, and NetSuite rolls them up into consolidated reports. A company you keep in GP only for history or testing usually doesn't need one.
It depends on how many companies you run, which modules you use and how much history moves. Every migration includes a sandbox rehearsal and a full check against GP before go-live, so pick a cutover date with room to spare before December 31, 2029.
Yes. Great Plains is the product's earlier name, and many teams still use it.
Still have questions? Book a call

Dates and Business Central details from Microsoft: GP lifecycle, end of support, migration options, Business Central GP migration.

Get started

Plan your Dynamics GP migration.

Tell us how GP is set up. We'll plan the move to NetSuite with you and pick a cutover date with room before support ends.

  • Which companies, modules and records move
  • How much history to bring, and at what detail
  • A sandbox rehearsal and a full check before go-live

Prefer to talk first? Book a GP migration call

Get a migration plan