Switching marketplace integration providers can be done without stopping sales; the condition is that the new system only watches for a while and write permission is handed over one channel at a time. Everything except two systems writing to the same channel at once is manageable. This article covers the plan from decision to shutting down the old system, the risks, and a checklist.
When is it time to switch?
Not every glitch calls for a new provider; sometimes a setting or a training session fixes it. But if the following symptoms have become permanent, it is time to plan a move:
- Stock updates lag and overselling has become routine.
- Connecting a new marketplace has been "on the roadmap" for months.
- Settlement and return tracking happens outside the system, in spreadsheets.
- When something breaks, nobody can say which system it broke in.
- The team has drifted back to the marketplace seller panels instead of the integration.
When evaluating candidates, put them through the list in 15 questions to ask before choosing an integration provider. Do not decide until you have seen, concretely, how the thing that bothers you in the old system is solved in the new one.
The biggest risk: two systems, one channel
There is one disaster scenario in a provider switch: two systems writing stock or price to the same marketplace at the same time. One sets stock to 10 while the other writes 3; a price is on campaign in one system and at list price in the other. The result is cancellations, penalty points, and complaints.
The fix is simple but demands discipline: one writing system per channel. Throughout the transition, keep a list of which channel belongs to which system and update it at every handover. In Bulutegra this is handled by the ownership flag at product and channel level; if a channel is marked as managed by an external system, the panel reads from it but never writes.
"Let's be quick and flip everything the same day" is the most expensive sentence in a migration. A channel-by-channel plan always finishes sooner than a same-day plan, because it never has to be rolled back.
The step-by-step migration plan
The sequence below matches Bulutegra's four-step setup; the same logic works with any system.
- Take inventory. Which channels are connected, which ERP or web store is the master catalog, how many products and variants exist, and which special rules (floor prices, channel-specific pricing, campaigns) are defined? Export all of it from the old system.
- Clean the data. Do not carry products with code conflicts into the new system. Move to one SKU and one barcode per item; matching products by SKU and barcode explains the method.
- Connect. Grant marketplace API access and the ERP connection in the new system. This usually takes half a day; the old system keeps running.
- Match. Link products to channel listings by SKU and barcode. Drive the unmatched list to zero; allow one to three days.
- Watch in shadow mode. The new system reads only, for one to two weeks. Compare the stock and prices the old system writes with what the new one calculates. Any difference points to a mapping or rule issue; fix it here. Testing an integration in shadow mode has the details.
- Hand over channel by channel. Start with the lowest-volume channel. Turn off writing for that channel in the old system and turn it on in the new one, both on the same day. Watch for a day or two, then move to the next channel.
- Shut down the old system. Once every channel is handed over, export the last remaining data and revoke the old system's API access. An old system whose access was never revoked can make an unexpected write months later.
What the team does during the switch
A migration is not a one-person job; assign roles from the start.
- Admin keeps the handover calendar and approves each step.
- Content closes the unmatched product list and reviews the new system's quality findings.
- Warehouse compares order counts in both systems throughout shadow mode: old system in the morning, new system in the morning.
- Accounting reconciles the migration month's settlements with extra care, because order records may be split across two systems.
For team structure, see team roles for multichannel selling.
Timing: when not to switch
Campaign periods, year end, and the weeks before holidays are the wrong time; the margin for error narrows when volume is high. The preferred window is a month with relatively calm order volume and the full team available. Map the campaign calendar as described in stock and price management during campaign periods and fit the migration into a gap.
On the contract side, set the old provider's end date at least two weeks after the planned end of the migration, not on it. If something goes wrong during handover, you want somewhere to roll back to.
Migration checklist
Tick every item before you begin:
- Product mapping, order history, and settlement records exported from the old system as CSV.
- Product catalog cleaned to one SKU and one barcode per item.
- Channel list written down with owner and handover date for each.
- Floor price, campaign, and channel-specific pricing rules moved to the new system and verified.
- New system ran in shadow mode for at least a week; stock and price differences reduced to zero.
- First channel to hand over chosen and that day's schedule announced to the team.
- Date for revoking the old system's API access decided.
- Settlement reconciliation for the migration month planned with extra attention.
How it works with Bulutegra
Moving to Bulutegra runs in four steps: connect, match, watch in shadow mode, hand over channel by channel. In shadow mode the system only reads; your current provider keeps working in the meantime. The ownership flag makes it clear at product level which channel belongs to which system and prevents both from writing to the same listing. After handover, channel monitoring runs continuously and a channel that goes quiet raises an alert. Details of the setup process are on the Why Bulutegra? page.
To build a migration schedule for your own setup, request a demo or write to destek@bulutegra.com.
Frequently asked questions
Do sales stop when you switch integration providers?
Not when it is planned properly. The new system first runs in shadow mode, reading only, while the old system keeps writing. Write permission is then handed over channel by channel; as long as only one system writes to each channel, order and stock flow never stops.
How long does the switch take?
It depends on catalog size and number of channels. Typically connection takes half a day, matching one to three days, and shadow mode one to two weeks. Channels are then handed over one at a time. The most important rule is to avoid campaign periods.
How do I get my data out of the old provider?
Before ending the contract, export the product mapping list, order history, settlement records, and channel settings as CSV. Listings and orders on the marketplaces themselves stay on the marketplaces; they are not deleted when you change providers.
