10
Revenue Execution Series · 12 of 14

ERP Migration

10 Questions to Ask Before Your Next ERP Migration

ERP migrations fail for many reasons. But the most common is revenue: too much complexity embedded in the wrong layer, discovered too late in the program to do anything about it.

Why This Matters

The problem is structural.
Not operational.

61% of SAP ECC customers have yet to move to S/4HANA — more than a decade after release. Only 8% of SAP customers complete migrations on schedule. The obstacle, more often than not, is revenue complexity that cannot be cleanly mapped to the new system.

Revenue execution has been living in ERP for years. Pricing rules. Custom billing logic. Contract terms that required customizations. Every one of these is a migration risk. And the program typically discovers them after the budget has been set and the timeline has been committed.

These ten questions should be answered before the migration architecture is finalized. They are not process questions. They are architecture questions — specifically about whether revenue execution should continue to live in ERP at all.

"Revenue Execution does not get thrown away when ERP changes. It compounds. Every motion modeled becomes the foundation for the next."

ERP

10 Questions to Ask Before Your Next ERP Migration

01
Where does your revenue execution logic actually live today?
Pricing rules. Discount approval logic. Contract term enforcement. Billing calculations. These often live in ERP custom code, in ABAP programs, in configuration that was never formally documented. Before migrating, map the logic. You will find it in places that will delay your timeline.
02
How much of your ERP complexity is revenue-related?
Enterprise ERP migrations consistently find that the majority of customization complexity is revenue-related — not operational or financial. If you can externalize revenue execution before migration, you descope the hardest part of the program.
03
Can you descope revenue execution from the migration?
The question most migration programs do not ask until it is too late. Revenue execution does not need to live in ERP. If you build the execution layer before migration, the migration scope contracts significantly. What was a multi-year program can become a more predictable infrastructure project.
04
What happens to CPQ, billing, and commerce during cutover?
ERP cutover is a frozen window. Revenue motions slow or stop. Deals cannot close. Invoices cannot process. The longer the cutover window, the more revenue is at risk. If revenue execution is externalized, it runs independently of ERP — cutover stops the record-keeping, not the execution.
05
How long will revenue be frozen during migration?
Ask your program manager for the expected cutover window and the revenue impact. The answer is usually uncomfortable. Revenue Execution reduces that window significantly — because revenue logic lives outside the system being migrated.
06
What is your plan if the migration takes three times longer than expected?
Only 8% of SAP customers complete migrations on schedule. The typical revenue change program overruns by three to five times. Your migration is not exempt. What revenue capabilities does your business need in years two and three while the migration continues? Revenue Execution runs independently of migration timeline.
07
Is clean core actually achievable with your current revenue model?
Clean core is the S/4HANA mandate. It means no ERP customizations. But your current revenue model requires customizations. Every pricing exception. Every billing calculation. Every contract term that required a workaround. Clean core is only achievable if revenue execution is externalized.
08
What is the cost of revenue execution downtime?
If revenue-related systems are unavailable during migration, what is the daily revenue impact? Calculate it. Then ask whether the migration architecture can be changed to reduce or eliminate that window. Revenue Execution running outside ERP means it is not dependent on ERP availability.
09
Can you prove revenue behavior before you commit to cutover?
The most dangerous moment in a migration is cutover — when you find out whether the new system handles revenue correctly. Revenue Execution allows you to model and test revenue behavior in the new architecture before cutover. Problems are found before they cost revenue, not after.
10
What would it take to decouple revenue execution from ERP before you migrate?
This is the most important question on the list. If revenue execution is externalized before migration begins, the migration descopes significantly, clean core becomes achievable, and business revenue runs continuously through the transition. The decoupling is a program in its own right — and it is shorter than the migration it makes possible.

How Many Apply?

Where does your organization stand?

1–3 questions unanswered
Your migration architecture is more mature than most.
The revenue execution questions have been considered. The remaining risks are manageable. The right next step is validating that execution behavior in the new architecture before committing to cutover.
See how viax starts small →
4–7 questions unanswered
Revenue complexity will affect your migration timeline.
These are not minor gaps. They are the questions that determine whether your migration runs on schedule, over budget, or both. Revenue Execution externalization is worth evaluating before the program architecture is locked.
See a proof-of-value in days →
8–10 questions unanswered
Your migration carries significant revenue execution risk.
The answers to these questions, once discovered mid-program, are what drive the 3–5× timeline overruns. The time to address them is before the program starts — not when the executive sponsor is asking why the timeline has extended again.
Talk to viax this week →

The Evidence

The numbers are not subtle.

61%
of SAP ECC customers have yet to move to S/4HANA — more than a decade after release
8%
of SAP customers complete migrations on schedule — revenue complexity is almost always why
3–5×
typical timeline overrun for revenue change programs routed through ERP

ERP migration is inevitable for most enterprises. The variable is whether revenue execution migrates with it — or whether it moves into its own layer first, making the migration faster, cheaper, and far less risky.

Execute revenue change with confidence.

Start proof-of-value — test real execution without ERP risk. Reduce risk and demonstrate measurable revenue behavior before you commit teams, timelines, or transformation dollars.

Schedule a Demo See Execution in Action

The Revenue Execution 10 Series

Diagnostic 10 Signs You Have an Execution Gap Persona 10 Reasons Revenue Execution Matters to a CIO Persona 10 Reasons Revenue Execution Matters to a CFO Persona 10 Reasons Revenue Execution Matters to a CRO Persona 10 Reasons Revenue Execution Matters in M&A Motions 10 Things You Can Do With a Revenue Execution Layer Value 10 Things Revenue Execution Allows You to Do Competitive 10 Signs Your ERP Is Holding Your Revenue Back Competitive 10 Things CPQ, Billing, and Commerce Can't Do Competitive 10 Reasons Point Solutions Are the Wrong Answer Speed 10 Revenue Motions Every Enterprise Should Run in Days AI 10 Reasons AI Needs a Revenue Execution Layer AI 10 Things That Go Wrong When AI Meets a Fragmented Stack
ERP 10 Questions to Ask Before Your Next ERP Migration
ERP 10 Ways Revenue Execution Gives New Life to Your Existing ERP ERP 10 Ways Revenue Execution Derisks Your ECC to S/4HANA Migration ERP 10 Ways Revenue Execution Delivers What S/4HANA Promised
View all series →