Consumer-grade dynamics gp legacy data access for small-business owners, bookkeepers, accountants and IRS/HMRC examiners. Query every active and historical GP record years after the SQL Server stack is gone — without paying perpetual GP licence and Windows Server fees.
GP retirement does not retire your retention obligation. IRS Pub 583, HMRC VAT records, state sales-tax, GDPR data-subject access — they all keep asking for records years after GP is gone.
Dynamics GP has been the workhorse SMB ERP for two decades. Tens of thousands of small businesses, professional-services firms, non-profits and light manufacturers run their GL, AP, AR, payroll and inventory inside Great Plains, often across multiple company databases representing legal entities, locations or business lines. When the time comes to retire that GP installation — because the business has been acquired, because Microsoft is sunsetting GP versions, or because the per-user enhancement-plan economics no longer make sense — the records inside those databases do not retire with the software.
The IRS expects 7-year retention of small-business tax records (Pub 583). HMRC expects 6-year retention of VAT and corporation-tax records. German GoBD pushes to 10 years for fiscal records. State sales-tax authorities require 3–7 years depending on jurisdiction. GDPR data-subject access can land at any time and demand a vendor or customer's full transaction history. Without dynamics gp legacy data access, the only way to meet those obligations is to keep the GP SQL Server stack alive, patched and licensed — which often costs USD 8K–40K/year for a system that is no longer producing transactions.
Syntra ETL extracts every active and historical row from the source GP databases, lands it in a cloud-archive format, indexes it for query, and surfaces it through a consumer-grade search UI that any bookkeeper, owner, accountant or external examiner can use without GP knowledge. The SQL Server, Dexterity runtime, Modifier resources and ISV add-ons all decommission cleanly. The records stay searchable for the full retention window.
A consumer-grade search UI on top of every historical GP record, backed by signed audit evidence and accessible without GP skills.
Type a vendor name, invoice number, check number, customer name or date range. Results in seconds across every active and historical company database. No SQL, no GP forms, no Dexterity required.
GL30000 journal line → PM30200 voucher distribution → PM30200 voucher header → PM10500 voucher document → original invoice attachment. The full audit chain stays clickable years after GP is decommissioned.
Result sets export with the audit-evidence metadata pack (extract timestamp, hash signature, read-access log). Accountants accept it as substantiation. Examiners accept it as audit evidence.
Filter by company DB, search across all companies, roll up totals across companies. SY01500 company metadata preserved so company names, fiscal calendars and addresses stay accurate at the moment each record was created.
Every search and every export logged: who, what, when, from where. The audit log itself is hash-signed and append-only — examiners get evidence that examiners themselves did not see records they should not have.
USD 1.2K–6K/year typical vs USD 8K–40K/year keeping GP live for query. Pays back the migration in year one for most small-business installations.
A repeatable 4–8 week process to retire a GP installation without retiring your audit substantiation. Multi-company installations scale linearly with company DB count.
Enumerate active company DBs from DYNAMICS. Row-count inventory per module per company. Custom Dexterity field catalog. ISV add-on inventory. Retention obligation review (IRS, HMRC, state sales-tax, GDPR) per record type.
SQL Server direct vs eConnect vs Web Services transport choice. Object storage destination (S3, Azure Blob, GCS, OCI). Partition strategy (company / fiscal year / table). Access model (role-based, SSO, MFA).
Parallel extract across every company DB. Parquet output with hash-signed manifests per partition. Search index build (full-text on descriptions, numeric on amounts, date-range on document dates). Document attachments captured if present.
Consumer-grade search UI configured with the master/transaction model of the specific GP installation. Drill-down paths configured. Export formats configured. Audit log destination configured.
Owner / accountant / bookkeeper UAT. Sample audit-evidence packs reviewed by internal audit or external accountant. IRS/HMRC retention obligations explicitly signed off per record type. Read-access log validated.
Final delta extract from any still-live GP DB. SQL Server backups taken and stored offline. GP installation decommissioned. Cloud archive becomes the system of record for the full retention window. Cost savings start immediately.
The system is built for the actual humans who will use it — not for GP power users who no longer exist.
An owner-operator who has not opened GP in 3 years needs to know what they paid Vendor X in fiscal year 2022. Three clicks: vendor search → period filter → export to PDF. Done.
Bookkeeper needs 1099 substantiation for the 2023 tax year. Vendor search → 1099 history filter → export to Excel with original voucher detail. Drill-through to original invoice attachment preserved.
Examiner needs every sales transaction with tax in the state of Texas, fiscal years 2020 through 2024. Date-range + tax-jurisdiction filter → export with audit-evidence pack including extract timestamp and hash signature.
External accountant preparing year-end accounts needs AR aging at a specific historical date. Date-as-of filter → aging output. Matches what the live GP would have produced — same calculation logic, same audit trail.
Customer X requests their full data footprint under GDPR Article 15. Customer search → all related records across RM, SOP, payments, communications → export with read-log capturing the disclosure.
Buyer's diligence team needs 7 years of financial history on a sold-off entity whose GP company DB was retired. Cloud archive opens read-only access to diligence team with read-log preserving who looked at what.
Dynamics gp legacy data access is the practice of letting non-technical consumers — small-business owners, accountants, bookkeepers, IRS or HMRC examiners, internal finance staff — query historical Great Plains records years after the original GP installation has been retired or moved to read-only mode. The need is unavoidable: IRS Pub 583 mandates 7-year retention of small-business tax records, HMRC requires 6 years for VAT records, German GoBD demands 10 years for fiscal records, and state sales-tax retention varies 3–7 years. Without dynamics gp legacy data access, organisations either pay perpetual GP licence and SQL Server fees just to look up an invoice, or risk audit non-compliance when they cannot produce the substantiation an examiner asks for.
Syntra ETL extracts every active and historical row from the source GP SQL Server databases — GL30000 posted GL history, PM30200 voucher history, RM30201 receivables apply history, SOP30200/POP30100 sales and purchase order history, FA00100 fixed assets and book history, plus master data and Dexterity custom fields — and lands them in a cloud-archive format (Parquet on S3, Azure Blob, GCS or OCI Object Storage) indexed for query. A web-based search UI lets a small-business owner type a vendor name, invoice number or date range and get a result in seconds. The Dexterity runtime, SQL Server licence, Modifier resources and ISV add-ons no longer have to be maintained — but every record is still queryable for the full retention window.
Yes, and that is one of the highest-value use cases. A bookkeeper preparing 1099 substantiation for prior tax years, an accountant reconstructing a vendor balance for a prior period, a tax preparer pulling sales-tax detail for a state audit — all need dynamics gp legacy data access to GP records they did not author. The Syntra ETL legacy access UI is built for that consumer: search by vendor, customer, invoice number, check number, document date, period or any custom Dexterity field that was in scope at extract time. Result sets export to Excel, PDF or CSV. Drill-down from a GL journal line to the original AP voucher distribution to the original voucher header to the underlying invoice scan (if document attachments were captured) works without any GP knowledge required.
Audits arrive with little notice and force production of records often 5–7 years old. With GP in read-only or fully decommissioned state, dynamics gp legacy data access becomes the audit substantiation system of record. Every record in the archive carries a signed timestamp showing when it was extracted from the source GP database and a hash signature proving it has not been altered since extract. Read-access is logged: who looked at which record, when, from which IP. When an IRS or HMRC examiner asks for 'every transaction with vendor X between fiscal years 2019 and 2024', the query runs, the result set is exported with the audit metadata pack, and the examiner accepts it as the same evidence they would have received from a live GP query.
Everything that was in the GP company databases at the point of extract. General Ledger: GL00100 account master, GL30000 posted history with full drill to source. Payables Management: PM00200 vendor master, PM30200 voucher history, PM30300 payment history, 1099 history. Receivables Management: RM00101 customer master, RM30101 invoice history, RM30201 apply history, cash receipts. Inventory: IV00101 item master, IV30200 transaction history, cost layers. Sales Order Processing: SOP30200 sales document history, SOP30300 line detail. Purchase Order Processing: POP30100 PO history, POP30110 line detail. Fixed Assets: FA00100 asset master, book history, depreciation history. Bank Reconciliation: CM20100 transactions and statement detail. Plus Project Accounting, Payroll (US/Canadian), and any active Dexterity custom fields captured during extract.
Yes, and the multi-company model is preserved end-to-end. GP's pattern of one SQL Server database per company (TWO, FAB1, customer-specific company codes, plus the shared DYNAMICS system database) is extracted in parallel during the initial load and stored in the cloud archive partitioned by company code. The legacy access UI lets a consumer filter by company, search across all companies at once, or roll up totals across companies for consolidated views that GP itself never offered natively. SY01500 company master metadata is preserved so company names, addresses and fiscal calendars stay accurate even when the consumer is querying 8 years after that company was sold off or merged into another entity.
Dynamics gp legacy data access typically costs 80–90% less than maintaining a live GP installation. A small-business GP environment running for read-only query carries SQL Server licensing (Standard or Enterprise edition), Windows Server licensing, a Microsoft Dynamics enhancement plan if still under support, partner support contracts, infrastructure (VM or on-prem hardware) and the human cost of patching, backing up and security-hardening the stack. That typically runs USD 8K–40K/year for a small-business GP install — just to look up old invoices. Cloud-archive legacy access typically runs USD 1.2K–6K/year covering Parquet storage on cheap object tiers, the search UI, and authenticated read access. The break-even versus keeping GP live arrives in the first year.
For a typical single-company or 2–4-company GP installation, end-to-end setup of dynamics gp legacy data access runs 4–8 weeks. Week 1: assessment (company DB inventory, table-level row counts, ISV add-on inventory, custom Dexterity field catalog). Weeks 2–4: bulk extract across every active company DB, with watermarked incremental refreshes for any GP installation that is still live during the project. Weeks 4–6: cloud archive build, indexing, search UI configuration, role-based access (finance staff vs auditor vs read-only consumer). Weeks 6–8: user acceptance testing, IRS/HMRC retention sign-off, decommission planning. The GP installation can then be safely decommissioned with confidence that every audit retention obligation is met.
Get a 30-minute scoping call. We'll walk through your company DB inventory, retention obligations, target user audience and decommission timeline — and give you a 4–8 week setup plan with concrete cost savings.