Skip to main content

POS migration

Switching from Clover to Square, run as a project instead of a weekend.

Most pages about this switch are written by somebody who sells one of the two systems. This one is written by the people who would do the work, and it starts with the parts that go wrong.

We work with Square, and we do not set up Clover. If the honest answer is that you should stay where you are and fix the configuration, that is the answer you will get.

Tell us what is happening on your floor →

The short answer

What happens when you switch from Clover to Square?

Your item library, categories and customer records move across as files. Your Clover terminals do not: Clover devices are locked to the merchant services provider that sold them and cannot be reprogrammed for another processor, so the hardware gets replaced. Sales history stays behind as an export. Gift card balances and loyalty points are rebuilt by hand. Plan four to six weeks.


The hardware trap

This is the single most expensive surprise in the whole move, and almost nobody is told about it before they sign somewhere else. A Clover device is locked to the processor that sold it. Clover is a Fiserv product sold through banks, independent sales organizations and payment processors, and the terminal you bought is bound to that relationship. Processors cannot reprogram a Clover the way they can reprogram a generic terminal. CardFellow put the question directly to First Data, Clover’s parent at the time, and got “security reasons” and no elaboration.

What that means in practice: the Station on your counter, the Mini by the register, the Flex your servers carry. None of them run Square. None of them can be made to. They are not resold, they are not traded in, and in a lot of contracts they go back to the processor or become e-waste. Owners routinely budget a migration as a software change and then discover a hardware line they had not counted on.

The one piece of good news is that Square hardware is cheap by comparison and not locked to anything, and a counter-service shop can often run the first weeks on an iPad it already owns while the permanent kit arrives. We will tell you which pieces you genuinely need and which ones are a want. That conversation happens before you commit, not after.

You own the Clover on your counter. You do not own what it is allowed to talk to.

What moves

The honest summary is that your catalog moves, your customers mostly move, and your history does not.

Clover’s item list and customer records come out as CSV, and Square takes a bulk item import with item name, variation, description, SKU, categories, pricing, modifier sets, inventory counts and tax settings. The mapping between the two is not automatic. Field names differ, Clover’s modifier groups do not land one-for-one in Square’s modifier sets, and Square’s own documentation notes that while nested modifier sets can be imported, the nesting relationships between them cannot be configured through the import. Somebody rebuilds that by hand. On a menu with real modifier depth that is the largest single block of work in the project.

The things that never come across as data, in any pair of systems, are the ones built inside the old software rather than stored in it: kitchen printer routing, floor plans and station assignments, combo and pricing rules, and the receipt and reporting setup. Those get documented off the old system while it is still running and rebuilt in the new one. If you switch off Clover before that is written down, you are rebuilding from memory.

Clover’s bulk export path for payment and order data is also narrower than people expect. Its export interface returns payments and orders in windows of at most 30 days per request, and the generated files are deleted after 24 hours. That is workable, but it is a job with a deadline on it, not a button you press on the last day.

Gift cards and loyalty

This is the part that ruins migrations, and it is the part every vendor page skips. Outstanding gift card balances are a liability on your books that does not move between systems. A customer holding a card from your old system will walk in six months from now and expect it to work, and there is no technical reason it will.

Square has no native way to hand gift card data to another platform. The workable route out is Reports, then Gift Cards, then Export, then Detail CSV, which gives you the card suffix and the outstanding balance. Going the other way, into Square, the official path is not self-service either: you contact Square with a CSV of previously issued cards and balances, they load it, and you then look cards up by manually entering the number. Their stated conditions are specific: strip the header row, drop zero-balance cards, amounts in cents with no decimal, card numbers numeric only and between 4 and 19 digits. Square also states plainly that non-Square gift cards cannot be activated or reloaded, and that not every card number format is guaranteed to be supported.

Read that last sentence again, because it is the whole issue. Old cards can often be honored. They usually cannot be reloaded. So the plan is always the same shape: freeze issuance on the old system a couple of weeks out, pull the closing balance report on the last night, load what will load, and keep the report as the fallback for the ones that will not. Then decide what you are doing about the physical cards in customers’ wallets, because they will keep arriving for a year.

Loyalty points are the same problem with a softer edge. Square has no self-service bulk export of customer reward balances; the account owner has to phone Square Support and have the data exported manually. Points are also a promise rather than money, which gives you an option a gift card does not: a lot of places use the switch as the moment to end an old scheme, write to the list, and open the new one with a launch offer that is worth slightly more than what people were sitting on. That costs less than the reconstruction and customers generally prefer it.

