Sandbox ↔ production config drift

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 read-only environment diffs against versioned configuration held in Git.

“Why not just spot-check sandbox against production in the UI before each release?”

A focused UI walkthrough catches obvious screen-level differences when you already know which preferences matter. For a short list of known settings, eyes on the form are still useful.

• →A walkthrough only covers the screens someone opens. Financial close, tax, approvals, and integration-critical settings span dozens of screens. A human walkthrough can miss a preference that wasn’t on this week’s list.
• →No ranked material-vs-noise report. Ad-hoc comparison produces screenshots and chat threads — not a recurring ranked list a support lead can act on without wading through cosmetic diffs.
• →Not weekly and not durable. Sandbox and production diverge between releases by default. A one-time UI check does not re-run next Monday or leave a trail of what changed when.

Spot-check the UI when you already know the two screens that matter. Use sandbox ↔ production config drift when you need a recurring, read-only ranked report on a named company pair.

Stable read access to both environments → recurring ranked drift report for a named company pair.

Nothing installs inside Acumatica. This is a read-only drift engagement — nothing is written to sandbox or production.

→Stable read access to both environments

You name the company pair (default sandbox ↔ production; other pairs only when the SOW says so) and a credentials owner. Service account or scheduled export — no write on either side.

→A recurring ranked drift report

Same pair each week: material changes ranked above noise so financial close, tax, approvals, and integration-critical settings are not buried under cosmetic diffs.

→Signal quality as the product surface

Material vs noise ranking is what makes the report actionable. Without it, the report becomes another ignored alert — that ranking is the paid surface, not a raw dump of every setting change.