Outpatient group: Acumatica upgrade without stopping billing
A multi-site outpatient organization needed a supported Acumatica version while weekly claims and provider payments kept running. Cutover ran over one weekend with a freeze plan the billing team helped write.
Upgrade risk sat next to cash flow
They were several versions behind. Customizations from a prior partner had little documentation. Billing leadership would not accept a weekday outage or a “we’ll catch up claims later” plan.
Inventory customizations, then a dress-rehearsed cutover
We cataloged every customization and integration, fixed what the new version broke in a sandbox, and ran two full restore-and-upgrade rehearsals with billing staff. Production cutover was Saturday night with a freeze on master-data changes; Monday morning claims ran on the new version with the same schedule.
Main pieces of the work
Customization inventory
Screens, GI, APIs and partner packages listed with owners.
Sandbox proof
Upgrade + regression on a full copy before any production window.
Freeze plan
What could change the week before cutover — agreed with billing.
Hypercare week
Nesha on call with the client IT and billing leads.
- Acumatica upgrade path
- SQL backup/restore
- Custom package validation
- Integration retests
- Claims batches ran Monday on the new version as scheduled
- No restore from backup was required in production
- Unsupported version risk removed for audit and partner support
- Billing team kept the same daily checklist with minor screen changes
Stuck on an old Acumatica build?
We will scope customizations and a realistic cutover window before you commit to dates.