Cutover rehearsal with reconciliation pack
For project managers and controllers · Scoped per engagement
Go-lives and reimplementations get one dress rehearsal — or none — because every rehearsal costs a week of manual tenant setup. The controller ends up signing off on spreadsheets nobody fully trusts.
You get. A cutover rehearsed until it is boring: full tenant rebuild, opening-balance load, and automated reconciliation — trial balance by account, AR/AP aging bucket totals, inventory quantity × cost against the GL control account — delivered as a report your client’s controller can sign.
I rehearse cutovers with rebuildable hosts, seed and scenarios, and acu apply/diff/run. Read Acumatica DEV/TEST environments with Ansible.
how i work
- Work ships in your repository — configuration, scenarios, and reports stay yours after the engagement.
- Runs in your environment, with read-only access wherever the deliverable allows it.
- Upgrade and cutover work runs against rebuilt copies — never against production.
- Everything is documented in plain language for the next consultant, not just for me.
- Verified against the current Acumatica release, twice-yearly majors included.
- Full environment rebuilds need a self-hosted or private-cloud lab; on Acumatica-hosted SaaS tenants the work runs as apply-and-diff against an existing company. Every engagement states which path it covers.
verified today
Measured. Scenario runs complete in about 3–5 minutes per run in CI, measured on a real Acumatica tenant.
Demonstrated. Full rebuild from empty tenant to configured company with running transactions and a clean diff, on the Lab5 sample company. Wall-clock time on your tenant is pinned in the first week of an engagement, not quoted from a brochure.
Built per engagement. Source-system loaders (QuickBooks, Sage 50/100), historical and opening-balance load paths, and merges into half-configured tenants are built when a paid engagement scopes them — not shelf inventory.