A clienteling platform migration looks like a data project, and it isn't. Most of the risk sits in a promise: whatever your customers agreed to hear from you, and whatever they told you to stop sending, has to survive the move. Customer records, consent history, store phone numbers and associate workflow all go from the old platform to a new one, and the old one stays available as a fallback until the new one is verified.

This runbook covers what to inventory, how to move consent, the eight steps from export to cutover and what to ask a vendor. It's written for the retail operations leader who owns the rollout and the IT, security and procurement teams who sign it off. (Yes, that's a lot of signatures, so the table below has a column for them.)

Key takeaways

• A clienteling migration moves records, consent, store phone numbers and associate workflow, not just data fields.
• Consent and opt-out records are the brand's to prove, so they travel with the migration and stay suppressed on day one.
• Test in a sandbox, pilot a few stores and reconcile records, consent, returns and attributed sales before cutting over by wave.
• Keep the old platform available until the last wave's counts reconcile.

What does a clienteling platform migration involve?

A clienteling migration involves six things, as this runbook scopes it: customer profiles, purchase and returns history, associate notes, consent and suppression records, store phone numbers, and templates and permissions. The table shows what to confirm for each and who should sign it off.

Treat each row as a deliverable with a named signer. A row with no owner is a row nobody checks, and an unchecked row is how consent history gets left behind. So start by listing what you're moving.

What should you inventory first?

Inventory every system that holds customer data before you export anything, and name one system of record for each type of data. POS, ecommerce, email, SMS and the old clienteling tool all count, and so does the spreadsheet nobody admits to.

Each system needs an owner who can say where its data comes from and who edits it. Endear includes a defined system of record with every account, according to its enterprise page, and our POS CRM integration guide covers how to set the rules when stores run different systems. Once you know what you have, you can deal with the part that can't be rushed: consent.

How do you move consent and opt-outs?

Move consent and opt-out records with the customer, because the permission was given to the seller named in the agreement, which is usually your brand, and not to the software. For texts, prior express written consent is a signed agreement, with required disclosures, that authorizes the seller to send autodialed or prerecorded marketing messages to a named number. Recipients can revoke it by any reasonable method, and the sender has a reasonable time, not to exceed ten business days, to honor the request, per 47 CFR 64.1200.

So export the signed wording, the timestamp and the number with each record, not just a yes or no flag.

Pause marketing sends from both platforms during the final export, then run a last export of new opt-outs and re-run suppression before sends resume, so no opt-out is lost in the gap.

Email opt-outs have their own rule: a business must honor one within 10 business days. It also can't sell or transfer opted-out addresses except to a company hired to help it comply, per the FTC's CAN-SPAM compliance guide. Ask counsel whether your migration vendor fits that exception.

California consumers can also ask a business to delete their personal information, with exceptions, and to tell its service providers to do the same, per the California Attorney General's CCPA page. Deleted customers need to stay deleted in the new platform, and that's a requirement to test, not legal advice, so have counsel review it, including state rules and the name on the signed agreement, and confirm what is in force.

With consent handled, the rest is sequencing: what happens in which order, and who owns each step.

What does the migration runbook look like?

Here's the run order: eight steps, each with named owners.

1. Inventory and scope: list every system, field and store, and freeze the scope. Owner: the retail operations leader.
2. Define the system of record: decide which system owns profiles, purchases and consent. Owner: IT.
3. Export and map: pull records with their consent and suppression fields, and map each field to the new platform. Owner: IT and marketing.
4. Test in a sandbox: load a sample and check it before touching live data. Owner: IT.
5. Pilot a few stores: run real outreach from the new platform, on ported or temporary numbers, in a small group of stores. Owner: retail ops.
6. Train associates: teach the workflow by role, on the devices they use. Owner: store managers.
7. Cut over by wave: move stores in groups, port the remaining store numbers and keep the old platform available. Owner: retail ops and IT.
8. Reconcile and retire: match records, consent, returns and attributed sales, then switch the old platform off. Owner: IT and finance.

Write a rollback rule before step 7: the trigger, the owner and the way back to the old platform. A cutover without one has no plan for the bad day.

Endear's enterprise page lists a sandbox environment, phone number porting, a defined system of record and a structured onboarding cadence with every account. The enterprise tier adds a formal SOW and RACI, dedicated integration support, custom system migration and white-glove onboarding.

A runbook only earns its keep if you test it before the bad day, so here's how.

How do you test before cutover?

Test before cutover by reconciling four counts between the old and new platforms: records, consent, returns and attributed sales. Load a sample in the sandbox first, then run the pilot stores on live data.

Agree the attribution window and returns handling in writing before the pilot, because both change the totals.

Define done up front: counts reconcile, a pilot store sends from the right number and no opted-out customer receives a message.

Make the last one a full match: every opted-out record on the old platform is present and suppressed on the new one. Then spot-check it by picking ten customers who opted out in the past year and confirming none appears in a pilot store's send list. (Yes, a ten-customer spot check feels low-tech. It also works.) Treat consent as a go or no-go item, so if the consent count doesn't reconcile, the next wave waits.

Testing covers the data. The stores need looking after too.

How do you keep stores selling?

Keep stores selling by moving them in waves, outside peak trading weeks, and train associates on the devices they'll use every day. Nobody wants to learn a new system the Saturday before a holiday.

Shared store devices need their own protection, and Endear's enterprise page lists 2FA or PIN login with auto-logout for them. It also says its onboarding team came from retail sales floors, with prioritized chat support after go-live.

Adoption is its own project, and our guide to getting stores to use AI covers it. Once the stores are ready, the last job is choosing who you migrate with.

What should you ask a vendor?

Put five questions to every vendor, and get the answers in writing.

1. Which of our systems can you migrate from, and who runs the work?
2. How do you carry over consent records with their source, wording and timestamp?
3. Can we port our store phone numbers, and in what sequence?
4. Do you offer a sandbox, and how do we reconcile counts before cutover?
5. Which security attestations do you hold, and is your SOC 2 report Type II? SOC 2 reports cover controls relevant to security, availability, processing integrity, confidentiality or privacy, per the AICPA's SOC suite page.

For the wider evaluation, our enterprise clienteling software evaluation guide adds a short pilot checklist.

Frequently asked questions

How long does a clienteling migration take?

Migration time depends on the brand, its systems and its pilot. Endear's enterprise page describes one brand that went from a 10-store pilot to a 113-store rollout in two months, which is a rollout example from one vendor and not a migration benchmark.

Can you migrate consent records?

You can if the old platform exports them with their source, wording, timestamp and number. Confirm that before you sign, because a consent flag without its source can't prove permission.

Should you keep the old platform running?

Keep the old platform available until the last wave's counts reconcile. Retire it once finance and IT have signed off.

What is a system of record?

A system of record is the one system that owns a type of data, such as customer profiles, purchases or consent. Every other tool reads from it or syncs to it.

What should a pilot include?

A pilot should include a few stores on live data, real outreach from the new platform and a reconciliation of records, consent, returns and attributed sales against the old platform. Review the results before the next wave.

Ready to plan your migration?

A clienteling migration works when records, consent and store numbers move together and the stores keep selling. Endear is one example, with its implementation items listed on its enterprise page.

Want to see how a pilot would run against your stores and your stack? Book a demo.