Retiring Dynamics GP means preserving agreed historical records and usable access before removing the source application dependency. For this scenario, prioritise open and history transactions, apply records and attached documents. Compare required reports and documents with source evidence, test permissions and obtain business acceptance before scheduling shutdown.

This guide covers the retirement questions, a mock-data ArchiveHub demonstration and the validation work needed to define a project scope.

The real cost of a read-only GP

Cost categories are a discovery checklist, not a guaranteed savings calculation. Verify support status, deployment, shared infrastructure and contract terms for the actual installation.

A GP install that nobody posts to still has to be kept alive:

  • An ageing Windows and SQL Server stack. GP typically sits on a SQL Server version and a Windows Server release that are already, or soon will be, out of support. Upgrading them only to keep reading history is money spent on nothing.
  • GP licences and the client install. Someone still has to keep a working GP client on a machine, with the right service pack and the right add-on DLLs, or the company database simply won't open.
  • Security exposure. An unpatched SQL Server holding vendor bank details, employee Social Security numbers and payroll history is exactly the kind of system auditors flag.
  • Know-how. Finding a voided check or a 1099 adjustment in GP means knowing which window, which SmartList and which series to look in. That knowledge leaves with the GP administrator.
  • Ad-hoc reporting debt. Every year-end, tax notice or audit request turns into a custom SQL query against tables called PM30200 and RM30101 that only a few people understand.

Scope, versions and evidence

This is an illustrative workflow, not a customer case study. Confirm the source release, deployment, modules, customisations and extraction permissions before using the mappings below. Tables and report labels describe the demonstration catalogue; native-report equivalence has not been independently certified. Use agreed source reports and representative records for acceptance testing.

An archive is not a replacement for every operational feature of the retired ERP. Document required historical tasks, excluded functions and any archive-derived calculations.

Historical data to scope for Dynamics GP

ArchiveHub archives GP the way GP stores itself. The general ledger comes across as GL20000 (Year-to-Date Transaction Open) and GL30000 (Account Transaction History), with GL10110 and GL10111 for the current and historical account summaries, GL00100 and GL00105 for the account master and account index, and GL00200 / GL00201 for budgets. Posting history comes with SY30500 and the audit trail codes in SY01000, so the batch that created a journal entry can still be traced.

Payables keep their open/history split: PM20000 for open transactions, PM30200 for paid transaction history, PM30300 for apply history and PM30600 for distribution history, with PM00200 and PM00300 for vendors and addresses and PM00204 for the 1099 period detail. Receivables follow the same pattern with RM20101, RM30101, RM30201 and RM30301. Sales Order Processing (SOP10100, SOP30200, SOP30300), Purchase Order Processing (POP10100, POP30100, POP30300, POP10500), Inventory (IV00101, IV00102, IV30200, IV30300), Bank Reconciliation (CM20200, CM20300, CM20500), Fixed Assets (FA00100, FA00200, FA00902) and US Payroll (UPR00100, UPR30100, UPR30300) are all there too.

In the demonstrated scope, each field keeps its GP technical name and description, so users who remember DOCNUMBR, VENDORID or JRNENTRY can still search by them in ad-hoc queries.

Aged trial balances need special care. GP produced its Historical Aged Trial Balance from document and apply history at run time, not from a stored table, so ArchiveHub rebuilds quarter-end aging from the RM and PM documents and applies and stores it in two clearly labelled archive tables (AH_RM_AGED_TB and AH_PM_AGED_TB). These are derived data and are marked as such, not presented as native GP tables.

Explore the demonstration

Account Transactions list in ArchiveHub Account Transactions: GP journal entry lines from open and history years in one list, filterable by account, period and source. ArchiveHub demonstration using mock data; not a native ERP screen or customer implementation.

Account transaction detail page in ArchiveHub Account Transactions detail: a single archived GP journal entry opened from the list. ArchiveHub demonstration using mock data; not a native ERP screen or customer implementation.

Historical Aged Payables in ArchiveHub Historical Aged Payables: vendor balances aged at each quarter-end as-of date. ArchiveHub demonstration using mock data; not a native ERP screen or customer implementation.

Explore the report reference catalogue

