Changing Platforms? What Comes Out Cleanly Now, and What You Still Rebuild by Hand

Ask a distributor who replatformed in 2015 what the migration felt like and you will hear about spreadsheets. Order history arrived as a flat CSV with the line items collapsed. Product images came on a drive, or by FTP, named after internal IDs nobody recognized. Customer-specific pricing, the thing the business actually ran on, often could not be extracted at all without a paid engagement from the vendor whose platform you were leaving. The quote was rarely small, and the timeline was never yours.

That has changed, and the change is worth understanding before you sign anything, because it shifted where the risk sits rather than removing it.

The export button used to be an afterthought. Now it is a sales feature

Ten years ago, data access was something you negotiated after the fact. Today most serious platforms expose a documented API covering products, customers, orders, quotes and price lists, plus bulk export endpoints built for volume rather than a browser timeout. Several publish direct sync into a cloud data warehouse, so the operational data lands somewhere you control while the platform is still live. That single shift matters more than any migration tool: if your order and customer records are already replicated into your own warehouse, leaving stops being an extraction project and becomes a cutover.

The commercial reason is straightforward. Buyers started asking. Procurement teams evaluating b2b ecommerce software now routinely ask for the exit path in the first demo, and vendors who can answer plainly win deals against vendors who change the subject. Data protection law aimed at consumers pushed portability language into contracts that have nothing to do with consumers, and the Federal Trade Commission's oversight of how companies handle and disclose customer data has kept the topic in front of general counsel. The practical result is that a clear export story is now something a vendor advertises rather than something you extract under duress.

What comes out cleanly today

In most current platforms, expect to retrieve without much fuss:

• Product records, including attributes, variants and category assignments, usually with image URLs you can crawl.
• Customer and company records, contacts, addresses and account hierarchies.
• Order and invoice history with line-level detail, in a format that reconciles to your accounting system.
• Price lists and contract pricing as tabular data, where the pricing is stored as values.
• Documents and attachments, though sometimes only through per-record API calls rather than a bulk job.

That list would have been aspirational in 2015. It is now a reasonable baseline, and a platform that cannot meet it is telling you something.

What still does not come out, and what to do about it

The gap has narrowed but it has not closed. What resists export is logic rather than records.

Pricing rules are the big one. If your platform computes a customer's price from tiers, volume breaks, promotions and contract overrides, the calculated results may export while the rules that produce them do not. You get the answers, not the arithmetic. The fix is to document the rule set independently of the platform while you are still using it happily, ideally as a spreadsheet a person could follow by hand. That document survives every replatform you will ever do.

Integration mappings are second. EDI transaction sets, punchout configurations, ERP field mappings and middleware transformations live in the connective tissue between systems, and none of it is part of a data export. Keep those specifications in your own repository, not in a vendor's admin screen.

Third is anything rendered by a proprietary page builder. Landing pages, merchandising blocks and category content built in a visual editor typically export as either nothing or unusable markup. Content that lives as structured data in your own content system moves. Content that lives as drag-and-drop layout does not.

Finally, search synonyms, saved carts, abandoned quotes and internal notes tend to be the last records anyone builds an export for. Ask specifically, because the answer varies by vendor and the good ones will tell you straight.

Test the claim before you sign, not after you leave

Vendor documentation describes what the API can do. It does not tell you how it behaves against your data volumes on a Tuesday afternoon. Before signing, run a short drill:

1. Ask for sandbox credentials and pull a full product and order export yourself, or have your integrator do it. Time it. Note the rate limits.
2. Take one customer with complicated pricing and check whether the exported price list reproduces what the storefront actually shows them.
3. Read the termination clause for a defined post-termination access window, a stated format, and whether export assistance is included or billed. Thirty days of read-only access is common and reasonable; silence is not.
4. Confirm in writing who owns derived data such as usage analytics and search logs.

Vendors that have invested in portability answer these quickly, and the exercise costs you a couple of hours.

The useful consequence of the last decade is that switching cost is now mostly a matter of preparation rather than permission. Keep your pricing logic and integration specs written down somewhere the vendor cannot reach, replicate your operational records into storage you own, and the question of whether you can leave stops being a question at all.