Purpose-built dynamics gp data archival for Great Plains. Open-format Parquet on cloud object storage, WORM immutability for SOX and IRS Pub 583, per-class retention rules, sub-second query without an active GP licence. Decommission GP without losing your history.
Microsoft has put GP into maintenance mode. Mainstream support ended September 2025. The bill for keeping a full GP environment alive just for history-only lookups gets harder to justify every year.
Great Plains has been a workhorse SMB and mid-market ERP for two decades. Tens of thousands of US distributors, non-profits, service firms and light manufacturers carry 10–20 years of posted GL transactions, AP voucher history, AR apply detail, SOP/POP shipment and receipt history, fixed asset depreciation, payroll register and 1099/W-2 history. That history is required for IRS retention, SOX trace, vendor 1099 amendments, customer dispute investigations and employment verification.
Microsoft's lifecycle decision changes the economics. Mainstream support ended in September 2025; extended support runs through April 2031, but it's extended support — no new functionality, increasingly expensive partner support contracts, vanishing Dexterity developer pool, ISV add-on partners winding down their GP products. Paying full per-user GP licence and partner maintenance for the privilege of occasional historical lookups becomes harder to defend with every annual renewal.
Syntra ETL's dynamics gp data archival breaks the link. Historical GP data moves to cloud object storage in open Parquet format, with hash-signed manifests, WORM immutability, per-class retention rules and a federated query layer that finance, audit and tax can use without firing up GP. The active GP environment can be decommissioned (or shrunk to a much smaller footprint) without losing a single byte of the history that compliance and the business actually need.
Six pillars that move dynamics gp data archival from 'a folder of CSVs on a NAS' to 'audit-ready compliance product'.
Apache Parquet — open, columnar, compressed, partitioned. No proprietary archive format that nobody can read in 7 years. Direct query from Athena, Synapse, BigQuery, Trino, DuckDB.
S3 Object Lock, Azure Blob Immutable Storage, GCS Bucket Lock. Once written, data cannot be modified or deleted for the policy-defined retention window. SOX and IRS substantiation.
Every partition signed at write-time. Read-access logged with timestamp and accessor. Audit can prove the data has not been tampered with — and prove who accessed it when.
Policy-driven retention per data class: 7-yr IRS for GL/AP/AR/sales-tax data, 4-yr federal for payroll, longer for some states. Automatic tier transition and policy-driven purge.
Hot-tier data on S3 Standard / Azure Hot / GCS Standard tier with partition pruning and predicate pushdown. Most lookups return in under a second.
Unified query layer across every archived company DB. Scope to one company or federate across all. Account framework variations handled transparently.
From discovery to live archive — typically 6–10 weeks for full-scope multi-company GP, faster for single-company or scope-limited archives.
Discovery enumerates GP company DBs, catalogs every history table by row count and date range, identifies ISV add-on data and Dexterity custom fields. Compliance, finance and legal agree per-class retention rules (IRS, SOX, payroll, GDPR, state sales-tax).
Cloud object storage configured (S3 / Azure Blob / GCS / OCI), WORM immutability enabled per retention class, hot/cold tier transition rules defined, partition strategy designed (company / fiscal year / table), access policies and audit logging configured.
Full historical extract across every company DB, all in-scope history tables, all ISV add-on tables, all Dexterity custom fields. Parquet partitions written with hash-signed manifests. Row-count and sum-aggregate reconciliation pack issued.
Federated query layer (Athena / Synapse / Trino) configured with views modeled on familiar GP query patterns. Self-serve UI for finance/audit/tax that mirrors SmartList query semantics. Power user access via SQL or BI tool of choice.
If GP remains in production, incremental delta archive runs on schedule. If GP is being decommissioned, final delta + GP read-only + GP environment shutdown sequenced. Signed audit log of the full archive lifecycle delivered.
The specific business needs that drive customers to dynamics gp data archival — every one of them tied to a measurable cost-avoidance.
Active GP per-user licence plus partner support contract typically runs $30k–$200k/yr depending on user count. Archive enables full decommission and recovers that spend annually.
Mainstream support ended Sept 2025. Extended support runs to April 2031 but is increasingly expensive. Archive lets you exit the lifecycle clock on your own schedule.
External auditors arrive expecting trace from GL to source document. Archive preserves the chain in queryable, signed form — no need to spin up old GP versions to satisfy audit requests.
Vendor 1099 amendments and former-employee W-2 reissues require access to historical payroll and AP data for years after retirement. Archive serves the query in seconds without GP.
Discovery requests for historical financial data are routine in commercial litigation. Archive's queryable, immutable format satisfies discovery far more cleanly than .bak restores.
Selling a business unit but need to retain the records? Archive holds the divested company's history independently of the buyer's IT environment for the full retention window.
Dynamics gp data archival is the process of moving historical Great Plains data — posted GL transactions (GL30000), AP voucher history (PM30200), AR apply history (RM30201), SOP/POP history, fixed asset history, payroll history — into a long-term, queryable, immutable cloud archive that can be consulted for the full IRS Pub 583 7-year retention window without requiring an active GP licence. A SQL Server .bak file is not an archive — it's a backup. You cannot query a .bak file directly, you cannot prove read-access integrity, you cannot satisfy SOX trace from cloud archive back to GP source. Syntra ETL's dynamics gp data archival product stores data in open-format Parquet on cloud object storage with hash-signed manifests, immutable WORM storage tiers, and a federated query layer that lets finance, audit and tax run lookups without firing up GP.
IRS Pub 583 small-business retention is 7 years for tax records; state sales-tax retention varies 3–7 years by jurisdiction. SOX requires 7-year retention with auditable trace from GL entry to source document. Syntra ETL's dynamics gp data archival preserves the full chain: GL30000 journal line → PM30200 voucher distribution → PM30200 voucher header, with every link hashed and signed. The archive sits on WORM (write-once-read-many) cloud object storage tiers (S3 Object Lock, Azure Blob Immutable, GCS Bucket Lock) so the data cannot be tampered with for the retention window. Every read access is logged with timestamp and accessor identity — that's the substantiation auditors actually need.
For history-only workloads, yes — and this is exactly why customers archive. Once GP has been moved to read-only and the cutover to Fusion is complete, the only remaining business need is historical lookup (vendor history for 1099 amendments, customer apply history for old disputes, GL journal trace for audit, payroll history for employee verification). Maintaining a full GP production environment plus per-user licences for those occasional lookups is wasteful. Dynamics gp data archival replaces that with a queryable cloud archive that costs a fraction of the per-user GP licence and partner support contract — and is faster to query than GP because the archive sits on cloud columnar storage tuned for analytical query.
Multi-company GP installations are the rule, not the exception — three to twelve company databases is common in distribution and non-profit. Syntra ETL's dynamics gp data archival enumerates active companies from the DYNAMICS system database (SY01500 Company Master), archives each company's history into its own partition in cloud storage (partitioned by company_id, fiscal_year, table), and exposes a unified query layer that can scope queries to a single company or federate across all. Account framework variations across companies are captured in the archive metadata so historical reporting handles segment-width and segment-count differences transparently.
Tier and retention rules per data class. Tax-relevant data (GL30000, PM30200 for 1099 source, sales-tax-driving SOP30200) defaults to 7-year IRS-aligned retention on hot tier for fast query, then transitions to cold tier (S3 Glacier Deep Archive, Azure Archive, GCS Archive) for the remainder of the legal hold. Payroll history follows employment-record rules (4 years federal, longer in some states). Customer/vendor master and operational history follow business need (typically 7 years matching tax). Personally identifiable employee or customer data follows GDPR / state-privacy-law rules and is purged or redacted on the legally required schedule. All rules are policy-driven and audited.
Yes. The archival extractor uses the same dynamics gp data extraction tool engine described elsewhere on the site, which walks the full SQL Server schema and discovers ISV add-on tables (Mekorma, Greenshades, Integrity Data, Rockton, Encore) plus Dexterity-added custom fields on native tables. ISV-resident data is archived alongside native GP data with the ISV vendor flagged in metadata. Custom fields are archived as additional columns on the corresponding native table partitions. This matters because much of the actual business context (payment routing rules from Mekorma, tax-filing detail from Greenshades, custom approval audit from VBA) lives in ISV or custom-field territory.
Sub-second for typical lookups on hot-tier data: 'show me all PM30200 vouchers for vendor X in fiscal year 2022', 'show me the GL30000 journal trace for batch Y', 'show me the SOP30200 sales history for customer Z'. The archive sits on cloud columnar storage (Parquet) with partition pruning, predicate pushdown and result caching — queries that took minutes against GP SQL Server return in seconds because the storage is purpose-built for analytical access patterns. Cold-tier queries (older than the hot-tier window) take longer to thaw (minutes to hours depending on tier) but are explicitly the trade-off for cheap long-term storage of rarely-accessed data.
When the retention window expires (typically 7 years for IRS, longer for some payroll), retention rules trigger automatic purge of the corresponding partitions — with a signed audit log of what was purged, when, and by which policy rule. The purge is non-reversible by design (legally required) but is preceded by a configurable grace window during which finance/legal can intervene. For data subject to GDPR right-to-be-forgotten requests during the retention window, targeted record-level redaction is supported with full audit log. This is the difference between a backup (which has no concept of policy-driven retention) and a real dynamics gp data archival product.
Send us your GP company DB list, your retention policy and your target cloud platform. We will return a sized archive plan with per-class retention design, storage cost estimate and decommission timeline within 5 business days.