One warning we will repeat until it is boring. Do not let anybody tell you the gift cards will be fine. Get the balance report before you sign anything, look at the total, and make the decision with that number in front of you.

The contract

Clover is sold through resellers, which means there is no single Clover contract to check. Yours came from a bank or an ISO, and the terms sit in that agreement rather than on Clover’s website. Three-year terms are common and early termination fees are common with them. Separately, a lot of merchants have a non-cancelable equipment lease sitting alongside the processing agreement, and canceling one does not touch the other.

Before you do anything else, ask your provider in writing for the exact figure owed if the account closed on a named date, and the notice period required. A phone call to customer service is useful for learning the process but frequently does not satisfy the contract’s own notice requirement, which usually wants it in writing before a renewal date.

Then do the arithmetic honestly. If the exit fee is large and there are two months left on the term, the answer is to wait two months. We have told people that. It costs us the work and it is still the right answer.

Reasons to stay

Our manifesto starts with honest value. That means understanding what your current system can do before recommending a change.

The complaints that bring people to this page are, in rough order: the modifier screen is wrong and staff work around it, online ordering is going somewhere that takes a cut, the reporting does not answer the question you keep asking, and the effective processing rate is higher than the number you were quoted. Three of those four are configuration or contract problems and survive a migration untouched. A badly built menu rebuilt badly on Square is still a badly built menu, and now your staff have to relearn where everything is.

The one that genuinely justifies a move is the fourth, plus a specific capability the current system does not have. Price your effective rate first: total card fees divided by total card sales, over three months, from statements rather than a brochure. If that number is the problem, you may be able to fix it without touching the point of sale at all.

A POS health check is a remote review of your settings and workflows with a prioritized action list at the end. It is a fraction of the cost of a migration, and a fair number of them end with us saying the platform is fine and here are the six things to change. Both prices are on the pricing page and you can compare them before you speak to anybody.

How the weeks go

Four to six weeks is the realistic window for a single location, and most of that is not us waiting on Square. It is you deciding things, your old provider producing paperwork, and hardware arriving.

Week one is inventory and export: the item list, the customers, the modifier structure, the printer routing, the integrations, the gift card and loyalty balance reports, and a written copy of the settings that only exist inside Clover. Week two is mapping and build, where the exports become a Square configuration and the decisions that were never written down get made deliberately. Week three is validation: our team checks the build back against the source, and your team runs the test-order script from the quick-start guide on the new system while the old one is still the one that counts, so the things that were wrong become visible in a room instead of on a Saturday.

Then launch, early in the week. A cutover heading into a Friday night is how a good build gets a bad reputation, so we schedule around your slow days.

After that, the first week is when the odd modifier, the tax rule on one category and the printer sending drinks to the wrong station show up. Anything like that goes to the support team in your portal against the setup record, so it is fixed from what was configured rather than from memory.

Side by side

Scroll sideways on a phone.

Clover to Square: what survives the move
Feature WhatComes across?What it takes
Items, categories, prices Yes, by fileExport from Clover, map the fields, bulk import into Square
Modifier groups PartlyModifier sets import; the nesting relationships between them are rebuilt by hand
Customer names and contacts Yes, by fileCSV out, deduplicated on the way in
Stored customer cards SometimesCard data can only be transferred between PCI DSS Level 1 processors, by arrangement, and it takes weeks
Sales history NoExport it and keep the files. It stays a spreadsheet, not a report inside Square
Gift card balances NoClosing balance report, then a manual load. Old cards are honored, not reloaded
Loyalty points NoRebuilt from an export, or closed out and replaced with a launch offer
Hardware NoClover devices are locked to the processor that sold them and cannot be reprogrammed
Integrations Re-authorizedEvery third-party app reconnects from scratch and is tested before launch

What the migration includes

Stated in numbers, so nobody has to guess where it ends.

One fixed scope, in plain numbers, so you can tell whether your business fits inside it before you call. The price for it is on the pricing page.

01

Full Square configuration

One location. Up to 100 items, 20 modifier groups and 100 modifier choices, categories, taxes and service settings, up to 5 staff roles, up to 2 standard integrations, and online ordering.

02

Clean-source data mapping

Your exported item library, categories and customer records mapped field by field before anything is loaded. Clean source means the export is legible. If the item list is three years of duplicates and retired specials, cleaning it is a separate conversation and we will raise it before we start, not after.

03

Migration and validation

The mapped data goes in and is then checked back against the source: item counts, price spot-checks, tax rules by category, and modifier behavior on the twenty things you sell most.

