DevOps Services for Acumatica ERP

Every Acumatica change, tested automatically — not clicked through by hand.

I apply software-development discipline to ERP work for Acumatica VARs, ISVs, and operators: every change versioned, verified, and repeatable — so the second run costs less than the first.

Konstantin Borovik

the problems I solve

For pre-sales teams

Every pitch leaves the demo tenant a little worse. Rebuilding a clean distribution, manufacturing, construction, or field-service demo by hand costs your pre-sales team days it does not have.

Demo tenant factory

Industry demo tenants rebuilt on demand — from empty to fully populated with realistic, linked transaction history.

For practice leads and ERP owners

What is actually in this Acumatica tenant after years of change — an inherited client or your own production company? Which settings are custom, which drifted from standard, and which nobody can explain?

Config audit

The tenant’s full configuration extracted into Git, plus a findings report on what’s custom, drifted, or undocumented.

For support, managed services, and ERP admins

Sandbox and production diverge between releases. “It worked in test” is still the most common post-change surprise.

Environment drift report

A weekly read-only diff of sandbox against production, ranked so material drift sits above the noise.

For service leaders and ERP owners

Acumatica ships two major releases a year. Every tenant with customizations, integrations, or non-trivial workflow carries regression risk into each one — and the answer today is manual click-through UAT, or nothing. When it breaks, someone eats the fire drill as non-billable work.

Upgrade assurance

Recorded business scenarios run against an upgraded copy before each Acumatica release — a pass/fail report per tenant for your release gate or install base.

For project managers and controllers

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.

Cutover rehearsal with reconciliation pack

A cutover rehearsed until it’s boring: full tenant rebuild, opening-balance load, and a reconciliation report your client’s controller can sign.

For technical and integration leads

Acumatica integrations with Shopify, EDI, WMS, CRM, and payment gateways break silently on upgrade. Your customer finds out when orders stop flowing — and those are the angriest tickets.

Integration contract testing

Contract tests for your Shopify, EDI, WMS, CRM, and payment-gateway integrations, run on every Acumatica release and configuration change.

For ISV engineering leads

Your extension has to certify against every Acumatica release, and the treadmill never slows down.

ISV release certification

Scenario suites that certify your extension against each Acumatica release candidate, wired into the pipeline you already run.

All 7 services

method

Same stack under every offer — start read-only, grow into rehearsals and release gates.

Your tenant configuration is versioned, and a working environment rebuilds from it on demand. AI turns plain-language intent into consistent, linked transactions that exercise every change, and each run ends in a diff and a report — about 3–5 minutes per run on a real Acumatica tenant.

about me

System integrator → DevOps → software and AI, aimed at Acumatica work.

Twenty years up the stack: data-center hardware first, then cloud infrastructure, then the software that runs on both — now applied to Acumatica configuration, hosts, and cutovers.

Toronto-based. Work ships in the client repository and runs in the client environment, documented in plain language.