Who this is for, and the warning signs
This guide is for brands that want to leave an agency, a freelance developer, an app, or a platform partner, and are worried about what they might lose on the way out: products, customer records, order history, or the integrations that keep the business running. If any of these sound familiar, it is time to plan an exit, even if you are not ready to leave yet.
Slow or vague responses
Simple requests take weeks, and answers to “where is this data?” get shorter every time you ask.
Access is withheld
You ask for an export, a login, or the code, and it is delayed, priced as extra work, or tied to an unpaid invoice.
Admin accounts in their name
The store owner account, the domain, or the analytics property was set up under the vendor’s email, not yours.
Integrations nobody can explain
Apps, scripts, and connections run in the background, and only the vendor knows what each one does or what breaks if it stops.
None of these mean the vendor is acting in bad faith. Often the setup just grew without anyone writing it down. But the risk is the same: the longer it goes on, the harder it is to leave cleanly.
Two ground rules before you start
Secure access before you announce anything
The quietest exits start with homework. Work out what you already control and back it up before you give notice. That way, a difficult conversation cannot leave you without your own data.
Contracts and ownership go to a lawyer
This is not legal advice. Questions about your contract, notice periods, unpaid invoices, or who owns the code, design, or content belong with a lawyer. This checklist covers the operational side: accounts, data, and the switch.
The vendor exit checklist
Six steps, in order. Each one ends with something you can check off.
1. Confirm what the brand owns
Start with accounts, not data. For each item below, find out who the owner is today. Anything in the vendor's name goes on a short list to move first.
| Account | What to check | Done when |
|---|---|---|
| Store admin and owner account | Who is the account owner, and whose email and payment method are on it? | The owner account is on a brand email, and the vendor is a staff or collaborator account you can remove. |
| Domain and DNS | Who holds the registrar login and the DNS provider account? | Both are in a brand-owned account, with renewal on a brand card. |
| Payments and paid apps | Which payment provider, subscriptions, and apps are billed to whom? | Every paid tool is billed to the brand, or you have a list of the ones that are not. |
| Theme and code repository | Where does the theme or custom code live, and who can download it? | You have a current copy, and the repository sits in an organization the brand controls. |
| Analytics and ad accounts | Who owns the analytics property, tag manager, and ad accounts? | The brand is the owner or admin, and the vendor is a user. |
| Email and SMS platform | Whose account holds your subscriber lists, flows, and sending domain? | The account is the brand’s, with at least two people from your team as admins. |
| 3PL, ERP, and helpdesk logins | Did the vendor set up these connections under their own credentials? | Each tool has a brand-owned admin login, and any connection keys are known. |
2. Inventory your data and integrations
Write down what exists before you move any of it. A simple spreadsheet is enough. List:
- Record counts: products and variants, customers, orders, and any subscriptions or gift cards.
- Content: pages, blog posts, images, and files hosted outside the store.
- Every app, script, and connection, what it does, and which account it runs under.
- Where data flows: store to 3PL, store to email platform, store to ERP or accounting.
- Anything custom: product fields, metadata, or tags that other tools depend on.
The counts matter most. They are how you will prove, later, that nothing was lost.
3. Export and back up
Export from accounts you already control first, and keep each file with the date and the record count. Cover:
- Products, including variants, prices, inventory, and custom fields.
- Customers, including tags and marketing consent.
- Orders and their history.
- Content and images.
- Every current URL, plus any existing redirects.
Most platforms have built-in exports. Shopify's admin can export products, customers, orders, and URL redirects as CSV files, and WooCommerce includes a product CSV exporter. Exports have gaps, though. Shopify notes, for example, that product images and collections are not part of the product CSV file. Check your platform's help docs for what each export leaves out, and keep the old store live until the new one is checked.
Store at least two copies in places the brand owns, such as a company drive and a second backup.
4. Plan the switch without downtime
The goal is a store that never stops taking orders. That usually means:
- Build and test the new setup alongside the old one, not on top of it.
- Do a full test run with the exported data and compare the counts.
- Pick a quiet window for the switch, away from launches and big sales.
- Plan a final sync for anything that changed since the test run, such as new orders and customers.
- Write down the rollback: what you do, and who decides, if something goes wrong.
5. Validate after the move
Check the same day, and again a week later:
- Counts match your inventory for products, variants, customers, and orders.
- Spot-check a sample of records by hand, including the odd ones with many variants or custom fields.
- Old URLs redirect to the right new pages, starting with your top-selling products.
- Analytics, ad pixels, and conversion tracking fire on a test order.
- Orders reach the 3PL, and customer data reaches your email platform.
6. Close access and rotate credentials
Once the new setup is stable, close every door the old vendor still has:
- Remove their staff, collaborator, and user accounts from every tool.
- Change shared passwords and replace any API keys or app tokens they could see.
- Turn on two-factor sign-in for every admin account.
- Cancel subscriptions you no longer need, and keep the backups.
When to get help
Plenty of brands can run this checklist themselves. It is worth bringing someone in when the vendor is not cooperating, when you have custom data that a standard export does not capture, or when the store is too busy to risk a messy switch. Cadence Ridge systems are designed to run in accounts your brand owns, so the next exit is easier than this one. How we grant, use, and hand back access is on our security and data handling page. Scope and starting prices are on the pricing page.