Switching restaurant POS loyalty system software is easier to survive in winter than in May, but only if you sequence it. A bad cutover costs you guest data, loyalty balances and a few ugly Friday nights. If you run a restaurant or bar in Medford, Burlington County or anywhere in South Jersey, the shore and patio rush is months away. That gap is your margin for error. This checklist covers what to export first, how to run old and new systems side by side, and which weeks to stay away from. It is general operations guidance, not advice about your specific contract.
The short version: export the guest list before you touch anything else.
Why winter is the window, and why the calendar still matters
January through mid-March is when most owners make this change. Covers are lower, staff have time to learn a screen, and a mistake gets fixed before the busy season. That logic holds. The trap is treating all of winter as safe.
Two stretches are not safe. The weeks from Thanksgiving through New Year's carry holiday parties, gift card sales and large reservations. Valentine's weekend packs dining rooms with short tables and low patience. Cutting over in either stretch means learning new software under peak load.
So you have two reasonable choices. Go live in the quiet days of November 2026, before Thanksgiving week. Or wait for the first quiet weeks of January 2027. We would not pick the weeks in between. As of today, October 5, 2026, mid-November is about six weeks away. That is enough to do the work below, but not enough to be casual about it.
Whatever date you choose, work backward from it. Treat the cutover day as the last item on the list, not the first. Everything in the next sections has to be finished before it.
This post is one piece of a larger question: who owns your guest list. We cover that in our guide to restaurant loyalty program software and guest data for South Jersey restaurants and bars. If your current vendor holds your list hostage, read that first.
What to export first, before you cancel anything
Export in order of how hard each item is to recreate. Menus can be retyped in a day. A guest's visit history cannot be rebuilt once the old account is closed. Most systems export to a CSV, a comma-separated values file you can open in Excel or Google Sheets. Ask your vendor in writing which data they can export and in what format. We do not know your vendor's limits, and neither can this article.
Tier one: guest and loyalty data
- Guest list: name, email, phone, birthday or anniversary if you collected them, and the date each person joined.
- Consent status: whether each guest agreed to email or text, when, and through which form. Keep this attached to every row.
- Visit and spend history: first visit, last visit, visit count and total spend per guest.
- Loyalty balances: current points, tier, and any unredeemed rewards. These are what you owe guests, so they need a signed-off snapshot.
- Gift card balances: card numbers and remaining value. Guests will notice a lost balance faster than any other mistake.
Tier two: operations data
- Item-level sales history: what sold, when, and at what price. You will want this for menu decisions and forecasting.
- Menu structure: items, modifiers (the add-ons and substitutions attached to a dish), prices by daypart, and tax settings.
- Staff data: roles, pay rates, tip pooling rules and clock-in history.
- Integrations list: every connected tool, such as online ordering, reservations, accounting and delivery. Each one needs a new connection on the new system.
Keep the cleaned list somewhere you control, such as the guest profiles in a custom restaurant CRM built around your reservations and events, not only inside a vendor's login. Do the first export now, then repeat it on cutover day. The first export tells you whether the data is usable. The second captures the last weeks of activity.
Open the file and look at it. Check that phone numbers are not cut off, that dates parse, and that duplicate guests are visible. A file that exports without errors can still be unusable. Catching this in October is cheap. Catching it in January, after the old contract ends, is not.
Keep your records, and ask your accountant what counts
A POS holds sales records that your bookkeeper and tax preparer may need later. Do not let your old account lapse before you have saved reports. The Internal Revenue Service says you must keep records that support income, deductions and credits until the period of limitations for that return expires. The general period for assessing tax is 3 years from filing, per the IRS Topic no. 305 page (accessed 2026).
Employment records run longer. The IRS guidance on how long to keep records says to keep employment tax records for at least 4 years after the tax is due or paid, whichever is later. Payroll and tip data often live in the POS.
We are not tax advisers. Ask your own accountant which reports to save, and in what form, before the old system goes dark. Also ask whether the mid-year switch affects how sales tax or payroll reports get split across two systems. That is a reason to avoid switching in the middle of a month or quarter if you can.
The sequence: a six-week plan
Here is the order we would run, counted back from your go-live date. Adjust it to your vendor's lead times. We cannot confirm how long hardware, card processing approval or data imports take for any specific vendor, so ask each one for a written timeline.
| When | What happens | Who owns it |
|---|---|---|
| 6 weeks out | First full export. Read your contract for notice periods and fees. Confirm the new system imports guests, consent flags, loyalty balances and gift cards. | Owner and manager |
| 5 weeks out | Clean the guest list: merge duplicates, fix formats, remove addresses that bounce. | Marketing or operations lead |
| 4 weeks out | Build the menu, modifiers, tax settings and printer routing in the new system. Connect integrations in test mode. | Manager |
| 3 weeks out | Train staff on a test terminal. Announce the change to loyalty members. | Manager |
| 2 weeks out | Start the parallel run (next section). Test a card payment, a refund, a voided item and a split check. | Whole team |
| Go-live week | Final export, balance reconciliation, cutover on your slowest weekday. | Owner and manager |
| 1 to 2 weeks after | Keep the old system readable. Reconcile daily sales against the old numbers. | Owner and bookkeeper |
The guest list cleaning step is the one owners skip. It is also the one that decides whether your first email to the new list lands or bounces.
How to run a parallel run without double-charging anyone
A parallel run means both systems are live for a short stretch, so the old one is your safety net. You do not have to run the whole restaurant twice. You choose what runs where.
A workable split looks like this:
- Payments and orders: one system takes real money at a time. Never process the same card in both.
- Shadow entry: for a few shifts, someone keys a sample of tickets into the new system, then you compare totals against the old one.
- Loyalty: freeze point earning in the old program at a stated time. Snapshot balances. Load the snapshot into the new program. Then turn earning on in the new one.
- Gift cards: keep honoring old cards at the old system until balances are confirmed in the new one.
The loyalty freeze is the step that goes wrong most often. If points earn in both programs, guests get double credit. If neither earns for a day, guests are annoyed. Pick a slow weekday morning, publish the time to staff, and write down the final balances.
Tell guests before it happens. A short message to your list, a note on the table and a sign at the host stand are enough. Say what changes, whether their points carry over, and who to ask. If you are not sure that every balance will carry over, say that too. A guest who hears about a gap from you stays; one who finds it at the register may not.
On consent: if your guests agreed to email or text through one vendor's form, the new platform needs that record. Rules about texting and email marketing are legal questions. Take them to your own lawyer before you send a first campaign from the new list.
Dates to avoid, and the day to pick
Avoid these windows for a cutover, in rough order of risk:
- Thanksgiving week and the weeks of December: holiday parties, gift card demand and large-group bookings stack up.
- New Year's Eve and the days around it: high volume, high prices, and staff you cannot spare for training.
- Valentine's weekend: many guests, short tables and low patience for a new ordering screen.
- Any week with a large private event, a local festival or a big televised game: check your own event calendar.
- The last days of a month or quarter: your bookkeeper will prefer a clean start to a reporting period. Confirm with them.
- Anything inside the four weeks before your spring and summer rush: if a problem appears late, you need time to fix it. Memorial Day weekend is not the day to find a printer routing error.
Pick your slowest weekday for the switch itself, early in the week, with the owner or manager on site. Open with a smaller menu on day one if you can. Keep the old system's login and its last export for at least a few weeks, in case a number looks wrong.
Write a rollback plan before you start. It is one page: who decides, what the trigger is (for example, card payments failing for 15 minutes during service), and how you go back. You may never use it. Having it means a bad Tuesday does not turn into a bad week.
When a new subscription is not the right fix
Sometimes the reason you are switching is that the loyalty tool, reservations, online ordering and POS each hold a different piece of your guest. Swapping one subscription for another leaves that problem in place. You change the vendor, and the data still lives in somebody else's account.
That is the case where a single guest record you own makes sense. We build that kind of system: a custom restaurant CRM connecting reservations, guest profiles, events, tasks and follow-up. It sits beside your POS rather than replacing it. We explain when replacing the register itself is worth it in our post on custom POS systems versus traditional ones. For most small restaurants, the register is the smaller question and the guest list is the bigger one.
Once the list is clean and in your hands, CRM-connected email automation can handle the welcome message, the birthday note and the win-back. A person on your team still approves the copy and the send list before anything goes out. We cannot promise what a campaign will earn, and we do not quote that in advance.
A one-page cutover checklist
- Choose a go-live window: November 2026 before Thanksgiving week, or early January 2027, not the weeks between.
- Export guests, consent flags, visit history, loyalty balances and gift cards. Open the files and check them.
- Ask your accountant which sales, payroll and tip reports to save before the old account closes.
- Clean and de-duplicate the guest list.
- Rebuild the menu, modifiers, tax settings and integrations in test mode.
- Train staff and tell loyalty members what is changing and when.
- Run both systems in parallel: one for real payments, one in shadow.
- Freeze loyalty earning, snapshot balances, load them, and restart earning in the new system.
- Cut over on your slowest weekday with a written rollback plan.
- Keep the old system readable for several weeks and reconcile daily.
Frequently Asked Questions
When is the best time to switch a restaurant POS?
Pick a slow stretch with a buffer before your busy season. For most South Jersey restaurants that means the quiet days before Thanksgiving week or the first weeks of January, away from holiday parties and Valentine's weekend. Cut over on your slowest weekday, and leave at least four weeks before spring volume returns so you can fix problems.
How do I move loyalty points when switching a restaurant POS loyalty system?
Freeze earning in the old program at a published time, export every guest's balance, and load that snapshot into the new program before earning restarts. Keep the file as your record. If the new system cannot import balances, tell members and credit them manually or with a reward. Ask both vendors what they support in writing.
How long should I keep old POS records after switching?
It depends on the record, so ask your accountant. As general background, the IRS says records supporting a return should be kept until the period of limitations expires, which is generally 3 years. Employment tax records must be kept at least 4 years. Save reports before the account closes.
Can I switch my POS without losing my guest list?
Usually yes, if you export before you cancel. Request a CSV of names, contact details, consent status, visit history and balances. Check the file for cut-off phone numbers and duplicates. If your current vendor will not export guest data, find that out now, because it affects whether you switch or build a guest record you own.
Plan the cutover before the holiday rush
If you want a second set of eyes on your export plan, or you want a guest record that survives the next vendor change, tell us what you run today. We will say plainly whether you need a new tool, a custom system, or just a cleaner list. If a CRM is the answer, it is part of our custom CRM development work, and you own what we build under the project agreement. Hosting and third-party subscriptions are scoped separately.
Sources
Every outside claim in this article links to where it came from. These open in a new tab.