These mappings identify intended business workflows, not certified one-for-one equivalents. Confirm availability, source coverage, filters, currencies, dates and calculations for the selected release and implementation.

General Ledger

  • Account Transactions: reference workflow: the SmartList Account Transactions and Journal Entry Inquiry (GL20000, GL30000)
  • Trial Balance: reference workflow: the Detailed/Summary Trial Balance report and Summary Inquiry (GL10110, GL10111), with the year-end close shown apart
  • Budget vs Actual: reference workflow: Budget Summary Inquiry and the Budget Trial Balance (GL00200, GL00201)
  • Posted Batches: reference workflow: Series Posting history and the Audit Trail Code inquiry (SY30500, SY01000)
  • Reconcile to GL: reference workflow: Reconcile to GL, subledger activity against the control account by period; confirm the required source data and reconciliation logic before offering this report

Purchasing

  • Payables Transactions: reference workflow: SmartList Payables Transactions and Payables Transaction Inquiry (PM20000, PM30200, PM30600)
  • Payables Checks: reference workflow: the Payables Check Register and Payment Inquiry, including voided checks (PM30200, PM30300)
  • Historical Aged Payables: reference workflow: the Historical Aged Trial Balance (Payables) at quarter-end as-of dates
  • Vendors: reference workflow: Vendor Maintenance, Vendor Inquiry and SmartList Vendors (PM00200, PM00201, PM00300)
  • Purchase Orders: reference workflow: Purchase Order Inquiry and SmartList Purchase Orders (POP10100, POP30100, POP10500)
  • Received Not Invoiced: reference workflow: the Received/Not Invoiced Report, tied to Accrued Purchases (POP10500, POP30300)

Sales

  • Receivables Transactions: reference workflow: SmartList Receivables Transactions and Receivables Transaction Inquiry (RM20101, RM30101, RM30301)
  • Cash Receipts: reference workflow: Cash Receipts Inquiry and the Cash Receipts Journal (RM30101, RM30201, CM20300)
  • Historical Aged Receivables: reference workflow: the Historical Aged Trial Balance (Receivables) at quarter-end as-of dates
  • Customers: reference workflow: Customer Maintenance, Customer Summary and SmartList Customers (RM00101, RM00102, RM00103)
  • Sales Documents: reference workflow: Sales Transaction Inquiry and SmartList Sales Transactions (SOP10100, SOP30200, SOP30300)
  • Back Orders: reference workflow: Sales Back Order inquiry and Fill Rate (SOPTYPE 5 in SOP10100, SOP30200)
  • Sales Item Analysis: reference workflow: the Sales Analysis report and Item Sales Summary, gross margin by item and year (SOP30300, IV30300)

Inventory

  • Items: reference workflow: Item Maintenance, Item Vendors, Price List and SmartList Items (IV00101, IV00103, IV00108)
  • Item Transactions: reference workflow: Item Transaction Inquiry, the Stock Ledger and SmartList Inventory Transactions (IV30200, IV30300)
  • Stock Status: reference workflow: Historical Stock Status and Item Stock Inquiry at the cut-off, with value tied to the Inventory account (IV00102, IV30300)
  • ABC Analysis: reference workflow: ABC Analysis and inventory turnover by item on annual usage value (IV00101, IV30300)

Bank Reconciliation

  • Checkbook Register: reference workflow: Checkbook Register Inquiry and SmartList Bank Transactions (CM20200, CM20300)
  • Bank Reconciliation: reference workflow: Reconcile Bank Statements, the Reconciliation Journal and the Cleared and Outstanding Transactions reports (CM20500, CM20501)

Fixed Assets

  • Fixed Assets: reference workflow: Asset General Information, Asset Book Inquiry and SmartList Assets (FA00100, FA00200, FA00700)
  • Depreciation Detail: reference workflow: Fixed Assets Depreciation Detail and the FA to GL Reconciliation (FA00902)

Payroll

  • Employees: reference workflow: Employee Maintenance, Employee Summary and SmartList Employees (UPR00100, UPR00102, UPR00400)
  • Payroll Check Register: reference workflow: the Payroll Check Register and Payroll Check Inquiry (UPR30100, UPR30300)
  • Payroll Summary: reference workflow: the Payroll Summary and Department Wage Report, payroll distribution against the GL (UPR30401)

