Cloud-native, immutable, queryable archive for microsoft dynamics nav cloud archive workloads. Object storage with KMS encryption, Parquet partitioning, self-serve finance/tax/audit query layer. SOX 7-year, GoBD 10-year, HMRC 6-year, SAF-T retention built in. 65–80% cheaper than keeping NAV alive.
Once Fusion is live, the only reasons to keep NAV running are compliance, audit and historical reporting. A purpose-built cloud archive serves all three for 20% of the cost.
Most organisations finishing a NAV to Fusion migration discover the same thing: Fusion is the system of record going forward, but they still need NAV records retrievable for 7+ years of compliance — SOX in the US, GoBD's 10-year digital-records mandate in Germany, HMRC's 6-year MTD-compatible retention in the UK, EU SAF-T windows in Norway, Poland, Portugal and France. Keeping NAV alive in maintenance mode is the path of least resistance — and the most expensive option available. SQL Server licensing, Windows Server, NAV server, infrastructure, security patching past extended-support end, partial admin headcount: $80K–$200K per year for a typical mid-market deployment.
Worse, NAV's support timeline turns the maintenance-mode option into a security liability. NAV 2016 extended support ends April 2026. NAV 2018 ends January 2028. Past those dates, there are no security patches, no tax-table updates for jurisdictions like UK MTD or German GoBD, and no Microsoft escalation path. Auditors, cyber-insurance providers and internal security teams increasingly refuse to sign off on an unpatched ERP environment that's still touching live data — even read-only.
A microsoft dynamics nav cloud archive replaces NAV-in-maintenance-mode with cloud-native object storage, KMS-encrypted Parquet partitions, an immutable retention layer (object-lock for the retention window) and a self-serve query layer that finance, tax and audit teams use directly. The result: 65–80% lower TCO than keeping NAV alive, hardened audit profile, no patching liability, and a cleaner compliance story for SOX, GoBD, HMRC and SAF-T audits.
Every NAV table that matters for 7–10 year compliance, plus the partner add-on tables that grew alongside.
G/L Entry 17, Customer Ledger Entry, Vendor Ledger Entry, Bank Account Ledger Entry, Item Ledger Entry 32 — full posting history preserved with dimensions, posting groups, source-document references intact.
Sales Invoice Header/Line, Sales Cr.Memo, Posted Sales Shipment, Purchase Invoice Header/Line, Posted Purchase Receipt, plus the corresponding archive tables — header-line integrity preserved.
Customer 18, Vendor 23, Item 27, Contact 5050, Bank Account 270, G/L Account, Dimension Value, Posting Group — point-in-time master snapshots aligned to the cutover moment plus periodic refreshes if needed.
Custom tables 50000-99999, partner add-on tables (Anveo, Continia, ChargeLogic, Insight Works, regional add-ons) — preserved alongside standard NAV tables with same query/audit access.
Document attachments, incoming-document files, BLOB-stored receipts and PDFs — preserved in object storage with hash-signed references in the Parquet layer for drill-back from any archived record.
Country-specific NAV localisation tables (DE GoBD, UK MTD VAT, NO/PL/PT/FR SAF-T, IT SdI, MX CFDI, BR SPED) — preserved with format-fidelity for retrospective regulator queries.
From scoping conversation to live archive with self-serve query access. Typical timeline: 4–12 weeks depending on multi-company scope.
Which NAV companies, which fiscal years, which tables in scope. Retention windows per data domain (SOX 7yr, GoBD 10yr, HMRC 6yr, SAF-T per country). Object-lock policy designed. Access-control model defined: who queries, who exports, who downloads.
Cloud object storage (S3, GCS, Azure Blob) provisioned in your account with KMS encryption, object-lock enabled for retention immutability, IAM roles configured per access tier (finance read, tax read, audit read+export, admin).
Syntra ETL NAV extractors pull every in-scope table from SQL Server, NAV Web Services and OData. Output staged as Parquet partitioned by company and fiscal year with hash-signed manifests. Attachments streamed to object storage with hash references.
Self-serve query UI configured with finance/tax/audit search patterns. Power-user SQL access via Athena/BigQuery/Snowflake. Audit-log infrastructure deployed: every query, export and download logged to immutable audit trail.
Reconciliation pack issued (NAV TB vs archive TB to the cent, AR/AP aging vs aging, inventory valuation vs valuation). Finance, tax and audit sign off. NAV environment decommissioned per retention policy, archive becomes the system of evidence.
Built for SOX, GoBD, HMRC, SAF-T from day one — not retrofitted.
Object-lock with retention period equal to the longest compliance window. No overwrite, no delete, no modification possible during retention — satisfies WORM requirements.
Every archived record hash-signed at ingestion. Hash drift detected on retrieval. Audit pack includes signature evidence for every record cited.
Every query, export and download logged with user, timestamp, scope, IP and result. Audit log itself is immutable and retained for the full compliance window.
AES-256 encryption at rest with KMS-managed keys. Key rotation supported without re-encrypting. TLS 1.3 in transit.
Per-data-domain retention windows: 7yr for US SOX, 10yr for German GoBD, 6yr for HMRC, jurisdiction-specific for EU SAF-T. Retention enforced by object-lock.
Read-only IAM tier provisionable for external auditors. Auditors self-serve historical NAV records without IT involvement. Year-end audit cycle compresses from weeks to days.
A microsoft dynamics nav cloud archive is a cloud-native, immutable, queryable repository of historical NAV data — G/L Entry 17, Item Ledger Entry 32, Customer/Vendor Ledger Entries, document tables (Sales/Purchase Header and Line), master data and supporting attachments — designed to preserve the legacy NAV record long after the NAV environment itself is shut down. Syntra ETL's NAV cloud archive runs on object storage (S3, GCS, Azure Blob) with KMS encryption, Parquet partitioning for query performance, and a self-serve query layer that lets finance, tax and audit teams pull historical records without spinning NAV back up. Retention windows are configurable per data domain to match SOX 7-year, GoBD 10-year, HMRC 6-year, SAF-T and any other regulatory regime in scope.
Fusion is the system of record for new transactions; the NAV cloud archive is the system of evidence for old ones. Even after a NAV to Fusion migration is complete, customers face 7–10+ years of post-cutover compliance obligations: SOX 7-year retention of financial records, GoBD 10-year retention in Germany, HMRC 6-year retention in the UK, EU SAF-T windows in NO/PL/PT/FR, IRS 4–7 year retention in the US. Keeping the source NAV instance live for compliance is expensive (SQL Server licensing, infrastructure, security patching past extended-support end), risky (unpatched NAV 2016 after April 2026, NAV 2018 after January 2028) and operationally complex. A microsoft dynamics nav cloud archive replaces all of that with a fraction of the cost and a hardened audit profile.
The cloud archive preserves the full NAV record exactly as it existed at the moment of cutover, plus an audit log of every read access against the archived record. Every archived G/L Entry, Item Ledger Entry, document header/line and master record is hash-signed at ingestion and stored in object storage with object-lock immutability — no overwrite, no delete, no modification possible during the retention window. The original NAV record-id, transaction date, posting date, dimensions, posting groups and user-id are preserved. A separate audit log captures every query, every export and every download with user, timestamp, scope and result — satisfying SOX, GoBD, HMRC and SAF-T audit requirements without manual reconstruction.
For a typical mid-market NAV deployment carrying 10 years of history across 5 companies, keeping NAV live for compliance costs $80K–$200K per year (SQL Server licensing + Windows Server + NAV server licensing + infrastructure + security patching + partial admin headcount). A Syntra ETL microsoft dynamics nav cloud archive on the same data volume runs $15K–$40K per year (object storage at $0.023/GB/month + KMS + query layer + audit-log retention). Even with the migration cost amortized, customers typically break even in year 2 and save 65–80% per year thereafter. The savings compound for organisations carrying multiple legacy NAV companies from M&A history.
Yes. The archive ships with a self-serve query layer designed for non-technical users: search by customer/vendor/item, filter by company/date range/dimension, drill into document header → line → posting → dimensions, export to Excel or PDF for audit pack delivery. Power users get SQL access via Athena, BigQuery or Snowflake against the Parquet partitions. Every query is logged to the audit trail. Customers routinely give read-only archive access to external auditors during year-end so they can self-serve historical NAV records without needing IT to spin up NAV environments — turning a multi-week audit cycle into a couple of days.
NAV's per-company database segregation is preserved in the archive: each company's data lives in its own logical partition with company-id preserved on every record, but cross-company queries (intercompany G/L Entry pairs, consolidated trial balance, group-wide AR/AP aging) are supported via standard JOINs on company-id and document-no. Customers carrying 20+ NAV companies from acquisition history routinely consolidate the entire estate into a single cloud archive with cross-company audit walkthrough — something that was painful in NAV itself because of the per-company database design.
Yes. Partner add-ons (Anveo eCommerce, Continia OPplus, ChargeLogic credit-card processing, Insight Works mobile WMS, regional specialists) each ship their own custom tables in the NAV database. Syntra ETL's cloud archive ingestion includes vendor-specific recognition for the major add-ons, preserves the add-on tables alongside standard NAV tables, and exposes them through the same query layer. The archive thus replaces not just the NAV functional footprint but the partner add-on footprint as well — eliminating the separate compliance overhead each add-on otherwise imposes.
For a single-tenant NAV 2016 or NAV 2018 environment with 10 years of history, the cloud archive can be deployed and fully populated in 4–8 weeks. For multi-company estates (10+ companies across 10 years), 8–12 weeks. The acceleration over a bespoke archive build comes from pre-built NAV extractors (SQL Server, SOAP, OData), pre-built Parquet schemas per NAV table, pre-built query layer with the standard finance/tax/audit search patterns, and a pre-built audit-log infrastructure that satisfies SOX/GoBD/HMRC/SAF-T out of the box. A hand-rolled equivalent typically takes 9–14 months.
30-minute call. Walk through your NAV version, multi-company estate, retention obligations and decommissioning timeline — leave with a concrete microsoft dynamics nav cloud archive plan and cost estimate.