Sandbox ↔ production config drift
For support 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 config 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.
how it works
Same loop under every offer: version → rebuild → exercise → report.
Nothing installs inside Acumatica. Nothing for you to keep running.
- Demo without the afternoon rebuild
- Minutes, not a day: clean company, linked transactions already in it — same rebuild next week when the pitch goes sideways.
- See what is actually configured
- Live tenant extracted to Git; agreed config versus live, sandbox versus production — ranked lists, no writes.
- Catch breakage before production
- Business scenarios on an upgraded copy. Failures name the step — not a customer on the phone.
- Cutover becomes a rehearsal
- Rebuild, load, exercise, recon, tear down — repeat until go-live is boring and the controller has a trail.
Work product stays in your repo. Read-only work only reads; release and cutover never touch production until the SOW says so. Hosted tenants use what you already have; full rebuilds need a lab you control — every engagement states which — and your Acumatica version is pinned.