Tax

  • 1099 Details: reference workflow: Print 1099 and the 1099 Details inquiry by vendor and tax year (PM00204)
  • Tax History: reference workflow: the Tax Detail History and Tax Summary reports, with return status (TX30000, TX00201)

Source documents stay attached

Document types below illustrate the intended scope. Include source attachments and external repositories explicitly, and test retrieval and record linkage before decommissioning.

Dynamics GP supports Document Attachment. An archival scope must cover the relevant attachments and any external document repositories, as well as their links to business records. Payables invoices, SOP invoices and purchase orders carry their PDFs, bank statements are attached to their reconciliations, and customer, vendor, employee and fixed asset records keep their files. Proving a 2019 invoice means opening it, not hunting through a file share.

Beyond the reports

Confirm these capabilities, configuration requirements and limits during the demonstration and scope review; the report catalogue alone does not validate them.

  • Ad-hoc query builder over the configured archived GP table, showing GP field descriptions and suggesting the usual joins, such as PM30200 to PM00200 on VENDORID.
  • Retention rules with approved purge, so payroll and personal data can be removed on schedule while the general ledger stays.
  • Legal hold to freeze specific vendors, employees or periods.
  • Personal-data governance: agree the lawful retention, access and deletion requirements with the responsible privacy and records teams. Product features alone do not establish regulatory compliance.
  • Access controls: define and test permissions for the required companies, records and sensitive fields. Do not assume that system-level roles reproduce the original ERP permissions, particularly for payroll and HR data.
  • OData feeds into Excel, Power BI and SAP Analytics Cloud for trend reporting across the old and new ERP.

How a GP decommissioning runs

  1. Extract each GP company database, plus the system tables needed to read it, with table and field descriptions.
  2. Validate. Row counts table by table, then balances that tie out: payables and receivables history to their control accounts, Fixed Assets to the GL, inventory value to the Inventory account and the trial balance to GL10110/GL10111 period totals.
  3. Parallel read access. Accounts payable, payroll and audit users check their usual lookups in ArchiveHub while GP is still there.
  4. Retire after acceptance. Obtain documented sign-off for data reconciliation, document retrieval, user access, retention and legal holds, recovery and remaining integrations. Retire only the approved components; shared infrastructure may still be needed. End or reduce subscriptions, licences and support only where the contract permits. Budget for archive operation and any residual costs.

Questions about Dynamics GP retirement

Does a GP archive need document extraction?

Yes when documents are in scope. GP supports Document Attachment, and implementations may also use external stores. Inventory both, preserve record links and test retrieval after extraction.

How should historical GP aging be tested?

Use agreed as-of dates and reconcile the relevant documents and application history to retained source reports. Clearly label reconstructed aging and document differences in date, currency or void handling.

What does this ArchiveHub demonstration prove?

The screenshots illustrate how selected records can be presented using mock data. They do not prove production completeness, customer outcomes or parity with every Dynamics GP report. Request a demonstration against your own approved scope and acceptance cases.

Related retirement resources

For the broader project approach, see Legacy application retirement planning. To evaluate how users will find transactions, follow relationships and retrieve documents, explore archived data reporting. These resources complement this Dynamics GP-specific scope rather than replace source-system validation.

Evidence and further reading

The report catalogue and screenshots originate from an internal mock-data demonstration. They are not vendor certification or customer implementation evidence.

Use Microsoft Dynamics documentation to locate the documentation for the installed release. This is a documentation entry point, not verification of every table or report mapping in this article.

Microsoft documents GP Document Attachment in its Dynamics GP R2 feature guide. Include attachments in discovery rather than assuming GP contains only relational records.

Fixed-price Dynamics GP retirement engagement

ArchiveHub offers a fixed-price engagement for Dynamics GP retirement and historical data access, based on an agreed scope, deliverables and acceptance criteria. Request a scoped proposal covering your source systems, data, documents, reporting and validation requirements. The proposal should specify included services, exclusions, ongoing platform or hosting charges, and how scope changes will be handled.

Discuss your Dynamics GP retirement requirements with ArchiveHub

Microsoft Dynamics GP is a trademark of its respective owner. ArchiveHub is not affiliated with or endorsed by Microsoft.