Environment drift report
For support, managed services, and ERP admins · Read-only
Sandbox and production diverge between releases. “It worked in test” is still the most common post-change surprise.
You get. A weekly read-only diff of sandbox against production, ranked so material drift — financial close, tax, approvals, integration-critical settings — sits above the noise. Nothing is written to either environment.
I run environment diffs with acu diff against configuration held in gitops. Read Configuration as code for Acumatica.
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.