Acumatica Migration Assessment — Discovery in Weeks, Not Quarters

Acumatica migration assessment is the structured discovery exercise that produces, in 2–3 weeks instead of 3–4 months, a complete inventory of what is in your Acumatica tenant, what would have to move to Fusion, what would have to be rebuilt, what could safely be retired, and what the resulting migration timeline, budget and risk register look like. It covers six domains: xRP customization inventory, Generic Inquiry inventory, third-party SuiteApp/ISV inventory, multi-Branch scope, transactional volume profile and integration footprint. Output is a signed assessment doc that the executive sponsor uses to approve project funding and the project team uses as the input to mapping and design.

Without an explicit assessment, mapping is guesswork. You can't design the Fusion COA without knowing how Account + Subaccount + Branch is actually used. You can't decide which Generic Inquiries to rebuild without knowing which ones are heavily used vs orphan. You can't size the xRP customization remediation without knowing the C# extension footprint. You can't budget the project without knowing the transactional volume. Consultant-led migrations skip a rigorous acumatica migration assessment and pay for it later: scope changes in month 4, re-baselined timelines in month 6, defects in production in month 9. Syntra ETL ships the assessment as the structured first stage with pre-built discovery tooling.

Acumatica's xRP Platform allows C# extensions that add custom fields to standard DACs, override graph events, add custom screens, register Business Events and integrate with the Mobile Application Framework. The acumatica migration assessment discovery engine connects to the Acumatica customization project repository in your tenant and walks the published projects: every C# class, every graph extension, every field extension on every DAC, every PXAction, every custom screen, every Business Event, every Mobile App definition. Output is a complete inventory broken out by DAC, by author, by date last modified, by usage frequency (from transaction logs). Approximately 35–55% of xRP customizations typically turn out to be redundant under Fusion's native capabilities and get retired.

Generic Inquiries are Acumatica's user-defined query builder — they get used as ad-hoc reports, as data-source feeds for dashboards, and as embedded inquiries within transactions. A typical Acumatica tenant has 200–600 Generic Inquiries. The acumatica migration assessment inventories every one with metadata: title, author, last modified, execution frequency (from access logs), source DACs, output columns, embedded parameter logic. The engine then classifies by business value (mission-critical, useful, occasional, orphan) and proposes Fusion replacement: OTBI dashboard, BI Publisher report, Smart View Excel inquiry, or retire. Typically 40–60% of legacy Generic Inquiries are duplicates, orphans or low-value and get retired.

Acumatica's Marketplace has a long catalog of ISV add-ons (sometimes called SuiteApps, though the terminology varies): payment processors (Authorize.Net, CardConnect, Stripe), shipping integrations (FedEx, UPS, EasyPost, ShipStation), eCommerce (Magento, Shopify, BigCommerce), CRM (Salesforce sync), warehouse management, EDI, payroll (CDK, Paychex), construction-specific (Procore, BuildAssist), document automation, sales-tax (Avalara, Vertex), and dozens more. The acumatica migration assessment inventories every active connection — what data flows, in what direction, at what frequency, on what protocol — and proposes a Fusion equivalent: native Fusion integration, replatformed integration via OIC (Oracle Integration Cloud), Fusion REST/SOAP services, or retain on Acumatica during a hybrid period.

Acumatica's Branch + Subaccount + Project structure is the primary multi-dimensional accounting framework. A typical mid-market tenant has 1–25 Branches representing legal entities, operational divisions, project sites or all of the above. The acumatica migration assessment walks every active Branch, classifies by usage (separate legal entity? operational division? consolidation purpose?), maps to proposed Fusion Legal Entity / Business Unit / Cost Center / Project segment assignments, and quantifies Inter-Branch Transaction volume (which becomes Fusion Inter-Company Transactions post-migration). Multi-currency Branches get specific attention: which translation rates were used, which gain/loss accounts are configured, which consolidation ledgers feed where.

The acumatica migration assessment deliverable is a 40–80 page signed doc covering: executive summary, current-state Acumatica inventory (modules in use, transactional volume, customization footprint), Fusion target architecture (proposed Legal Entity / BU / Ledger structure, 6-segment COA, item categorization, supplier classification), gap analysis (what moves, what gets rebuilt, what gets retired), timeline (week-by-week migration plan), budget (resourcing, infrastructure, licensing), risk register (top 15 risks with mitigations), and recommendation. Sponsor signs the deliverable, project team picks it up as input to mapping and design. Total elapsed time: 2–3 weeks from kick-off.

Syntra ETL's standalone acumatica migration assessment runs as a fixed-fee 2–3 week engagement, typically in the $25K–$45K range depending on the size of the Acumatica tenant, number of Branches, customization complexity and integration footprint. The fee is fully creditable against a subsequent full-migration engagement — sponsors regularly use the assessment as a low-commitment first step that produces a deterministic basis for the bigger decision. By comparison, consultant-led discovery typically runs $150K–$400K over 3–4 months and produces a less rigorous output because it lacks the pre-built discovery tooling.