Moving your agency onto a new CRM is rarely hard because of the software. It is hard because the system you run today lives in a dozen places at once: offers in a pricing doc, personas in someone's head, links scattered across old automations, and a follow-up sequence that only one person remembers writing. This guide is about getting all of that out of your head and into one file, so the move to Inflowave is fast, complete and boring in the best way.
It covers the two ways a migration starts, the request form, exactly what goes into a migration file, a ready-made prompt that lets Claude interview you and write the file for you, and what happens after you send it.
If you want the offer itself, what we do for you and on what terms, that lives on We will migrate your agency CRM for you and Migrate to Inflowave from any platform. This page is the practical how.
Step 1: Send the migration request form
Every migration starts with the Migrate to Inflowave form. It asks what we need to plan the move properly:
- Where you are moving from (GoHighLevel, HubSpot, ManyChat or another platform) and what you would like to bring over.
- How many client accounts you have and which of them to move first.
- What to move: contacts and tags, custom fields, pipelines and deals, calendars, workflows, forms, websites and funnels, email and SMS templates, and whether you want your setup only or your history as well.
- Phone numbers and texting: which numbers you want to keep and where they live today, plus the business details US carriers need to register you for texting.
- WhatsApp, email and domains: the number you use, how you send email today and the domains your sites and booking pages run on.
- Whether you want a short call to plan the move, or would rather we email you the plan.
You get an email back confirming the request and explaining what to send next. Filling it in does not commit you to anything, and you do not need to cancel your current platform. The safest way to move is to run one client on Inflowave alongside your existing setup, compare the two while both are live, and only then move the rest.
Step 2: Pick your path
There are two ways we get your setup across, and which one you take depends on whether we can log in to the platform you use today.
Moving from GoHighLevel
You do not need to write anything. Invite support@inflowave.io as a user in your GoHighLevel account (Settings, then My Staff, then Add Employee), and we copy your setup across from there: contacts, pipelines, custom fields, tags, forms and automations rebuilt to match what you have now. If you run several GoHighLevel agency accounts, invite us in each one.
Moving from anything else
ManyChat, Systeme.io, Kit, Kajabi, a Calendly-only setup, a spreadsheet and a lot of goodwill: if we cannot log in to it, you send us one plain text file that describes your system, plus your exports. That file is called migration.md, and the rest of this guide is about writing it well.
What actually moves (and what might not)
What moves depends on what your current platform lets out, and we tell you plainly on the first call which is which, rather than after you have committed.
- Contacts, pipelines and custom fields generally move cleanly from an export.
- Tags move, and we keep what each one means so your automations still make sense.
- Automations are rebuilt to match, step by step, from your description or from the platform itself.
- Conversation history depends on the platform. Some do not export it in a usable form, and where that is true we say so.
- Phone numbers and texting registration depend on where your numbers live. If they are in your own Twilio account, nothing changes and the switch takes minutes. If they belong to your current platform, the registration has to be done again with us, and we start that before anything moves so you keep texting from your old platform while it is in review. Numbers move across last, after everything else has been tested.
Step 3: Write your migration file
Name the file migration.md. It is plain text with headings, and you can write it the way you would explain your business to a new assistant. Leave out any section that does not apply.
You can download the blank template, which has every heading below ready to fill in.
1. Your business
Business name, your name, email, phone, website, time zone, and every social account we should connect.
2. Who you sell to
Each type of customer you have: who they are, what they struggle with, what they want, how soon, and what they can spend. If you have real customer quotes, paste them in. This becomes your personas inside Inflowave, which your AI agent, ads and content all lean on, so it is worth ten honest minutes.
3. What you sell
Every product and service: name, price, how it is paid (one-off, monthly or a payment plan), what is included, the checkout link, and whether it is live or retired. These become your offers.
4. Your links
Every link your messages send people to: sales pages, checkouts, booking pages, sign-up forms, lead magnet downloads and replays. One per line, with what it is for. We keep them in one place, so changing a link later changes it everywhere it is used instead of hunting through forty automations.
5. Tags and fields
The tags you use and what each one means, plus any custom fields you store on contacts, such as a lead score or a source.
6. Your pipeline
The stages a lead moves through, in order, and what moves them from one stage to the next.
7. Your automations
One block per automation, in this shape:
- Starts when: what triggers it (a keyword DM, a new follower, a purchase, a form, a tag, a booking)
- Then: each step in order, with waits ("wait 2 days") and conditions ("only if they did not book")
- Messages: the exact text of each DM, SMS or email, or the name of the file that has them
- Stops when: what ends it (they bought, they replied, a tag was added)
This is the section people rush, and it is the one that matters most. An automation described as "follow up with leads" cannot be rebuilt. One described with its trigger, its waits and its exit can be rebuilt exactly.
8. Your email sequences
Either paste every email (subject, preview text and body) or attach them as separate files named after the sequence, for example workshop-sequence.md.
9. Your pages
Links to the sales pages and funnels you want rebuilt here, and anything that must change on the way.
10. Your rules
How your messages must sound: words you always or never use, your sign-off, and anything you never claim. Your AI agent follows these too.
11. Anything else
Team members who need a login (name, email and role), tools you want connected, deadlines, and anything we should not move.
Let Claude interview you and write the file
Most agency owners know their system perfectly and still find it slow to write down. The fastest way we have found is to let an AI assistant do the asking. Open a new chat with Claude (or any assistant you like), paste the prompt below, and answer its questions. It works through your business one section at a time, pulls the facts out of anything you paste in, such as a sales page, an old email or a pricing sheet, and finishes by writing your migration.md in exactly the format above.
You are helping me prepare a migration file so Inflowave can rebuild my business
system in their CRM. Interview me one section at a time, in this order: my business;
who I sell to (personas); what I sell (offers, prices, how they are paid, checkout
links); my lead magnets and every link my messages send people to; my tags and custom
fields; my pipeline stages; my automations; my email sequences; my pages and funnels;
the rules for how my messages must sound; and anything else (team logins, tools,
deadlines, what not to move).
Rules for you:
- Ask a few questions at a time, wait for my answers, and ask follow-ups when an
answer is vague (for example a price without how it is paid, or an automation
without what starts it).
- If I paste an export, a sales page or an old email, pull the facts out of it
yourself instead of asking me to retype them.
- Never invent anything. If I do not know something, write "Not sure yet" there.
- When we are done, output ONE Markdown document with these headings in this order:
1. Your business, 2. Who you sell to, 3. What you sell, 4. Your links,
5. Tags and fields, 6. Your pipeline, 7. Your automations, 8. Your email sequences,
9. Your pages, 10. Your rules, 11. Anything else.
Write every automation as Starts when / Then / Messages / Stops when.
A few tips that make the result better:
- Paste, do not retype. Drop in your pricing page, your best-performing DM script and a couple of your sequence emails. The assistant extracts the details faster and more accurately than you can type them.
- Describe one real lead's journey. "Someone comments PRICE on a reel, gets a DM, books a call, and if they do not book we follow up twice" is worth more than a list of tool names.
- Say "Not sure yet" freely. A gap we can see is easy to fill on a call. A guess written as a fact gets rebuilt wrong.
- Read the finished file once. Correct anything that is off before you send it; it is your system, in your words.
The same file is useful well beyond the migration. It is the clearest written record most agencies will ever have of their offers, personas and follow-up, and it is a good thing to hand any new team member.
Step 4: Send it with your exports
Email migration.md to support@inflowave.io from the address you used on the form, and attach your exports in the same email:
- Contacts: a CSV export of your contacts (in ManyChat, for example: Contacts, select all, Export).
- Email sequences: the files from your email tool, if they are not pasted into the file.
- Anything the file mentions: lead magnet PDFs, images and documents.
What happens after you send it
- We read your file and exports. Anything unclear becomes a question in the migration panel at the top of your Inflowave account, so you answer it in one place instead of a long email thread.
- We build everything switched off. Personas, offers, links, tags, fields, pipeline, automations and sequences are set up in your account, but nothing reaches your contacts until you are happy.
- The panel shows progress. You see what is done, what we are still working on and what we need from you.
- You approve the switch. When you are ready, we turn everything on together and you approve the migration in the panel.
You keep your current platform running the whole time, so there is no window where leads fall through.
Ready to start
Send the migration request, then download the template or paste the prompt above into Claude while you wait for our reply. If you would rather talk it through first, book a call and we will tell you on that call exactly what moves cleanly from your current platform.
