DevOps for ERP

Configuration-as-code. A tax rule, a new branch, an edited approval workflow — ERP configuration is normally changed by hand, directly in the tenant. I keep tenant configuration as code in Git, so every change is reviewed, diffed, and rolled back like application source.

Automated regression testing. Those configuration changes normally ship to production after manual testing only, each checked by clicking through screens by hand. I test every change in a pipeline instead: AI generates the transactions, runs them, and compares the result against what was expected. About 3-5 minutes per run, measured on a real Acumatica tenant.

Infrastructure-as-code. The tenant has to run somewhere and come back after a bad upgrade or a data loss. I automate the infrastructure around ERP — provisioning, virtualization, and backups — across Google Cloud, Azure, AWS, and on-premise, with disaster recovery rehearsed and a second copy kept off-site.

ETL / data migration. Moving onto an ERP means getting data out of the old system without breaking it. I map source fields from QuickBooks, Xero, or a legacy system to ERP entities and validate them against those entities before any data moves.

Twenty years moving up the same stack: I started in the hardware, moved to the cloud, and now write the software that runs on both. I bring all three to ERP.

Toronto-based, working with ERP teams across North America. The work ships in your repository and runs in your environment, documented in plain language.