Turnkey Acumatica Upgrade

We take over the whole scene. That includes upgrading all customizations, collecting ISV packages from ISVs and testing them, and running automated regression testing on the standard modules your client uses - reports, dashboards, GIs, workflows. Your team doesn't need to do any development or technical testing. The client's role is limited to a high-level review of the sandbox before go-live. We handle the rest - customization upgrade, ISV coordination, system integrity testing, sandbox deployment, production execution, and post-upgrade support.

Very little. From the code, we can tell the story - we have a tool that analyzes customizations and gives us the full spec on what's going to work and what's not. The customer really only needs to do a review of the sandbox at the end, which shouldn't be in-depth since we've already tested all the modules. If something isn't working and we need to understand the business logic, that's when we'd reach out, but in most cases we don't even need to communicate with the end client directly. We work through you.

Mostly automated. We built an automated framework based on Acumatica's SDK for all the standard modules - including reports, dashboards, and workflows. When we onboard a customer, we use the intake form to see which modules they're using and enable the appropriate test cases. We do some manual verification on top of the automation, but the heavy lifting is automated. We also use AI to help analyze code discrepancies between versions and are continually incorporating AI into more of our tools.

We need access to either a previous sandbox or the production environment - not necessarily the new sandbox with the 90-day window. We just need to see what's there. Then we take time to analyze it, define the scope, review the environment, and give you a quote. The analysis piece is at no cost. Three components drive the price: the modules the customer uses (for system integrity testing), the number and size of customizations, and the number of ISVs. We have an intake form that captures all of this.

We don't request a sandbox while we're upgrading customizations - we do that work on our local environment while we coordinate with ISVs to collect their packages. When both are ready, that's when we ask you to request the sandbox so the 90-day window starts when we're already prepared. Then we deploy customizations, run regression testing, and the client does their review. This way, the client doesn't need 60 days to test because we're delivering a fully tested system - they're just doing smoke testing at a higher level.

Modern UI conversion is a separate exercise. We can package it together with the upgrade, but it will be a different line item in the cost. If you're upgrading to 25R2 or later, we'll ask if you need Modern UI conversion for customizations and include it at that point. Classic UI will be deprecated in 26R2, so it makes sense to plan for this. We have a special program for Modern UI migration and have done a lot of conversions already - including for our own ISV products (Property Management, Cash Basis).

Absolutely. Many partners present this as their own program to clients. You can say it's your upgrade service - we work behind the scenes. Communication with the client goes through you, and we coordinate everything with your team. We have a portal where you can track progress in real time, and after the upgrade is done, we provide the updated source code back to you for your repository. The pitch to your client is simple: "We want to take the onus off of you for testing."