Moving from Keap, ActiveCampaign, HubSpot or Mailchimp? Here's how to rebuild your automations as GoHighLevel workflows without losing a lead in the switch.
Updated
Moving to GoHighLevel from Keap, ActiveCampaign, HubSpot, Mailchimp, ClickFunnels or Kartra? Your contacts import from a CSV and your pages can be rebuilt, but your automations are the part that takes real work. No tool converts another platform's automations into GoHighLevel workflows: every platform stores triggers, conditions and actions in its own format. The good news is that most automations fall into a handful of patterns, and rebuilding them in GoHighLevel goes quickly once the groundwork is in place.
An ActiveCampaign automation, a Keap campaign and a HubSpot workflow all look like flowcharts, but under the hood each is tied to that platform's own lists, tags, deal stages, fields and email templates. GoHighLevel can import contacts (with their tags and custom field values) from a CSV, and it can import funnels from some platforms, but it has no importer for another tool's automations. Treat the migration as a rebuild from a written plan, not a file transfer.
Before you build anything, list every automation in the old platform with four things: what starts it, what it does, how many contacts are in it right now, and whether it still matters. Most accounts carry years of dead automations. Typically only a handful actually run the business: lead follow-up, appointment reminders, onboarding, review requests and a re-engagement sequence. Rebuild those first and archive the rest.
Screenshot or export each one you keep, including the full email and SMS copy and the wait times between steps. Once the old account is cancelled, that copy is the hardest thing to recover.
Workflows reference other things in the account, so create those before the workflows that use them:
The concepts carry over even when the names don't. Use this as a translation sheet:
| In your old platform | In a GoHighLevel workflow |
|---|---|
| Subscribes to a list / joins a sequence | Trigger: Contact Tag added, or Form Submitted |
| Deal or opportunity moves stage | Trigger: Pipeline Stage Changed / Opportunity Status Changed |
| Appointment booked or cancelled | Trigger: Appointment Status |
| Purchase or order placed | Trigger: Order Submitted or a payment trigger |
| Wait / delay / timer | Action: Wait (a set time, or until an event) |
| If / else, split, decision | Action: If/Else with conditions on tags, fields or replies |
| Send email / send SMS | Actions: Send Email, Send SMS |
| Apply or remove a tag | Actions: Add Contact Tag, Remove Contact Tag |
| Create or update a deal | Action: Create/Update Opportunity |
| Notify a team member | Action: Internal Notification or Assign to User |
| Call another tool (Zapier, webhook) | Action: Webhook, or a native integration |
| Start another automation | Action: Add to Workflow |
Two habits make the rebuild cleaner. Use one workflow per job rather than recreating a sprawling all-in-one automation. And add a stop condition (a goal, or a tag check) so a contact who books or buys drops out of the follow-up.
Most of the automations you'll rebuild, such as missed-call text back, appointment reminders, lead nurture, review requests and database reactivation, are standard patterns. Our free GoHighLevel workflow templates lay each one out step by step, with the email and SMS copy, so you can compare them against your old automation and adapt the wording instead of starting blank. A few good starting points: appointment reminders, database reactivation and the any-business set.
If you're an agency moving several clients onto GoHighLevel, you only need to rebuild each automation once. Build it in one sub-account, then copy it to the rest. GoHighLevel's own Copy Workflow handles sub-accounts in your agency if you're an agency admin. ExportGHL Workflows handles any account, including clients' own agencies, and rematches tags, pipelines, users and custom fields by name so the copy works in its new home. See copying a workflow to another account.
Moving automations between GoHighLevel accounts rather than into GoHighLevel? That's a different job, covered in GoHighLevel workflow migration between accounts.
Build a workflow in one account, then copy it into every client account with references rematched.
Start free