The short version: payback period in years equals total migration cost divided by annual saving. The trap is that buyers underestimate the migration cost and overestimate the saving, which makes every switch look better than it is. Build both sides honestly and the number tells you whether to move or to use the model as leverage to stay. This calculator is part of our wider ITSM TCO calculator toolkit.
What are the inputs?
Two sides. On the cost side, everything you pay once to move. On the saving side, the recurring difference between the old run cost and the new one. Get both complete before you divide.
| One-time migration cost | Annual saving |
|---|---|
| Implementation and configuration | New subscription versus old run cost |
| Data migration and cleansing | Avoided uplift on the incumbent, compounded |
| Integration rebuild | Reduced add-on and module spend |
| Dual-running both platforms | Right-sized seat count on the new platform |
| Training and change management | Lower AI or consumption cost, if applicable |
| Internal staff time | Support and maintenance difference |
The two costs buyers forget most are dual-running and internal time. You almost always pay for both platforms during the cutover, and your own team's hours are real money even when no invoice records them. Leave them out and the payback looks artificially short.
How do you run the calculation, step by step?
- Total the one-time cost. Add every line in the left column. Be generous; this is the figure that protects you from a bad switch.
- Total the annual saving. Subtract the new annual run cost from the old, then add the avoided uplift you would have paid on the incumbent. Use the multi-year ramp modeling worksheet to project both across the term.
- Divide. Migration cost over annual saving gives the payback period in years.
- Compare to the term. If payback is shorter than the new contract term, the switch recovers before you renew. If it is longer, the move needs a non-cost justification.
- Run the incumbent counter. Re-run the saving assuming your incumbent matches part of the new price. Often the renewal concession closes most of the gap, and staying wins.
A worked example
Take a mid-market estate paying $300,000 a year on its incumbent, facing an 8 percent uplift, looking at a new platform quoted at $210,000 a year. The one-time migration cost totals $250,000 once dual-running and internal time are included.
| Line | Figure |
|---|---|
| Old annual run cost | $300,000 |
| New annual run cost | $210,000 |
| Annual saving (year one) | $90,000 |
| Avoided uplift, year one | $24,000 |
| Total annual saving | $114,000 |
| One-time migration cost | $250,000 |
| Payback period | about 2.2 years |
On a three-year term, this switch pays back with roughly nine months of saving to spare. These figures are illustrative; your real inputs will differ, and the avoided uplift in particular varies by deal size and the cap you can negotiate. The point is the structure, not the specific numbers.
When does migrating actually win?
When the payback is comfortably inside the term and the incumbent will not match the gap. End-of-life deadlines tighten the case: a platform being retired forces a move regardless of payback, which is why migration math matters most for buyers on sunsetting products. The deadline-driven versions of this are covered in our migration guides, including the Cherwell to Freshservice migration guide.
When the payback runs past the term, treat the switch as a capability decision and justify it on the features, not the savings. And in every case, run the incumbent counter first, because the cheapest migration is often the one you use as leverage and never make.
The gated CIO and CFO guide to ITSM cost includes the full payback worksheet with the dual-running and internal-time lines built in.
What to do next
Build both sides of the model honestly, divide, and compare to your term. Then take the result to your incumbent before you commit to a move. If you want the payback modelled and the incumbent counter run for you, our contract negotiation service does both on fixed fee or gainshare.
Frequently asked questions
- How do you calculate ITSM migration payback?
- Divide the one-time migration cost by the annual saving the new platform delivers. Migration cost includes implementation, data and integration rebuild, dual-running, training and internal time; the saving is the difference between old and new run cost with the uplift compounded.
- What is a good payback period?
- It varies by deal size, but most buyers want payback inside the new term, often inside two years, so the switch is recovered before the next renewal. A payback past the term makes the move a strategic choice, not a cost-saving one.
- Should payback drive the decision to switch?
- It should inform it, not decide it alone. A credible payback model is also leverage: a costed, real alternative often produces a renewal concession that beats migrating. Build it even when you intend to stay.
Model the switch before you commit.
We build the payback both ways and run the incumbent counter, so you move only when it pays. Fixed fee or gainshare.
Book a contract negotiation review →