What Moves With You and What You Rebuild After Boulevard

TL;DR: When you leave Boulevard, your client list and appointment history are exportable, and your service menu is too. Saved cards and memberships with active billing need separate handling, as do certain configuration details, so know what falls into each bucket before you pick a cancellation date.

That structure works fine at one location with a small team. Add a second location or a few more providers, and the bill climbs in ways that feel disconnected from actual revenue. If you've been running the math and it no longer adds up, you're probably already thinking about what a move involves.

Getting clear on those three before you do anything else saves you from discovering a gap two weeks after you've cancelled.

What Boulevard Actually Lets You Export

Boulevard's data export gives you a CSV of your client records. It includes names, contact info, service history, and notes. If your front desk has kept records consistently over time, that data will likely be in reasonable shape for an import with minimal cleanup required.

Your service menu and pricing are not in the export file, and neither is your staff list. They live in your account settings and you'll re-enter them. That's a few hours of work, not a crisis, but it matters for scheduling. Get your service menu documented (a spreadsheet is fine) before you start the new account setup so you're not re-creating it from memory.

Appointment history exports as a record. Future appointments booked past your cutover date will need to be entered manually if they aren't handled before you switch. If your new platform supports it, you can migrate them in bulk instead. Pull a report of everything booked beyond your planned go-live date and decide whether you're moving those over or contacting clients to rebook directly.

That is not a long runway. Boulevard's 30-day export window is worth understanding before you commit to a timeline. The clock starts the moment you cancel, not the moment you finish your import.

The Saved Card Problem

This is the part most operators don't think about until it's too late. Your clients' saved cards live with your payment processor, not with Boulevard. Those tokens don't travel automatically when you move platforms.

When you switch to Tersavia, we request the transfer of your clients' saved cards from your current payment processor. Whether the processor releases them is the processor's call, not ours. That means your first question before setting any timeline should be directed at whoever processes your payments: will you transfer saved card tokens to a new platform? Ask that before you pick a go-live date.

If the answer is yes, your card-on-file clients, memberships, and recurring billing can come with you. If the answer is no or not yet, you'll need a plan to re-capture cards at checkout over the weeks following the switch. That's not a reason to stay. It's a reason to plan. A card-on-file migration checklist is worth working through before you finalize any timeline.

What You Rebuild, and How Long It Takes

Some things don't export because they're configuration, not data. Expect to rebuild:

• Your service menu, with durations and processing times. Pricing is listed per provider level
• Staff schedules, including recurring availability and time-off rules
• Membership tiers: the terms and billing cycles, plus exactly what each tier includes
• Intake forms and any custom fields you've built
• Automated messages and reminder timing, along with your confirmation copy
• Online booking rules (deposit requirements, cancellation policies, booking windows)

None of that is complicated, but it takes time to do carefully. Plan for a full setup week before your go-live date, more if you have multiple locations or a staff of ten or more. The operators who run into trouble are the ones who try to cut over on a Friday afternoon and discover Sunday that their online booking page went live without deposit requirements.

The right sequence: build your new account completely, run it in parallel for a few days while you verify everything, then cancel Boulevard. Keep your Boulevard account open until your import is confirmed and your new setup is verified. Cancel after, not before.

Questions to Ask Before You Set a Date

Four questions worth answering before you commit to a timeline:

1. What payment processor does Boulevard run on for your account, and will they transfer saved card tokens?
2. How many future appointments are on the books past your planned cutover date, and how will you handle them?
3. Do you have active memberships with billing cycles mid-flight, and when do those cycles hit?
4. Who on your staff will own the data entry for the service menu and scheduling rebuild?

The membership question matters most if you have high membership volume. Active memberships with billing mid-cycle need careful timing so clients aren't double-billed or dropped during the transition. That's a manual reconciliation. Push your go-live date to land after a billing cycle, not during one.

For the operational specifics of what you're leaving behind, the Boulevard seat and location pricing structure is worth revisiting when you're preparing to make the case internally for switching. Knowing the exact number you're escaping makes the rebuild effort easier to justify.

Running the Full Transition

Once you've answered those four questions, the transition itself is a project with a checklist, not a leap. Tersavia imports from Boulevard, so your client records come over without manual re-entry. The switching overview at Tersavia lays out what the import covers and what the process looks like from the other side.

After the import is verified:

• Confirm client records match what you expected
• Run a test booking end to end, including payment
• Send a heads-up to clients about the new booking link before you publish it
• Brief your front desk on the new checkout flow before the first day live

The front desk piece is underrated. Even a clean migration feels disruptive if your staff is learning a new interface during a busy morning. A one-hour walkthrough the day before go-live is worth more than any amount of documentation.

Switching platforms is one of those decisions that feels larger than it is while you're inside it. The data moves without a hitch and the clients don't notice. The monthly bill drops, and the work is in the preparation, not the cutover.

FAQ

Can I export my full client list from Boulevard before I cancel?

Yes. Boulevard lets you export client records as a CSV while your account is active. The export includes contact details and service history; notes are included as well. Pull it before you cancel. The post-cancellation export window is 30 days, and working from an active account gives you more control over timing.

What happens to my active memberships when I leave Boulevard?

Membership billing is tied to your payment processor, not to Boulevard itself. When you switch, you'll rebuild your membership tiers in the new platform and need your processor to transfer saved cards so recurring billing can continue. Time your go-live date to land after a billing cycle, not during one, to avoid mid-cycle reconciliation issues.

Will my clients need to re-enter their card information after the switch?

That depends on your payment processor. When you move to Tersavia, we request the transfer of saved card tokens from your current processor. If the processor releases them, existing cards come with you. If not, you'll re-capture cards at the next checkout. Ask your processor directly before you set a go-live date.

How long does it take to rebuild the service menu and settings in a new platform?

For a single location with a team of six to ten providers, budget a full setup week. Larger operations or multi-location businesses should plan for two weeks. The client data imports require manual re-entry of the service menu, staff schedules, intake forms, and booking rules, so document everything in a spreadsheet before you start.