Understand what Acumatica actually is as a platform — tenants, branches, accounts and subaccounts, posting classes and customisation projects — and why the branch decision is the least reversible call in the whole engagement.
Acumatica migrations mislead people early, and they do it in a specific way. The source is a modern cloud platform with a documented developer story, contract-based REST endpoints, a coherent customisation model and no legacy client to decommission.
It is a platform with a first-class customisation model. Business logic lives in data access classes and their extensions, in graphs and graph extensions, and in workflows. Those artefacts are packaged into customisation projects and published to a tenant.
The adapter's description of the accounting primitive is worth reading slowly, because it names the whole problem in one sentence: Acumatica combines account, subaccount, branch, account and posting classes, customer and vendor classes, inventory posting classes, tax zones, project and account groups, and account and subaccount masks to…
An Acumatica tenant is a data-isolation and administrative boundary. Tenants exist for a variety of reasons: statutory separation, acquisition history, test and training isolation, customer-facing segregation, or simply because someone once needed a clean environment.
The second finance-side hazard is the subaccount. The source concept note lists six things a subaccount segment may encode: department, location, branch, product line, project, and legacy reporting exceptions.
Being explicit about the evidence boundary matters more here than in most paths, because the platform documentation is good enough to make a confident-sounding but unfounded design easy to write.
The playbook lists twelve mandatory fingerprint items. They are not a discovery checklist to be worked through in parallel with build; they are the inputs without which build cannot start.
The programme recommendation in the executive summary is a sequencing rule disguised as governance advice. Detailed migration planning should not be approved until:
Acumatica is a modern platform, and that is precisely why the migration is misjudged. Its clean APIs make extraction straightforward and change nothing about the two design problems that dominate the programme: deciding what a tenant and a branch become, and decomposing the account-plus-subaccount model into main accounts, financial…