TL;DR — Quick Summary
- Migrating a Clover or Square merchant to a white label POS is a relationship decision, not just a software swap: The terminal may look different, but the merchant’s trust is built on continuity — of their data, their training history, their relationships with staff, and their day-one experience on the new platform. If you lose those in the migration, you lose the account regardless of how good the new platform is.
- The migration window is 90 days — and it decides retention: The first three months on a new platform are when merchants form habits, judge support quality, and decide whether to stay or churn. Every decision in the migration — data completeness, training depth, communication timing, and incentive structure — shapes whether the merchant emerges loyal or already gone.
- A structured migration checklist prevents the surprises that kill accounts: Most migration failures are not caused by the new platform — they are caused by missing data, a poorly timed switchover, under-trained staff, or an incentive structure that signals “we are not sure about this either.” The ISO that migrates with a checklist migrates with confidence; the one that wings it loses accounts in the 90-day window it never sees coming.
Window
Migration Source
Migration Guide
What Every ISO Should Know About Migrating from Clover or Square
Most POS migration guides are written for the ISO — they cover contract terms, data formats, and technical checklists. This one is written for the relationship: what the merchant experiences, what they fear, and what makes them stay loyal through a platform switch rather than using it as a reason to leave. The technical steps matter; the human steps matter more.
If you are an ISO with Clover or Square merchants, you face a growing question: whether to help those merchants migrate to a white label platform under your own brand. The answer depends partly on economics, partly on the merchant relationship, and partly on whether you can execute the migration without losing the account in the transition. This playbook covers all three — with a checklist you can use on day one.
Square Dashboard
for each migration phase
from day one
reduce migration friction
1. When to Propose a Migration — and to Which Merchants
Migration is a fit conversation, not a sales pitch: not every Clover or Square merchant should migrate. High-volume, multi-location, or growth-stage merchants are the natural candidates — they are the ones whose needs a white label platform can serve better and whose accounts justify the investment. Low-volume merchants already on a cheap flat-rate plan rarely benefit from the switch; pitch them and you create a churn risk for a migration you did not need to make.
Propose migration when you have a genuine improvement to offer: better pricing at the merchant’s volume tier, features the current platform lacks (multi-location management, loyalty, advanced analytics), or a support model that better matches the merchant’s needs. The merchant who sees a clear “what’s in it for me” migrates willingly; the one pitched on “our new platform” because it is good for you churns at the first frustration.
Sequence matters: approach your strongest merchant relationships first. If you lose a migration with a tier-one account, the signal spreads fast. Start with accounts where you have trust depth, and use those migrations as proof points for the ones that come after.
2. Exporting Data from Clover: REST API and CSV
Clover REST API — for structured data: Clover exposes a REST API that returns orders, payments, customers, and item data in JSON format. Authenticate with an OAuth token tied to your merchant account, then pull the relevant endpoints before the migration date. The API returns transaction-level detail including timestamps, payment methods, and line items — everything needed to reconstruct the merchant’s sales history on the new platform.
Clover Dashboard CSV export — for quick inventory and item data: the Clover Dashboard lets you export items, modifiers, categories, and employee records as CSV files directly from the web console. This is the fastest way to move the product catalog. Run the export 48–72 hours before the migration cutover, then import into the new platform’s item management tool.
Verify data completeness before the cutover: run a reconciliation check comparing total transaction volume from the Clover export against the Clover settlement statements for the same period. Any gap larger than 0.1% warrants investigation before you migrate. Missing transactions on day one erode merchant trust immediately — and give the merchant a reason to blame the new platform for the data problem.
3. Exporting Data from Square: Dashboard Export
Square Dashboard export — the primary tool: Square’s Dashboard lets you export sales reports, item performance, customer lists, and payment summaries as CSV from the Reports tab. Run full-period exports covering at least the last 12 months of transaction history — this gives the new platform enough data to generate meaningful reports from day one and gives the merchant continuity in their analytics.
Square Items Library export: from the Items section of the Dashboard, export the full item catalog including modifiers, categories, and item images. Square stores items as a structured catalog that maps cleanly to most POS import formats. Run this export early — it often surfaces items in the Square system that the merchant has forgotten about, and finding those now rather than on day one of the new platform matters.
Customer data and loyalty history: if the merchant used Square Loyalty or Square Appointments, export the customer list and loyalty points data from the Customers tab. This is often the most sensitive data to migrate and the most important for retention — the merchant has built a customer base inside Square, and losing that history undermines the value of the migration in the merchant’s eyes.
4. The Migration Conversation: Merchant Communication Templates
Phase 1 — Early outreach (4–6 weeks before migration): introduce the conversation as a check-in, not a pitch. Reference what you know about the merchant’s business — their volume, their setup, the features they use. Present the white label platform as something you have evaluated specifically for their situation, with concrete improvements listed. Do not mention Square or Clover by name yet; let the value proposition stand on its own.
Phase 2 — Data confirmation (2 weeks before): once the merchant agrees to migrate, confirm in writing what data will be transferred, what will not, and how long the process takes. Give the merchant a named contact they can reach during the migration — and make sure that contact actually responds within 24 hours. A merchant left waiting during a data migration is a merchant who calls their old vendor.
Phase 3 — Cutover day (day one): be on-site or on the phone at opening. Walk the staff through the new interface on live orders before the first rush. This is the moment that determines the merchant’s first impression — a smooth day one converts a skeptic; a rough day one without support converts a skeptic into a churner.
5. Managing the 90-Day Window and Minimizing Churn
Week 1–4: prove the basics work: the merchant’s primary concern in the first month is whether orders ring up correctly, whether reporting is accurate, and whether support answers. Answer those three questions affirmatively every time and the merchant settles into the new platform. Let any of them fail and you have planted doubt that grows into a cancellation request.
Week 5–8: show the delta: by week five the merchant is past the adjustment phase and ready to evaluate. This is when you surface the features the new platform has that the old one did not — a loyalty report, a multi-location comparison, a real-time sales dashboard. The merchant who sees something on the new platform they could not get on the old one becomes a retention case, not a churn risk.
Week 9–12: formalize the relationship: schedule a QBR-style check-in at the 60-day mark. Bring a written summary of the merchant’s performance on the new platform versus the same period on the old one. Present the data, ask what they want to improve, and propose next steps. This cements your role as an advisor — the ISO that brings data to the relationship, not just a terminal.
White Label POS Migration Checklist — Clover or Square to Your Platform
| Phase | Task | Owner | Timing |
|---|---|---|---|
| Pre-Migration | Assess merchant fit — volume, locations, growth stage | ISO | Week -6 |
| Export Clover API data (JSON) and Dashboard CSV; Square Dashboard CSV exports | ISO | Week -2 | |
| Reconcile export totals vs. settlement statements (<0.1% variance) | ISO | Week -2 | |
| Outreach | Send Phase 1 introduction — value proposition, no platform named | ISO | Week -4 |
| Confirm migration scope, data scope, and named contact in writing | ISO + Merchant | Week -2 | |
| Cutover | Import items, customers, and loyalty data into new platform | ISO | Day 1 AM |
| On-site or live phone support during first service rush | ISO | Day 1 | |
| Verify first-day transaction totals match pre-migration baseline | ISO + Merchant | Day 1 PM | |
| 90-Day Retention | Weekly check-ins weeks 1–4; surface new features at week 5 | ISO | Day 7–60 |
| 60-day QBR: written performance summary vs. prior platform period | ISO | Day 60 |
How OrderPin Supports ISOs Through Every Migration
OrderPin is a white-label POS platform built for ISO and MSP partners. For an ISO migrating Clover or Square merchants to a white label platform, OrderPin’s program is designed to make the transition smooth for both the ISO and the merchant — so the relationship survives the cutover and compounds from there. Through full data ownership, flexible pricing, and seamless API integrations, an ISO can build a recurring revenue business under its own brand without building software from scratch.
- Keep the merchant relationship in your name: the white label platform carries your brand, not the old vendor’s — so the merchant’s first experience of the new platform is of you, not a faceless switch.
- Import what matters, skip what does not: OrderPin’s item and customer import tools accept standard CSV formats compatible with Clover and Square exports, so the migration is a data move, not a data reconstruction.
- Be present on cutover day: OrderPin’s ISO partner resources include a migration playbook designed to help ISOs be on-site or on the phone at the moment that decides whether the migration sticks.
- Grow the account from day one: modular add-ons — loyalty, analytics, online ordering — give the ISO the tools to show the merchant something new on the new platform by week five, converting a skeptic into a loyal account.
Frequently Asked Questions
How do I export data from Clover?
Use two tools in parallel: the Clover REST API (authenticated via OAuth tied to your merchant account) to pull structured order, payment, and customer data in JSON, and the Clover Dashboard CSV export for items, modifiers, categories, and employees. Run both exports 48–72 hours before the migration cutover and reconcile total transaction volume against your settlement statements — a gap larger than 0.1% warrants investigation before the cutover date.
How do I export data from Square?
From the Square Dashboard, use the Reports tab to export sales data as CSV for at least 12 months of history, the Items section to export the full item catalog including modifiers and categories, and the Customers tab to export the customer list and loyalty data if the merchant used Square Loyalty or Appointments. Run the full export sequence at least two weeks before the migration date to allow time for reconciliation and for finding catalog items the merchant has forgotten about.
When is the right time to propose a migration to a merchant?
Propose migration when you have a genuine, concrete improvement to offer — better pricing at the merchant’s volume tier, features the current platform lacks, or a support model that better matches their needs. High-volume, multi-location, and growth-stage merchants are the natural candidates; low-volume merchants on a flat-rate plan rarely benefit. Approach your strongest merchant relationships first — a successful migration with a tier-one account becomes the proof point for every conversation that follows.
What is the 90-day migration window and why does it matter?
The first three months on a new platform are when a merchant forms habits, judges support quality, and decides whether to stay. Weeks 1–4 are about proving the basics — correct orders, accurate reporting, reachable support. Weeks 5–8 are about showing the delta — features the new platform has that the old one did not. Weeks 9–12 are about formalizing the relationship with a QBR-style check-in and a written performance summary. Every decision in the migration — data completeness, training depth, communication timing, incentive structure — shapes whether the merchant emerges from the 90-day window loyal or already gone.
How do I structure a conversion incentive for a migrating merchant?
Structure the incentive around what the merchant actually risks in the migration: a reduced or waived setup fee in the first 90 days, a rate guarantee for the first 6 months, or a feature upgrade (loyalty or analytics) at no additional cost for the first year. Avoid cash upfront — it signals uncertainty. Instead, tie the incentive to the merchant’s success on the new platform: a performance review at 90 days where both sides assess whether the migration delivered what was promised. The merchant who sees a fair deal tied to their results migrates with commitment; the one who got a cash bribe migrates with suspicion.
What kills migrations and how do I prevent them?
The three migration killers are missing or incorrect data (reconcile before the cutover, not after), a rough day one without ISO support (be on-site or on the phone at opening), and a poorly timed or generic outreach message (lead with what is better for this merchant specifically, not “we have a new platform”). The fourth killer is the incentive that signals you are not sure about the migration either — if you are hedging the conversion with cash, the merchant reads the hesitation and wonders what you know that they do not.
Migrating a Clover or Square merchant to a white label POS is a relationship decision, not just a software swap — and the merchant’s trust in the migration is built on continuity of data, training history, staff relationships, and day-one experience. The 90-day migration window is when the account is won or lost: weeks 1–4 prove the basics work, weeks 5–8 show the delta from the old platform, and weeks 9–12 formalize the relationship with a data-backed QBR. Every migration killer — missing data, no cutover support, generic outreach, and hesitant incentives — is preventable with a checklist and a commitment to being present on day one. The ISO that migrates with structure keeps the merchant; the one that wings it loses the account in the 90-day window it never sees coming. OrderPin is a white-label POS platform built for ISO and MSP partners — giving you the tools, the import compatibility, and the partner resources to make every migration a retention story.
About OrderPin
OrderPin is a white-label POS platform built for ISO and MSP partners. We offer full data ownership, flexible pricing, and seamless API integrations to help you build a recurring revenue business under your own brand. Learn more about OrderPin’s white-label solution
