Super Migrator copied your assets across. A few things still need your own logins, your DNS, or a manual sweep before you flip the new account live. Work top-to-bottom — most teams finish in under an hour.
Folders for workflows and funnels do transfer — Super Migrator recreates the folder tree and drops each item back into its folder on the destination. Media library, forms, and surveys are the current exceptions (GHL doesn't expose folder APIs for those yet) — every item migrates, just at the root level. If you want the old organization back for those three, it's a quick drag-and-drop in the destination UI.
Quick spot-checks so you can trust the data before flipping any switches.
Confirm their notes and conversation history are sitting on the new contact record. The fastest way to feel confident the bulk import landed cleanly.
Check that any "add tag", "update custom field", or sub-workflow action is pointing at the right destination tag / field / workflow. If a tag was renamed during migration, the action will look fine but quietly do nothing.
End-to-end — submit a test, watch the workflow fire. Form / survey IDs change across accounts, so trigger references sometimes need to be re-pointed at the new form (next section).
Workflow and funnel folders should have come across with their items inside — if a couple landed loose at the root, drag them into the right folder. Media library, form and survey folders don't migrate yet (GHL limitation) — those items are at root and just need to be re-organized if you want the old layout.
These integrations live behind your logins or your DNS — Super Migrator can't carry the credentials. Each one is a short, self-serve task with a GHL guide.
Your sending and landing domains are tied to DNS records that only you control. Disconnect the domain from your old sub-account first, then add and verify it on the new one.
→ GHL guide: Dedicated email sending domains — overview & setup
Once the domain's added, finish the LC Email sending setup so your marketing emails go out from the new account's verified address. Same article as above covers both pieces.
Re-link your personal Google or Outlook calendar to each calendar in the new sub-account, and reconfigure any linked / conflict calendars so booking still respects your real availability.
→ GHL guide: Setting up linked calendars & conflict calendars
Stripe holds the OAuth connection between your Stripe account and the GHL sub-account. In the new account, go to Payments → Integrations and reconnect Stripe (and PayPal / NMI / Authorize.net if you use them). Existing products migrated; the payment processor link did not.
→ GHL guide: Getting started — Connect Stripe
Phone numbers can't be moved via the API — GHL Support has to do it. Submit a request to GHL (usually ~5 min on your side, then they handle the rest).
→ GHL guide: Moving phone numbers (Case 3: LC → LC, sub-accounts in different agencies)
Forms, surveys and calendars all migrated as assets. The references to them inside your funnel and website pages still point at the old account's IDs, so each page needs a quick re-pointing.
Open each funnel page that has a form, edit the form element, and pick the corresponding form in the new account. Tip — fixing the form on one page in a funnel often cascades to the rest.
Same pattern as forms — open the survey element, pick the new account's survey.
Edit each calendar widget on funnels / websites and select the new account's calendar. Test a booking once you're done so you know the slot picker, time zone, and confirmation email all fire.
Anywhere a funnel collects payment, confirm the product picker is sourcing from the new account's catalog and that Stripe is connected (Section 2). Run a $1 test purchase end-to-end before going live.
Last sweep before the new account starts taking real traffic.
Super Migrator preserves the source state, but double-check before live traffic hits. Anything that should be on — turn it on. Anything you migrated for reference but don't want firing — leave off.
For workflows that email or notify your team, confirm the user references resolved correctly. Super Migrator remaps team members by email address — if anyone's email differs in the new account, that step will be blank and needs re-picking.
Workflows that have contacts mid-sequence (e.g. a 7-day nurture) need to either finish on the source side or be manually re-enrolled on the destination. Cancel the source workflows only after their in-flight runs complete — otherwise contacts get dropped mid-journey.
Templates moved across, but the sending identity is account-specific — quick test before any blast.
Confirm the From address is the new sub-account's verified sender (from Section 2's domain setup), and that any merge tags like {{contact.lead_source}} still resolve correctly.
If you had scheduled campaigns in the source, decide whether you want them to keep sending there or to recreate the schedule in the destination. Don't have both firing at once.
You're ready. Last few items are about everything outside GHL that pointed at the old sub-account.
Zapier zaps, Make scenarios, third-party CRMs, website embed codes, payment webhooks, any custom API integrations — re-point them at the new sub-account's IDs / webhooks / API keys.
New login URL, new sub-account name, anything they need to know about renamed assets or moved folders. A 5-minute Loom save you a week of "where did X go?" Slack messages.
Either flip a hard cutover at a specific date / time, or run both accounts side by side for a few days while you watch for anything that broke. Side-by-side is safer if you have time; hard cutover is cleaner if you don't.
Once you're confident traffic, leads and bookings are all landing in the new account, you can disable workflows, pause campaigns, and eventually cancel the old sub-account. Keep it accessible for 30 days minimum — handy if something turns out to need re-checking.
Reply to your migration-complete email — we'll triage and help you unblock. We've walked dozens of agencies through the same checklist; nothing here is unusual.