Operational estimate
Compare the current contracted stack with a 12 January 2027 scenario. Savings are illustrative.
Illustrative operational estimate only. It does not claim that any charge is illegal, and it does not auto-zero egress for parallel or multi-cloud scenarios.
Pair this estimate with FX risk and international pricing margin tools, plus the switching readiness screen.
Adds data volume, egress, engineering, vendor support, downtime, replatform, parallel run, termination, and other costs. The January 2027 column removes a single-provider egress figure only as an illustration. Parallel, multi-cloud, and unknown patterns keep egress.
Current contract keeps entered fees. The January 2027 rule scenario illustrates removal of a single-provider switching-process egress charge. User-defined subtracts only the amount you enter.
Current switch cost is the sum of every line. Operating cost excluding switching charges drops the classified switching-charge amount. Potential savings compare the current total with the January 2027 scenario.
Savings are a discussion figure. Applicability of any switching-charge rule depends on the service.
Termination fees stay in the operating stack unless you place them in the user-defined switching-charge field. Nothing here declares a fee unlawful.
The calculator does not say that. It labels scenarios and shows an illustrative comparison.
Parallel and multi-cloud egress is not automatically treated as a switching charge for the switching process.
You choose the amount to set aside. The egress line itself stays in the breakdown.
No. Figures stay in the units you enter. Use the FX tool if you need a currency view.