Suger is now Fours. Read the announcement

Cloud Marketplace Platform Migration: A Checklist

Switching cloud marketplace platforms without breaking live revenue: what to check before, during and after a migration, and the risks to retire first.

Chloe Wu
Aug 18, 2026 ·

Cloud marketplace platform migration is the process of moving your listings, private offers, metering and co-sell operations from one system to another without interrupting live revenue. Done in the right order, it need not delist a product, lose the history the marketplace still holds, or break your ability to close deals.

Updated November 6, 2026: an earlier version of this post promised that a new platform reads in your full history, that a migration never needs delisting or downtime, and that the history sync takes hours. How far back history reaches depends on each marketplace’s retention, and the sections and FAQ answers below now state the conditions the other answers rest on.


Most teams reach a marketplace platform migration the same way they reached the platform in the first place: something stopped fitting. The tool covers one cloud and you now sell on three. Metering breaks on a pricing model it was never built for. Support answers slowly, or the renewal quote arrives and the value no longer matches it. So you evaluate an alternative, pick one — and then the real question surfaces, the one that stalls more switches than any feature gap: how do we move without breaking the revenue we already have?

That fear is rational. Marketplace revenue is live contracts, active entitlements, and metering records that turn into invoices. Nobody wants to be the person who delisted a product or dropped a usage record chasing a better dashboard. But the fear usually outruns the actual risk, because the mechanics of a marketplace migration are more forgiving than they feel — if you understand where your data really lives and sequence the cutover correctly.

This is a checklist for switching cloud marketplace platforms without interrupting the money.


What is a cloud marketplace platform migration?

A cloud marketplace platform migration is the move from one marketplace operations tool — in-house or third-party — to another, covering listings, private offers, metering, co-sell and CRM sync. It is a change of the software that operates your marketplace motion, not a change to the marketplace listings themselves.

That distinction is the whole reason a migration can be low-risk. Your listings, contracts, entitlements and historical transactions are the marketplace’s records, held in AWS, Microsoft, Google Cloud or wherever you sell — not your platform’s private property. A platform reads and writes to those records through each cloud’s seller APIs; it does not own them. Switching platforms means pointing a new tool at the same underlying records, the way you would connect a new BI tool to a database you already have. The database — your marketplace — does not go anywhere.

Get that mental model right and most migration anxiety deflates. You are not moving your revenue. You are changing what operates it.


Do you have to delist to switch platforms?

Not when your listings are published from your own seller accounts. Then delisting is not a step in a platform migration, and any process that starts by taking your products down is doing it wrong. Your existing listings stay published, buyers keep transacting, and you keep creating private offers and closing deals throughout the switch and after it.

This is the single most common misconception, and it comes from conflating two different things: the listing (published on the marketplace) and the platform (the tool you use to operate it). You can change the second without touching the first. A new platform connects to your seller accounts alongside whatever you use today; for the early part of a migration both can be connected at once, because reading marketplace data is non-destructive. Nothing is removed until you choose to sunset the old tool at the very end.

If a switch would require you to delist and republish, treat that as a red flag about the incoming platform’s integration model — not as a cost of migrating.


Will you lose your historical revenue data?

Not the history the marketplace still holds. Historical private offers, entitlements, usage records and disbursements are stored by the cloud marketplace, so a new platform can read them in once it connects — you are not carrying a data export across from the old tool. How far back that reaches depends on each marketplace’s retention: Snowflake’s disbursement report, for one, keeps 365 days.

This is the direct consequence of the “your data lives in the marketplace” principle above. Because the marketplace is the system of record, history is not something the old platform hands you on the way out; it is something the new platform reads in on the way in. A well-built platform back-fills past offers, contracts, revenue and usage on connection, so you have continuity from day one rather than a blank slate that starts accumulating only after go-live.

Two caveats worth confirming before you commit. First, ask how far back the incoming platform pulls history and whether it reconciles historical disbursements, not just current pipeline. Second, if you have derived data that lives only in the old tool — custom fields, internal notes, tags you added — that is genuinely yours to export, because the marketplace never saw it. So is any history older than the marketplace still keeps: if the old tool holds a copy, export it before you sunset that tool.


The migration checklist, phase by phase

A safe marketplace platform migration runs in four phases, each of which can be verified before the next begins. The rule that keeps the risk low: nothing destructive happens until the final phase, and by then you have already proven the new platform works.

PhaseWhat happensHow to keep it safe
1. Connect (read-only)New platform integrates with your marketplace seller accounts and syncs historical and current listings, offers, entitlements, revenue and usageVerify the connection is passive and read-only at this stage. It should not touch your live listings or your existing tool. This is where you confirm history came across correctly.
2. Parallel-runBoth platforms stay connected. You reconcile the new platform’s view against your current tool and your CRMCompare offers, entitlements and disbursements across systems until the numbers match. Do not cut over anything you have not reconciled.
3. Cut over per workflowMove one workflow at a time — start creating new private offers, then co-sell, then metering — in the new platformSequence by blast radius. New offers first (the old tool is still there to fall back to), metering last if usage-based (it feeds invoices, so it is the least forgiving).
4. Sunset the old toolOnce end-to-end tests pass, decommission the previous in-house or third-party solutionThis is the step that removes your way back, so it comes last — after you have transacted real deals on the new platform, not before.

