Leaving a Frankenstack without losing your customers (a checklist)
Moving off a stack of tools? A step-by-step checklist to export your data, protect open invoices, tell customers, and cancel safely, with no gaps.

Most people do not stay in a Frankenstack because they love it. They stay because leaving feels risky.
What if an open invoice disappears in the move? What if a customer’s recurring payment fails and nobody notices? What if the follow-up you promised on Thursday lives in a tool you just canceled?
Those fears are fair. A long-term GoHighLevel user in one r/gohighlevel thread said switching “becomes a giant pain in the ass” once your setup piles up (r/gohighlevel). Over on r/hubspot, one thread is titled “Struggling to Cancel HubSpot? $600+/Month” (r/hubspot). Lock-in is a real thing people write about.
The good news is that a safe move is mostly a matter of order. You protect the money, protect the customer relationships, run the old and new side by side for a short while, and only then cancel. This guide gives you that order as a checklist you can copy.
It works for any destination: a different all-in-one, a smaller stack, or Runza, where Ace, Runza’s AI co-founder who does the work, handles many of the small jobs a move creates. We will say more near the end. The checklist comes first, because it is useful either way.
The one idea behind every step
Your customers do not care which tools you use. They care that nothing breaks.
Nobody has ever thanked a business for a better CRM. They notice when an invoice link is dead, when a booking page 404s, when a reply goes to an inbox nobody reads, or when they get charged twice. So the whole plan is built around the places a customer can actually feel a change:
- Money (invoices, payment links, recurring charges)
- Messages (email sender, replies, texts, the list you promised to respect)
- Links (your website, booking page, forms, and anything printed or pinned)
- Promises (follow-ups, appointments, deadlines already in motion)
Everything else, like tags, internal notes, and pretty dashboards, is yours to rebuild at your own pace.
Should you leave at all? (a short honest check)
Leaving costs time. It is worth it only if the stack costs you more than the move will. Stay put, or at least wait, if:
- You are in the middle of a launch, a busy season, or a tax deadline. Pick a quieter two weeks.
- One tool is the problem, not the stack. Replacing one tool is a much smaller project than leaving the whole thing. Fix the weak link first.
- Your stack is lean and calm. Plenty of small DIY setups run well. If you are not losing hours to glue work, you may not need to move. Our piece on the learning-curve tax has a five-minute worksheet to find out.
- You are bound by an annual term you cannot exit yet. That does not stop you from preparing. Do Phases 1 and 2 now and set the cancel date for renewal.
If your Tuesdays are going to logins, glue, and fixing automations (see the Frankenstack), keep reading.
The seven phases at a glance
| Phase | What you do | Done when |
|---|---|---|
| 1. Inventory | List every tool, what it does, and who it touches | You have one page that covers every tool and every customer-facing touchpoint |
| 2. Back up | Export and save everything you might need | A dated folder exists with every export, and you opened each file once |
| 3. Protect the money | Settle open invoices and recurring payments | No customer is mid-payment on something that is about to move |
| 4. Build and test the new side | Set up the new home and send yourself test messages | Every customer-facing path works end to end, from a customer's point of view |
| 5. Tell people | Message customers, your list, and your team of one (you) | Anyone who needs to change a habit has been told, once, clearly |
| 6. Overlap, then cut over | Run old and new together briefly, then switch the live links | All live links point to the new home; the old tools are read-only |
| 7. Cancel and check | Cancel in the right order, then watch for strays | Cancellations are confirmed in writing and the 30-day watch list is clear |
Phase 1: Inventory (what exactly are you leaving?)
You cannot move what you have not listed. Most stacks hide a tool or two you forgot you were paying for, and a few connections nobody remembers building.
Step 1: List every tool. Check three places: your bank and card statements for the last year, the “Sign in with Google” list in your Google account security settings, and your browser’s saved logins. Write down every business tool you find, even the ones you barely use.
Step 2: For each tool, answer five questions.
| Question | Why it matters |
|---|---|
| What job does it do? | Tells you what the new home must do |
| What data lives only here? | These are the things you can lose |
| Which customers or leads touch it? | These are the things a customer can feel |
| What does it connect to (Zapier, webhooks, embeds)? | Hidden dependencies are where “nothing broke yesterday” turns into “everything broke today” |
| When does it renew, and can you cancel online? | Sets your cancel date |
Step 3: Mark each tool Keep, Move, or Drop. Dropped tools may still hold data worth saving, so Phase 2 applies to those too.
Here is what a filled-in inventory can look like. Example data only, not a benchmark or a real customer.
| Tool (example) | Job | Data that lives only here | Customer-facing touchpoint | Renews | Decision |
|---|---|---|---|---|---|
| Funnel builder | Landing page and checkout | Page copy, form submissions | Website link on business card, checkout link in emails | Annual, month of March | Move |
| Email service | Newsletter and sequences | Subscriber list, unsubscribe history | “From” address on every email | Monthly | Move |
| Scheduling tool | Booking | Appointment history | Booking link on website and in email signature | Monthly | Move |
| CRM board | Leads and notes | Deal notes, last-contact dates | None directly | Monthly | Move |
| Invoicing app | Invoices and recurring billing | Invoice history, saved client details | Pay links in sent invoices | Monthly | Move, carefully (Phase 3) |
| Zapier | Glue between the above | The Zaps themselves | Indirect: forms and notifications run through it | Monthly | Drop after cutover |
Step 4: Write the “customer map.” One list, with a line for every place a customer can touch your business: website, booking page, payment links, invoice emails, newsletter sign-up form, support email, phone or text number, social profile links, email signature, printed material, QR codes. Next to each, note which tool powers it today. This list is your cutover to-do list later.
Step 5: Find the glue. In Zapier or Make (or whatever you use), list each automation in plain words: “when X happens, do Y.” These are rules you will rebuild or retire. If one is the only thing that sends a customer a receipt or reminder, mark it as a customer-facing automation and treat it like a live link.
Phase 2: Back up (export before you do anything else)
Do this first, even if you are not sure you are leaving. A saved copy is cheap insurance.
Make a dated folder on a drive you control, named something like tool-exit-backup-YYYY-MM-DD. Inside, one subfolder per tool.
What to export, by type. Not every tool offers every export, and the menus change, so look in each tool’s settings or help center for “export,” “download,” or “backup.” Where a tool has no export, take screenshots or copy to a spreadsheet by hand.
| Data | Why you want it | Format to look for |
|---|---|---|
| Contacts and customers (names, emails, phones, tags, source) | The core relationship record | CSV spreadsheet |
| Notes, call logs, deal history | The memory of each relationship | CSV, or a copy-paste into a document if there is no export |
| Invoice and payment history | Your own records and your accountant's | CSV and PDF copies of each invoice |
| Quotes, proposals, contracts and signed documents | Proof of what you agreed | |
| Email list, plus unsubscribes, bounces, and complaints | You must honor opt-outs in the new tool | CSV (look for a separate “unsubscribed” or “suppressed” list) |
| Email templates and sequence text | Saves you rewriting | Copy into a document |
| Website pages, blog posts, images | The content you already wrote | Page text copied into documents, images downloaded, plus screenshots of each page |
| Forms and their fields | So the new form asks the same questions | Screenshot |
| Booking types, durations, availability rules | So the new calendar matches | Screenshot |
| Automation list from Phase 1 | The rules you will rebuild | Your plain-English list plus screenshots |
| Domain and DNS records | The records that make email and your site work | A screenshot or text copy of every record (see Phase 4) |
| Analytics and ad pixel IDs | So tracking continues | Copy the IDs into a note |
Open every file once. An export that is empty or garbled is worse than none, because you find out too late. Check that the row counts look right, that special characters survived, and that the list of subscribers is not missing the unsubscribes.
Think about sensitive data. A contact export is personal information about other people. Store the backup somewhere private and delete it when your accountant and you no longer need it. If your customers are in places with privacy rules (for example the EU or UK), check what you are allowed to keep and for how long. We are not lawyers, so ask a professional if you are unsure.
Keep invoice and payment records. How long you have to keep business records depends on where you live and what you do. Ask your accountant, and keep the export until they say otherwise.
One thing exports usually cannot do: copy saved payment methods. A customer’s stored card details are generally held by the payment processor, not by the tool you are leaving, and they usually cannot be handed over as a spreadsheet. Moving them typically involves the processor itself, or asking customers to enter payment details again. Phase 3 covers how to plan around this.
Phase 3: Protect the money
Money problems are the ones customers feel immediately, so handle them before anything else changes.
Step 1: Finish what is in flight. Where you can, let open invoices be paid in the tool that sent them. Do not delete or “migrate” an invoice that a customer is about to pay. A dead pay link is the single most avoidable way to lose goodwill during a move.
Step 2: List every recurring charge. Memberships, retainers, payment plans, subscriptions. For each: who pays, how much, how often, when is the next charge, and where does the money go now? Write it in a simple table.
Step 3: Choose a plan for each recurring customer. There are usually three options:
- Let it run to the end. If a plan has three payments left, finish them where they started, and start new customers in the new home.
- Start fresh at a natural boundary. For monthly retainers, begin the new arrangement on the first of the next month. Tell the customer ahead of time (Phase 5).
- Move with the processor’s help. If you are moving stored payment details between systems, talk to your payment processor’s support about what is possible before you cancel anything. Do not cancel the old billing tool first.
Step 4: Never leave a customer double-billed or unbilled. Set the old recurring charge to end and the new one to start on a specific, written date. Put both dates on your calendar. Check the first charge on the new side the day it runs.
Step 5: Understand your new fee picture before you commit. Every tool takes its cut somewhere, and a move changes where. List the per-payment fees you pay today (processor fees, the invoicing tool’s fee, any marketplace or platform fee) so you can compare honestly with the new setup. For Runza, here is the plain version: if you end up using Stripe for payment processing, there's a minimal processing fee on payments through your Runza checkout, on every plan including Free. It does not apply to sales tax or tips. The payment processor’s own fee comes out of each sale too, and Runza returns its fee when you refund a payment. Every cost is on the pricing page. Look for the same breakdown from any tool you are comparing.
Step 6: Tell your accountant or bookkeeper. A tool change moves where your invoices, receipts, and sales reports live. A two-line heads-up now saves a confusing tax season later.
Phase 4: Build and test the new side (before any customer sees it)
Build the new home while the old one keeps running. Move in this order, because it follows the risk: money paths first, then messages, then content.
1. Payments and invoicing. Set up how you get paid. Send yourself a small test payment, then refund it. Check what the customer sees, what you see, and where the receipt goes.
2. Customers. Bring over your contact list. A clean CSV with one column per field (name, email, phone, notes, source) is the most portable format there is, so clean it up before you import: remove duplicates, fix obvious typos, and make sure the unsubscribe list from Phase 2 travels with it. On Runza, you can add customers by hand, and Ace can read a spreadsheet of contacts you upload through the chat.
3. Email and sending identity. This is where quiet damage happens, so go slowly.
- If your emails come from your own domain, the records that prove you are allowed to send (SPF, DKIM, and DMARC, set in your domain’s DNS settings) are tied to your old email tool. Do not delete those records until the new tool is set up and sending. Add the new tool’s records alongside the old ones.
- Send test emails to a few addresses at different providers and check that they land in the inbox, not spam.
- If you change your sending address or service, expect a short period where more messages land in spam. Send to your most engaged people first, and keep volume modest for a couple of weeks. Do not blast your whole list on day one.
- Make sure unsubscribes work, and that people who opted out before stay opted out.
4. Scheduling. Rebuild each appointment type with the same name, length, buffer, and availability. Book a test appointment end to end, including the reminder and the calendar invite.
5. Website and forms. Rebuild or move the pages that customers actually visit, starting with the ones in your customer map. On Runza, Ace builds and updates your website from plain-English instructions, and you approve the result. Check every form: submit a test entry and confirm it reaches you, and confirm the person who submitted it gets whatever confirmation you promised.
6. Customer-facing automations. Rebuild the receipts, reminders, and follow-ups from your Phase 1 list. Test each one by being the customer.
7. Domain and links. If you use your own domain, do not change where it points yet. You will do that during cutover, with a plan for redirects (Phase 6).
8. Do a “customer walk-through.” Pretend to be a brand new customer: land on the site, book, pay, get the receipt, join the list, reply to an email. Then pretend to be an existing customer with an old link in an old email. Write down anything that fails.
Phase 5: Tell people (briefly, once, and before it matters)
A change that people hear about first from you is a small thing. A change they discover alone feels like a problem. You do not need a big announcement. You need a short, calm note to the right people at the right time.
Who to tell, and when:
| Who | What changes for them | When to tell them |
|---|---|---|
| Customers with recurring payments | New pay link or new billing date | At least a week before the first change |
| Customers with open invoices | Possibly a new pay link | Only if the pay link will change, and before it does |
| Newsletter subscribers | Possibly a new sender name or address | A short note a few days before, asking them to add the new address to their contacts |
| Booked clients | Possibly a new booking link or reminder format | Only if they have to do something |
| Your accountant or bookkeeper | Where invoices and reports now live | Before cutover |
| Collaborators, partners, referrers | New contact links | After cutover, with the new links |
Three templates you can adapt. These are templates with placeholders, not quotes from anyone. Swap the brackets for your own details and keep your own voice.
For a customer with a recurring payment:
Subject: A small change to how you pay me
Hi [name], quick heads-up. I am moving how I send invoices and take payments. Your [monthly/weekly] payment of [amount] will keep running the same way until [date]. From [date], you will get your invoice from [new sender] with a new payment link. Nothing else changes about our work together. If you would rather not enter payment details again, or if anything looks off, reply to this email and I will sort it out with you directly. Thanks, [your name]
For your email list, before a sender change:
Subject: New sender address for my emails
Hi [name], from [date] my emails will come from [new address]. If you want to keep seeing them in your inbox, please add that address to your contacts. Nothing else changes. If you would rather not hear from me, there is an unsubscribe link at the bottom of every email. Thanks for reading, [your name]
For an open invoice with a link that will change:
Subject: Updated link for invoice [number]
Hi [name], I am updating my invoicing. The link in my earlier email for invoice [number] will stop working on [date], so here is the new one: [link]. The amount and due date have not changed. Please reply if the link gives you any trouble. Thanks, [your name]
Two small rules: do not over-explain your tools (customers do not need to know about your stack), and do not promise a date you cannot keep. If cutover slips, send one short update and move on.
Phase 6: Overlap, then cut over
Overlap is the safety net. For a short, defined window, both homes work. Nobody falls through a gap because you flipped a switch on a Friday afternoon.
How long? Long enough to catch the monthly things (a billing cycle, a newsletter send, a recurring appointment), short enough that you are not paying for two stacks forever. Decide the window before you start and write the end date in your calendar. Where you can, schedule cutover for a quiet day, not a Friday.
The overlap week, step by step:
- Re-export the data that changed since Phase 2 (new leads, new notes, new invoices), and bring those into the new side.
- Freeze the old side. From a chosen date, new work happens only in the new home. Stop adding customers, notes, and invoices to the old tools.
- Switch the live links one at a time, in this order: payment links, booking link, forms, email signature, website domain. After each switch, test it.
- Redirect old links. Where a tool lets you, forward its old pages or links to the new ones. If you are moving a website, set up redirects from old addresses to new ones so old links still work. If you cannot redirect, leave the old page up with a short note and a link until the traffic dies down.
- Update every place your links live. Work through your customer map from Phase 1: social bios, email signatures, directory listings, printed material, QR codes. Printed material is the one you cannot fix after the fact, so check that a redirect covers it.
- Check for strays. Search your email for the old tool’s name for the last month. Anything it still sends is something you forgot.
- Turn off the old side’s customer-facing automations, so customers do not get two copies of a reminder.
Phase 7: Cancel (in the right order) and watch for strays
Canceling is where many moves go wrong, because it is easy to do too early and hard to undo.
Before you cancel any tool:
- Phase 2 backup is complete and was re-exported after the freeze
- Nothing customer-facing still depends on it
- You know its renewal date, notice period, and cancellation method (some require a form or an email rather than a button)
- Any annual term has run out, or you have decided a paid-up balance is worth losing
Cancel in this order:
- Automation glue (Zapier, Make), after the things it connected are gone.
- Tools with no customer-facing role (internal CRM boards, note apps).
- Scheduling, forms, and landing page tools, once redirects are live.
- Email service, after the new sender has run for a couple of cycles and you have confirmed unsubscribes carried over.
- Invoicing and payment tools last, after the last open invoice is paid and the last recurring charge has run its course.
Cancel carefully:
- Take a screenshot or save the confirmation email. Keep it. If you are billed again, this is your proof.
- If the tool lets you downgrade to a free or read-only tier instead of deleting your account, consider keeping that for a few weeks as a safety copy.
- Put a calendar reminder 30 days out to check your card statement for stray charges.
- Do not delete accounts and data right away. Many tools remove data permanently on deletion. Wait until the 30-day watch is clear.
- For subscriptions paid through an app store or a third party, cancel there, not in the tool.
The 30-day watch list:
- No unexpected charges from canceled tools
- No customer messages about broken links or missed emails
- Email sends are landing, not bouncing
- A test payment, test booking, and test form still work
- Your accountant has the invoice history they need
- The old data export is stored privately, and you have decided how long to keep it
The copy-and-paste checklist (one page)
Paste this into your notes app and tick as you go.
Phase 1: Inventory
- Listed every tool from card statements, Google account sign-ins, and saved logins
- For each tool: job, data that lives only here, customer touchpoint, connections, renewal date
- Marked each tool Keep, Move, or Drop
- Wrote the customer map (every place a customer touches the business)
- Listed every automation in plain words and flagged the customer-facing ones
Phase 2: Back up
- Made a dated, private backup folder
- Exported contacts, notes, invoices, signed documents, email list, and unsubscribes
- Copied templates, page text, images, forms, booking settings, and DNS records
- Opened every file once to check it
- Asked my accountant how long to keep records
Phase 3: Protect the money
- Decided what happens to every open invoice
- Listed every recurring charge, with a plan and date for each
- Confirmed with the payment processor what can move, before canceling any billing tool
- Compared fees fairly, including processor fees and any per-payment platform fee
- Told my accountant or bookkeeper
Phase 4: Build and test
- Payments: test payment and test refund done
- Customers imported, deduplicated, with opt-outs carried over
- Email: new records added next to old ones, test sends checked, unsubscribe tested
- Scheduling rebuilt and tested end to end
- Website pages and forms rebuilt and tested
- Customer-facing automations rebuilt and tested
- Did a walk-through as a new customer and as an old one
Phase 5: Tell people
- Told recurring-payment customers at least a week ahead
- Warned people with open invoices whose link will change
- Told my list about any new sender address
- Updated my accountant and any partners
Phase 6: Cut over
- Chose a quiet day and an overlap end date
- Re-exported data that changed since Phase 2
- Froze the old side
- Switched live links one at a time and tested each
- Set up redirects and updated every item on the customer map
- Searched my email for stray messages from old tools
- Switched off old customer-facing automations
Phase 7: Cancel and check
- Confirmed backups and renewals before each cancellation
- Canceled in order: glue, internal tools, front-end tools, email, billing last
- Saved every cancellation confirmation
- Set a 30-day reminder to check statements
- Held off deleting accounts until the watch list was clear
What a safe move can look like (example data)
A plan should have dates. Here is a three-week outline for a one-person business with five tools. Example data only. Your timing will differ, and nothing here is a benchmark or a real customer story.
| Week | What happens |
|---|---|
| Week 1 | Inventory, customer map, full backup, accountant heads-up. Nothing customer-facing changes. |
| Week 2 | Build and test the new side. Send the heads-up emails to recurring customers and the list. New customers start in the new home. |
| Week 3 | Re-export, freeze the old side, switch live links one at a time, set redirects. Old tools stay on as read-only. |
| Weeks 4 to 7 | Cancel in order as each tool's last duty ends. Check statements at the 30-day mark. |
Some people move much faster. On r/agency, one person wrote that “the day after onboarding I cancelled Hubspot, ClickFunnels, SamCart, Mailchimp and a couple others” (r/agency). That works if your setup is simple. If customers pay you or hear from you through any of those tools, the overlap above is cheap insurance.
Where Ace fits
A move like this is mostly a lot of small jobs, and small jobs are what Ace, Runza’s AI co-founder who does the work, is for. Ace builds and updates your website, keeps track of your customers and follow-ups, sends quotes and invoices, and plans and drafts your marketing. You tell Ace what you are trying to do in plain English, and you approve what goes out. You stay the owner.
In a move, that can look like: telling Ace which pages from your old site matter most and having it rebuild them for your approval, drafting the “new pay link” and “new sender address” notes above in your voice, and keeping the follow-ups on track while the move happens, so a promise made on a Thursday does not fall into the gap between two tools.
We will be straight about the limits. Moving still takes some days and some decisions that only you can make: who needs to hear what, and when you cut over. Ace does not guess your recurring-payment arrangements or decide your cancel dates. Whether a particular old tool lets you export a particular thing depends on that tool.
And whichever way you go, run this same checklist on us. Before you sign up for any tool, Runza included, ask three questions: is there a monthly plan, can I cancel online myself, and can I export my customers, invoices, and content? Those questions apply to us too. Here is our answer on the last two: on Runza, you can export your data and cancel with one click each.
If you are weighing options, these will help:
- Compare Runza with other tools, including GoHighLevel, HubSpot, HoneyBook, and Systeme.io
- See pricing, including how payment fees work
- See how Runza works for freelancers, coaches, consultants, and local service businesses
- Not sure a bigger tool is the answer? Read Agency tools vs one-person companies
Ready to start? Tell Ace what you are moving, and begin with the inventory.
FAQ
How do I leave a Frankenstack without losing customers?
Do it in order: list every tool and every place a customer touches your business, back up your data, protect open invoices and recurring payments, build and test the new setup before customers see it, tell the people who need to do something differently, run old and new side by side briefly, and cancel old tools last. The seven phases above cover each step.
How long does it take to switch business software?
It depends on how many tools you use, how much data they hold, and how much of it faces customers. We do not have a reliable average, so we will not quote one. Plan the phases in a calendar with real dates, and give yourself room for overlap. The example timeline above is example data, not a benchmark.
What should I back up before I cancel a tool?
Contacts and customer notes, invoice and payment history, signed documents, your email list with unsubscribes and bounces, templates and sequence text, website content and images, form and booking settings, your automation list, and your domain's DNS records. Open each file once to check it. Ask your accountant how long to keep financial records.
Can I move my customers' saved payment methods?
Usually not as a file you export yourself. Stored payment details are generally held by the payment processor, and moving them typically means involving the processor or asking customers to re-enter payment details. Talk to your processor before canceling any billing tool, and let recurring plans finish where they started if you can.
Will my emails land in spam after I switch email tools?
They can, for a while, especially if you change your sending address or service. Add the new tool's sending records alongside the old ones rather than replacing them, send test emails first, send to your most engaged people before the whole list, and keep volume modest for a couple of weeks. Make sure people who unsubscribed stay unsubscribed.
Do I have to tell my customers I am changing tools?
Only the ones who need to do something differently, such as use a new pay link, add a new email address, or expect a new billing date. Keep it short and calm. Customers do not need to know your stack.
Should I cancel the old tools right away?
Not until the new side is tested, live links have moved, and nothing customer-facing depends on the old one. Cancel in order, keep confirmations, wait for the 30-day watch list to clear before deleting data, and check your card statement a month later.
Does Runza charge fees on payments?
Yes. If you end up using Stripe for payment processing, there's a minimal processing fee on payments through your Runza checkout, on every plan including Free. It does not apply to sales tax or tips. Stripe's own processing fee comes out of each sale too, and Runza returns its fee on refunds. See the pricing page.
Is it ever better not to switch?
Yes. If only one tool is the problem, if your stack is calm and lean, or if you are in a busy season, wait or fix the weak link. Switching is worth it when the stack costs you more than the move will.
Can I use this checklist if I am moving somewhere other than Runza?
Yes. Nothing in it is specific to any product. It works for a move to another all-in-one, a smaller stack, or a different CRM.
The bottom line
You do not have to choose between staying stuck and risking your customers. A safe move is a short project with a clear order: inventory, backup, money first, test, tell, overlap, cancel.
If the thing in your way is “I do not have the hours to do this,” that is the kind of work Ace is for. Tell Ace what you are moving.