Acumatica Data Archival — Capture Every Entity, Cancel the Subscription

Acumatica data archival is the discipline of moving aged transactional history out of the live Acumatica tenant (or capturing it after migration to Fusion) into a long-term, immutable, query-ready repository. It matters for three reasons. First, finance and audit teams need 7+ years of GL, AP, AR, FA, project and inventory history for SOX, IRS, GAAP and construction-specific retention — but keeping it in live Acumatica is expensive. Second, after migration to Oracle Fusion, the Acumatica tenant becomes a six-figure annual carrying cost with no operational use. Third, archival is the only way to keep historical xRP custom field values, Generic Inquiry outputs and attached documents accessible without paying the running subscription.

A backup is a binary blob of the Acumatica SQL Server database, restorable only by spinning up an Acumatica instance with matching version, xRP customizations, integrations and credentials — a multi-week, six-figure recovery exercise that everyone hopes they'll never need. Acumatica data archival is the opposite: a query-ready repository where finance, audit, tax and operations search by customer, vendor, GL account, project or document number and get answers in seconds, without an Acumatica instance running anywhere. Backups satisfy IT continuity. Archival satisfies business continuity, audit defense and the actual day-to-day historical lookups.

Every entity that matters to a future audit, tax inquiry, customer dispute or operational lookup. Financial Management: GL journals, Account Class, Subaccounts, Branches, AP Bills, AR Invoices, Cash Management, Fixed Assets, Multi-Currency translations, Tax History. Distribution: SOOrders, POOrders, InventoryItems, Warehouses, Receipts, Issues, Lot/Serial. Manufacturing: BOMs, Production Orders, MRP history. Construction: Projects, Pay Apps (AIA), Subcontracts, Change Orders, Certified Payroll. Retail/CRM: Customer Master, Sales Orders, Returns, Leads, Opportunities. Plus every attached document, every xRP custom field, every Generic Inquiry definition and every Acumatica Report Designer report.

Attached documents are first-class citizens of the acumatica data archival design. Every document attached to a Pay App, Subcontract, AP Bill, AR Invoice, SOOrder, POOrder, Project or any other Acumatica entity is extracted with its original binary intact, hash-signed for tamper evidence, indexed by parent-entity ID, and stored in cloud object storage with KMS encryption and object-lock retention. AIA Pay App backups are particularly important for construction customers facing lien-rights challenges years post-completion — the archive serves them up in under 2 seconds searchable by project number, Pay App number or subcontractor name with the full backup PDF intact and audit-ready.

Yes — the multi-dimensional accounting context is the single most important thing acumatica data archival has to preserve. Every archived transaction carries its Branch, Subaccount, Project, Cost Code, Sub-Project and any xRP-customized dimensions as first-class columns in the archive Parquet, not as opaque text strings. Branch and Subaccount master data is captured at every point-in-time so a 2018-as-of trial balance for Branch 03 uses 2018 Subaccount descriptions, not today's. Project hierarchy snapshots are preserved similarly, so a project profitability lookback for FY2020 reflects the project structure that was in production during FY2020.

Depends on tenant scale and document volume. Typical mid-market Acumatica tenants archive 50 GB – 2 TB of structured data (compressed Parquet typically 5–10x smaller than raw SQL), plus 100 GB – 10+ TB of attached documents depending on industry (construction tenants with AIA Pay App backups, signed Subcontracts and certified payroll exports often run multi-TB; pure distribution tenants without heavy document attachments run lighter). Cloud object storage costs cents per GB-month, so even a 10 TB archive runs well under $5K/year in raw storage — versus a six-figure Acumatica subscription. The payback math is straightforward.

Tightly. The standard pattern is: pre-migration, run a bulk acumatica data archival pass to capture everything currently in Acumatica; during the parallel-run window, run scheduled nightly OData delta extracts so the archive stays current right up to cutover; at cutover, run a final reconciled delta to capture the last 24 hours; post-cutover, Acumatica goes read-only and the archive becomes the authoritative source for historical queries while Fusion handles all new transactions. The whole sequence is choreographed to give finance, audit and operations zero data loss and full visibility throughout.

Yes — many customers do this purely to escape the consumption-based subscription. The pattern: run a one-shot full archival of every entity, every document and every xRP custom field; run weekly deltas until the next Acumatica renewal date; at the renewal date, cancel the subscription and let the archive become the source of truth. This is common for customers who built an Acumatica deployment for a specific project, division or subsidiary that has wound down — the historical data still needs to be retained for SOX/IRS/GAAP/construction-specific periods, but there's no business need for a running tenant.