Until the last phase the old tool is still there to fall back to, and every phase is verifiable. If you cannot reconcile phase two, you do not proceed to phase three — you have lost nothing but time.


The one workflow to migrate carefully: metering

Usage-based metering is the only part of a marketplace migration that touches active invoices, so it gets its own care. If your pricing is contract- or seat-based, this section does not apply and your migration is simpler; skip to the takeaways.

For usage-based products, metering records are what the marketplace turns into buyer invoices, which means an error here is a billing error, not a cosmetic one. The safe pattern is to start reporting usage to the new platform’s metering endpoint in parallel, confirm the records match what you have been sending, and only then stop reporting through the old path. Never dual-report the same usage to the same marketplace from two systems at once, and never cut the old path until the new one has produced correct records across a full billing cycle. Metering is migrated last for exactly this reason — it is the workflow where “verify, then switch” earns its keep.

For the deeper mechanics of metering accuracy and pricing models, see the Fours billing and metering platform.


How Fours approaches migration

Fours is a Cloud GTM platform for selling and billing across six marketplaces — AWS, Microsoft, Google Cloud, Snowflake, Alibaba Cloud and Oracle — and it is built to be adopted the low-risk way this checklist describes. The initial integration is passive and read-only: it connects to your seller accounts, syncs historical and current listings, private offers, entitlements, revenue and usage, and gives you visibility from day one without touching your live listings or your existing tool.

From there the cutover follows the phases above. You keep closing deals throughout, migrate usage metering to the Fours metering API only if your pricing is usage-based, and sunset the previous solution as the final step — a few clicks, after end-to-end tests pass. If your motion runs through resellers as well as direct, Fours PRM migrates alongside it, onto the same platform that operates your transactions: partners, contacts and deal registrations come across in one import with no commission attached, and past deals whose commission you want on record through a separate one; moving partners, contacts and deal history in a PRM migration has its own order and its own guardrails.

For the broader question of which platform to switch to, our guide to how to choose a cloud marketplace platform covers the evaluation criteria; this post is about moving once you have chosen.


Frequently asked questions

Do you have to delist products to switch marketplace platforms? Not when your listings are published from your own seller accounts. A new platform then connects alongside your current tool and reads marketplace data non-destructively; your listings stay published, and nothing is removed until you sunset the old system.

Will you lose historical revenue data when migrating? Not what the marketplace still holds. Offers, entitlements, usage and disbursements are the marketplace’s records, so a new platform reads them in. How far back depends on each marketplace’s retention — Snowflake’s disbursement report keeps 365 days — so export anything older the old tool holds before you sunset it.

Is there downtime or a period when you can’t close deals? Not if both platforms can stay connected while you reconcile. You keep creating private offers and closing deals throughout, cut over one workflow at a time, and sunset the old tool last. If either tool can’t run alongside the other, plan for that gap before you start.

How long does a marketplace platform migration take? It depends on how many marketplaces and workflows you run, how much history the new platform reads in, and whether you meter usage. Usage-based metering adds a verification cycle because it feeds invoices; contract- and seat-based products migrate faster. Ask the incoming platform for its sync time.

Which workflow is riskiest to migrate? Usage-based metering, because its records become buyer invoices. Migrate it last, report to both systems in parallel first, confirm the records match across a full billing cycle, then stop reporting through the old path. Offers and co-sell updates reach buyers and clouds too, so reconcile each before it moves.

In what order should you cut over? Sequence by blast radius. Connect read-only and reconcile first, then move new private offers, then co-sell, then metering if usage-based. Sunset the old tool only after real deals have transacted on the new platform.


Takeaways

  • Your revenue lives in the marketplace, not in the platform. Listings, contracts, entitlements and history are the marketplace’s records — switching tools points a new one at the same data, so most migration risk is perceived, not real.
  • Never delist. If a switch would require taking products down and republishing, that is a red flag about the incoming platform, not a cost of migrating.
  • Run it in four phases — connect read-only, parallel-run and reconcile, cut over per workflow, then sunset — so nothing destructive happens until you have already proven the new platform works.
  • Migrate usage-based metering last and in parallel. It is the only workflow that feeds buyer invoices, so it is the one place “verify, then switch” is non-negotiable.
  • Keep closing deals the whole time. With both platforms connected while you reconcile, a sequenced migration needs no shutdown window.

The reason a marketplace platform migration feels risky is that it looks like moving your revenue, when it is really just changing what operates it. Sequence the cutover so the step that removes your way back comes last, and the switch is as safe as the platform you move to. See how the operations you would move fit together on the Fours platform.

Sources

Primary sources for the platform rules cited above. Last verified November 6, 2026. Cloud providers change fees, eligibility, and program terms without notice — check the source before relying on a figure.

Browse every post on the Fours Blog

Stay Updated

New posts, product updates and marketplace strategy are shared on LinkedIn as they publish.

Follow Fours on LinkedIn