04

Launch checklist and test-order script

A written checklist you keep afterward, and a test-order script your team runs on Square while Clover is still the system of record, so the wrong printer route shows up before it counts.

05

Launch review and portal support

Our team reviews the configuration against the checklist before it goes live, early in the week, never into a Friday night. Afterward, the support team in your portal works from the setup record.

06

Quick-start guides, walkthroughs and a setup record

A quick-start guide for each role and short video walkthroughs written for your setup, so your team learns the screens they will use. A setup record of everything configured lives in your portal, so somebody on your side can change a price without calling anyone.

Anything past these limits is quoted before it starts, never after. Every published price is on one page.

Be honest with me

Do not hire us for this migration if:

  • Your Clover agreement has a year to run, there is an early termination fee, and nothing is broken. Paying to escape a system that works is a poor trade and we will say so on the first call.
  • The thing annoying you is the modifier tree, the online ordering link or the reporting. Those are configuration problems. They will follow you to Square, and a health check costs a fraction of a migration.
  • You have a large outstanding gift card balance and no appetite for honoring cards by hand for a year. Balances do not move between systems. Somebody keys them in and somebody keeps the report.
  • You need to be live in nine days for a season opening. We will not take the validation out of a migration to hit a date, and a cutover without one is how a Saturday goes wrong.
  • You have never worked out your effective processing rate. Get that number from three months of statements first. It sometimes makes the whole decision for you, in either direction.

Questions we get

Can I keep my Clover hardware and just run Square on it?

No. Clover devices are locked to the merchant services provider that sold them and processors cannot reprogram them for a different account. This applies to the Station, Mini, Flex and Go. Budget for replacement hardware from the start. Square hardware is comparatively inexpensive and is not locked to a processor, and a counter-service shop can often start on an iPad it already owns.

What happens to gift cards my customers are already holding?

The balances do not transfer. You pull a closing balance report from Clover on the last night, load what Square will accept, and keep the report for anything that will not load. Square can accept a list of previously issued cards and balances through its support team, but non-Square cards cannot be reloaded afterward. Get the outstanding total before you decide anything.

Do I lose my sales history?

You lose it as a live report. You do not have to lose it as data. We export payments and orders from Clover before the account closes, in the windows its export allows, and hand you the files. Year-on-year comparisons in Square will start from your launch date. Anything earlier lives in a spreadsheet, which is worth knowing before your accountant asks in April.

How long does the whole thing take?

Four to six weeks for a single location is realistic. The build itself is not the long pole. Waiting on your current provider for contract terms, waiting on hardware, and getting the menu decisions made are what set the pace. If someone quotes you a weekend, ask them when the validation happens.

Will you tell me not to do it?

Regularly, and it costs us money every time. If the complaint is a modifier tree, an ordering link pointing at a marketplace, or reporting that never answered your question, those are configuration problems and they will follow you to Square. A health check finds them for a fraction of a migration. Both prices are on the pricing page.

How do you work with Square?

Yes. Shop & Table works with Square; we do not set up Clover, we move people off it. Our configuration fee is published. What matters more is having done this migration many times and knowing where it breaks.


Send us the Clover contract and the gift card report.

Those two documents answer most of the question before anybody commits to anything. We will read them, tell you what the switch would genuinely involve, and tell you if the answer is to stay put and fix the configuration instead.

Platform pricing and features change; where a platform does not publish a number we say so rather than guessing.

Shop & Table connects with supported commerce platforms. Clover and Square are trademarks of their respective owners.

Your preferences

Privacy choices

Choose which optional services can run on this website. Everything optional stays off until you choose. You can change your settings at any time.

Advertising tags are not configured on this website. These settings apply to this browser on this website; platform and ordering accounts have their own choices.

Make yourself comfortable

Accessibility

Choose what makes this page comfortable. Preferences stay on this device.

Navigate this page

Keyboard shortcuts

On a Mac, Alt is the Option key. Shortcuts do not run while you’re typing in a field, or with Control or Command held.

Alt + Shift + A
Open accessibility tools
Alt + Shift + S
Navigate by page structure
Alt + Shift + ?
Show keyboard shortcuts
Alt + Shift + T
Text size: next size
Alt + Shift + C
Contrast: next level
Alt + Shift + F
Focus outline on or off
Alt + Shift + L
Highlight links on or off
Alt + Shift + H
Highlight headings on or off
Alt + Shift + M
Stop animation on or off
Alt + Shift + G
Reading guide on or off
Alt + Shift + R
Reset everything

Policies & Choices

Open Page →