How to decommission Dynamics GP without losing your history

What must survive the shutdown

Decommissioning GP combines records management, accounting approval and technical shutdown work. Before the server goes off, move the required history into a format the business can still search and verify. Preserve:

• ✓The records your business must retain. Confirm the required companies, modules, years, notes and attachments instead of assuming that open balances are enough.
• ✓Record notes and descriptions. Twenty years of notes attached to customers, vendors, and documents. Inside GP these are effectively write-only; they still matter in a dispute.
• ✓Third-party and custom tables. Mekorma, Binary Stream, SmartList Builder, and anything custom. If you don't know what you have, find out before you plan anything else.
• ✓Evidence that the copy agrees with GP. Keep a report showing the source and archive counts and accounting totals.

Why a SQL backup is not an archive

Keep the SQL backups, but plan how people will use the records. A restore requires a compatible SQL Server and someone who understands GP tables such as RM30101 and RM20101. The backup preserves the source. A searchable archive provides routine access. See the SQL backup guide for a restore checklist.

The sequence that works

1. 01
   Assess the environment first. Identify the companies, history by module, transaction volume, third-party tables and data issues before agreeing the archive scope.
2. 02
   Extract a test archive during migration planning. Give users time to try real searches and compare the results with GP before cutover.
3. 03
   Extract the production archive the day GP is frozen. The final extract captures everything up to the last posting. Extraction runs unattended and is resumable if the connection drops.
4. 04
   Verify the archive before shutdown. Review the record counts and accounting totals while the source system is still available.
5. 05
   Run both in parallel for a few weeks. Answer real questions from the archive. When nobody reaches for GP anymore, shut it down. Cancel the VM, the SQL license, the backup job.

The verification step

Nobody should decommission anything on trust. Every ERPDataArchive extraction produces a reconciliation report: source and archive record counts; GL trial balances by fiscal year; AR and AP totals at cutover; inventory controls where included; and document counts by type and year. Your controller reviews that report before anyone agrees to turn the server off. If the totals do not agree, keep GP available while the differences are investigated.

The end state

When it is done, you keep the archive file, reader app and verification report on controlled storage. Staff search the archive without restoring a GP server, and analysts can connect Excel, Power BI or other reporting tools. Opening an existing archive does not expire. For the full cost comparison with keeping GP alive read-only, see what a GP data archive actually costs.