The complete acumatica migration checklist that gates every successful Acumatica to Oracle Fusion cutover. Tenant readiness, xRP customization inventory, Branch + Subaccount walk, Generic Inquiry triage, Fusion target setup, compliance retention routing, cutover logistics. Auditor-shareable evidence pack.
The difference between a 14-week Acumatica migration and a 14-month one is rarely the technical work. It's whether the checklist was complete on day one or built reactively as issues surfaced.
Acumatica, founded in 2008, has built a rich and customizable cloud ERP platform. A typical mid-market Acumatica tenant carries 10–25 Branches, 50–500 Subaccount combinations, 25–80 xRP Platform customizations of various sizes, 80–400 Generic Inquiries used as ad-hoc reports, 20–60 Business Events firing on transaction posts, dozens of Acumatica Report Designer reports and (often) several Mobile Application Framework apps. Every one of these surface areas needs explicit treatment in the migration plan. The acumatica migration checklist is the artifact that makes sure nothing is missed.
The checklist serves three audiences. For the technical team, it's a sequenced work plan — every item maps to a specific extractor, transformation rule, FBDI emitter or reconciliation check. For finance and ops leadership, it's a status dashboard — completion percentage by category provides honest progress reporting (not optimistic verbal status). For internal audit and external auditor, it's the evidence pack — every retention routing decision, every customization disposition, every reconciliation sign-off documented and timestamped.
Syntra ETL ships the acumatica migration checklist pre-populated with the standard 60+ items, plus module-specific branches for Distribution (SOOrder / POOrder / InventoryItem / Warehouse / Lot-Serial), Manufacturing (BOM / Production Order / MRP), Construction (Project / Pay App / Subcontract / Change Order / Certified Payroll), Field Service, CRM and Payroll. The discovery engine auto-populates inventory items (Branches, customizations, Generic Inquiries, Business Events, reports) and the team works from a complete starting checklist rather than building one reactively.
The technical foundation items. Without these complete, extract cannot begin.
Contract-Based REST API enabled, OData v4 enabled, OAuth2 client credentials issued, scoped read-only role created, throttle limits documented per tenant.
Module entitlements verified (Financials, Distribution, Manufacturing, Construction, Field Service, CRM, Payroll, Project Accounting), license cap (resource units) confirmed, consumption usage trajectory.
Acumatica customization project repository accessible, every project enumerated, source code or compiled DLL inventoried, deployment history captured.
Complete Generic Inquiry catalog pulled (typically 80–400 entries), each with definition, parameters, last-run date and run frequency from usage log.
Every Business Event inventoried by trigger condition, action type (email, webhook, BPM, audit log), enabled status and run frequency.
Acumatica Report Designer reports inventoried, classified by business purpose (operational, financial, regulatory), and last-run date / run frequency captured.
The decisions that shape every downstream design choice. Made in checklist weeks 2–4.
Every active Branch enumerated, every Subaccount combination walked, classification by legal entity vs operational unit vs cost center vs project applied.
Migration scope: open fiscal year transactions only, current + prior 2 FYs detailed, or full history. Drives extract throughput and archive routing decisions.
Every xRP custom field on every DAC walked, classified by reporting materiality, routed: Fusion COA segment / DFF / Application Composer field / OTBI dimension / archive.
Every Generic Inquiry triaged: retire / consolidate / rebuild as OTBI / rebuild as BI Publisher / rebuild as Smart View. 40–60% retire typical.
Every Business Event routed: retire / Fusion notification / OIC subscription / BPM workflow / audit log. 30–50% retire typical.
Acumatica Report Designer reports triaged and routed: retire / replace with OTBI / replace with BI Publisher / replace with Smart View.
Sequenced through a typical 14-week migration. No item is skipped; every item gates the next.
API access verified, OAuth2 client credentials issued, customization project access granted, usage logs accessed. Tenant readiness category complete.
Branch + Subaccount walk complete, customization inventory complete (xRP DACs, Generic Inquiries, Business Events, Report Designer reports), fiscal year scope decided.
xRP custom field routing decisions made, Generic Inquiry triage decisions made, Business Event routing decisions made, Report Designer rebuild scope set. Signed off by finance + ops + IT leads.
Fusion enterprise structures, ledgers, BUs, Legal Entities, 6-segment COA, item categories, supplier classifications configured. FBDI submission access verified.
Compliance retention routing decisions made for every framework (SOX, GAAP, IFRS, IRS, state sales tax, ASC 606, GDPR HR, construction-specific). Auditor reviews and signs off on routing.
Parallel-run window scheduled, hyper-care window scheduled, consumption-pricing renewal date confirmed, Acumatica read-only schedule communicated, subscription cancellation date scheduled.
The retention obligations that need explicit routing. Most under-budgeted on consultant-led projects.
Public-company customers: 7-year retention of financial records with auditable trace from GL entry back to original supporting document. Route to Fusion attachments or long-term Acumatica archive.
IRS general business records 4 years (often 7), payroll 4 years, state sales tax 3–7 years by jurisdiction. Route to Fusion attachments or archive with read-access log for audit support.
Customer contract documentation retained for lifetime of contract + 7 years. Sales orders, performance obligations, revenue allocation history routed to Fusion attachments.
European subsidiaries: HR data retention varies by EU member state (typically 6 years post-employment). Route with member-state-specific retention policy and right-to-erasure support.
Lien rights 1–6 months post-completion, AIA Pay App backup for full project lifecycle + warranty period, Certified Payroll 3–7 years post-completion for prevailing-wage jobs.
Every read access to archived data logged with user, timestamp, query, records returned. Supports SOX, GAAP, IFRS and construction-specific audit evidence.
A comprehensive acumatica migration checklist covers 60+ pre-migration verification items grouped into six categories: Acumatica tenant readiness (API access, OAuth2 client credentials, license entitlement, customization project inventory), data scope (Branches, Subaccounts, modules, fiscal years, historical depth), customization inventory (xRP DACs, Generic Inquiries, Business Events, custom screens, Acumatica Report Designer reports, Mobile Application Framework apps), Fusion target readiness (enterprise structures, ledgers, BUs, Legal Entities, 6-segment COA, FBDI access), compliance retention (SOX 7-year, GAAP, IFRS, IRS 4–7 years, construction-specific lien rights, certified payroll), and cutover logistics (consumption-pricing renewal date, parallel-run window, hyper-care window, Acumatica read-only schedule).
Distribution customers running Acumatica Distribution Management add SOOrder / POOrder / InventoryItem / Warehouse / Lot-Serial / Landed-Cost specific checks: open SO/PO inventory, warehouse master, item cost layers (LIFO/FIFO/Standard), requisition workflows, intercompany transfer history. Construction customers running Acumatica Construction Edition add Project / Pay App / Subcontract / Change Order / Certified Payroll / Lien Waiver specific checks: AIA Pay App format validation, Subcontractor lien waiver chain, Change Order revision tracking, prevailing-wage payroll retention, Cost Code structure, project actuals-to-date. The acumatica migration checklist branches at the module level to ensure no domain-specific compliance carrier is missed.
Because the xRP custom field routing decision drives FBDI design, COA structure and reporting rebuild scope. Acumatica's xRP Platform allows custom fields on any DAC, and customers carry an average of 25–80 customizations of various sizes. Without a complete inventory at the start of the project, you discover critical custom fields in week 6, redesign the COA in week 8, and slip the timeline by 4–6 weeks. The acumatica migration checklist requires inventory completion before week 3 of the project — every custom field walked, classified by reporting materiality and routed to Fusion COA segment / DFF / OTBI dimension / archive before transformation rules are written.
Yes — and this is the item most teams under-budget. The checklist verifies retention obligations across multiple frameworks: SOX (7 years post-fiscal-year-end for public companies), IRS general business records (4 years, often 7), IRS payroll (4 years), state sales tax (3–7 years depending on jurisdiction), ASC 606 contract documentation (lifetime of contract + 7 years), GDPR HR data (varies by EU member state, typically 6 years post-employment for European subsidiaries), Construction-specific (lien rights 1–6 months post-completion plus 3–7 years for prevailing-wage jobs, AIA Pay App backup for full project lifecycle plus warranty period). The acumatica migration checklist routes each retention obligation to Fusion attachments or long-term Acumatica archive explicitly.
The acumatica migration checklist verification phase runs 2–4 weeks for SMB customers (single Branch, modest customization) and 4–8 weeks for mid-market customers (10–25 Branches, 50+ xRP customizations, Construction Edition complexity). Syntra ETL's discovery engine accelerates the inventory components — xRP customization catalog, Generic Inquiry catalog, Branch + Subaccount walk, Business Event registry, Acumatica Report Designer report inventory all run as automated discovery against Contract-Based REST + OData v4. The human work concentrates on classification decisions (retire / keep / replace) and compliance retention routing, where finance, ops, audit and legal stakeholder input is required.
Cutover day (typically a long weekend after fiscal-period close) has its own micro-checklist: final OData modified-since delta extract executed, FBDI loads completed and reconciled per Branch per period, sign-off pack signed by finance, ops and audit leads, Acumatica tenant moved to read-only archive mode, Fusion go-live communicated to all user populations, hyper-care monitoring activated, first-day-of-business validation script run, daily reconciliation cadence established for the 2–4 week hyper-care window, and the Acumatica subscription cancellation notice scheduled for the next renewal date. Every item gates the next. No item is skipped.
Business Events in Acumatica fire on transaction posts (invoice created, PO approved, inventory transferred) and trigger webhooks, email notifications or custom workflows. The acumatica migration checklist inventories every Business Event by trigger condition, classifies by business purpose (email notification, webhook to external system, internal workflow trigger, audit logging), and routes to Fusion equivalent: Fusion notifications, Oracle Integration Cloud subscriptions, BPM workflow, or audit log. Approximately 30–50% of Business Events turn out to be obsolete and get retired. The remaining ones get explicit Fusion routing with reconciliation test cases.
Yes — and the acumatica migration best practice is to share it explicitly. The full checklist with completion status per item, sign-off signatures per phase, reconciliation evidence per period, customization disposition (retire / keep / replace) per xRP item, Generic Inquiry triage decisions, Business Event routing decisions and retention routing decisions is shared with internal audit and external auditor (if applicable) 4–6 weeks pre-cutover. Auditor sign-off on the checklist is the gate for cutover — not a verbal status update. This eliminates the post-cutover audit surprises that derail go-live in T&M-driven projects.
Book a 30-minute discovery call. We'll walk through your Acumatica modules, Branch structure, customization footprint and compliance obligations — and deliver a tailored 60+ item acumatica migration checklist with completion targets for every phase.