Campaigns in HighLevel (Legacy)

Updated: February 6, 2026  | 
Author: Bill Stilwell

This post covers what legacy Campaigns were, how they differ from both current Workflow Builder automations and current Email Campaign Automation, what they could contain, how to audit them in an older sub-account, and how to migrate them to Workflow Builder.

Reading time: about 5 minutes.

What Are Legacy Campaigns in HighLevel?

Legacy Campaigns in HighLevel were the action component of the original automation system. A Campaign was a pre-built sequence of messages – SMS, email, calls, and voicemail drops – arranged in order with configurable timing delays between each step.

The Campaign itself did not fire automatically. It sat dormant until a Trigger detected the appropriate event and activated the Campaign for the contact who triggered it.

The Trigger was the event detector; the Campaign was the action sequence. Together, Trigger plus Campaign was HighLevel’s first automated communication system.

This system predates Workflow Builder, which now handles everything Triggers and Campaigns could do – and much more – in a single integrated canvas.

Legacy Campaigns vs. Email Campaign Automation

The name “campaign” is used in two completely different contexts in HighLevel, which creates frequent confusion. Understanding the distinction is important when working with either current or legacy HighLevel setups.

Legacy Campaigns (the subject of this post) were automation sequences – drip sequences of messages fired automatically when a Trigger event occurred. They were a CRM automation tool, not a broadcast tool.

Each contact received the Campaign’s messages individually, triggered by their specific event.

Email Campaign Automation (the current system under Marketing) is a bulk email broadcast tool. It sends a designed email to a selected contact list – like a newsletter or promotional announcement.

It is not triggered by individual contact events; it is sent to a list on a scheduled date.

Both are called “campaigns” but they are fundamentally different: legacy Campaigns were individually triggered automations; current Email Campaigns are scheduled bulk broadcasts. Confusing the two is one of the most common points of confusion for people inheriting or auditing older HighLevel sub-accounts.

What a Legacy Campaign Could Contain

A legacy Campaign was built as a linear sequence of steps. Each step was one of: an SMS message, an email message, a call action (placing an outbound call to the contact), or a voicemail drop (delivering a pre-recorded voicemail to the contact’s voicemail).

Between each step was a Wait configuration – how long after the previous step the next step should fire. Wait periods could be set in minutes, hours, or days.

A typical lead follow-up Campaign might be: SMS immediately, email after 1 hour, SMS after 1 day, email after 3 days, call after 5 days, voicemail drop after 7 days.

The Campaign ran this sequence for each contact it was fired for – independently, based on when each contact entered the Campaign. A contact who entered on Monday started their sequence on Monday.

A contact who entered on Friday started their sequence on Friday. The timing was relative to each contact’s entry, not a fixed broadcast date.

The Limitations of Legacy Campaigns

Legacy Campaigns were useful for their time but limited compared to Workflow Builder. The most significant limitations: they could not add or remove tags, create tasks, update pipeline stages, move contacts between pipelines, branch conditionally based on contact behavior, check whether a reply had been received before sending the next step, or integrate with webhook actions.

A legacy Campaign ran its sequence in a straight line regardless of what the contact did. If a contact replied to the first SMS and made a purchase, the Campaign continued sending the remaining follow-up messages unless manually stopped.

Workflow Builder can branch based on reply status, purchase events, or any other trigger condition – stopping the sequence when it is no longer appropriate.

This straight-line limitation was a real operational problem for businesses using aggressive follow-up sequences. Contacts who had already converted still received sales follow-up messages, which created awkward communication and occasionally damaged relationships that had already become customers.

Are Legacy Campaigns Still Active?

Legacy Campaigns continue to function in older sub-accounts. If a sub-account has Triggers connected to Campaigns that were set up before Workflow Builder, those automations are still running.

Contacts who trigger the qualifying event still enter the Campaign sequence and receive the messages.

The legacy Campaign section may or may not be visible in the sub-account navigation depending on the HighLevel account configuration and age. Newer accounts provisioned after Workflow Builder became the standard may not have the legacy Campaigns section visible at all – only Workflow Builder is available for those accounts.

Auditing Legacy Campaigns in Older Sub-Accounts

When inheriting or taking over an older HighLevel sub-account, one of the first audit tasks is identifying whether legacy Campaigns are running and what they are doing.

Navigate to the Campaigns section (if visible). List all Campaigns.

For each Campaign, note its name, whether it is active, and what steps it contains. Then navigate to Triggers and identify which Triggers are connected to each Campaign.

This gives a complete picture of the legacy automation architecture.

Contacts who are currently in progress through a Campaign (have started the sequence but not completed all steps) may need to be handled carefully during migration – either allowing them to complete the sequence, or manually moving them to the new Workflow Builder equivalent.

Migrating to Workflow Builder

The migration process for a legacy Campaign is the same as migrating a legacy Trigger – because the two are always a pair. Rebuilding the Campaign alone in Workflow Builder without addressing the Trigger, or deactivating the Trigger without rebuilding the Campaign’s steps, produces an incomplete migration.

The complete migration rebuilds both the Trigger (as the Workflow trigger event) and the Campaign (as the Workflow action steps) in a single Workflow Builder workflow. After the workflow is tested and activated, the legacy Trigger is deactivated and the Campaign is effectively retired – no longer receiving new contacts.

During migration, the opportunity exists to improve what the legacy Campaign was doing. Replace the straight-line sequence with conditional branches.

Add tag actions when steps are completed. Create a task at the end of the sequence if no reply has been received.

The migration from legacy Campaign to Workflow Builder is always an upgrade opportunity, not just a replication exercise.

What Can You Do With It?

• Understand what legacy automations are running in an older sub-account: Identifying active Campaigns and their Triggers is the first step in auditing any inherited HighLevel account. Knowing what is running prevents accidentally disrupting active automations or leaving them running indefinitely without review.
• Migrate legacy Campaign automations to Workflow Builder for improved capability: Every migrated Campaign can be upgraded with branching, tag actions, and conditional logic that was not available in the original system.
• Eliminate the straight-line follow-up problem: The most common issue with legacy Campaigns – continuing to send follow-up messages to contacts who have already converted – is solved by adding a reply-received or purchase condition in the Workflow Builder equivalent.
• Ensure snapshot templates do not propagate legacy Campaign architecture: Snapshots created from older template sub-accounts may contain legacy Campaign automations. Updating those snapshots to use Workflow Builder automations ensures new client sub-accounts start on the current system.

Key Definitions

Who Is This For?

How to Migrate a Legacy Campaign

Step 1: Open the Campaign

Navigate to the Campaigns section and open the Campaign to be migrated. Document each step – message type, content, and timing delay.

Step 2: Find the associated Trigger

Go to Triggers. Identify which Trigger fires this Campaign.

Document the event and any filter conditions.

Step 3: Create the Workflow

In Workflow Builder, create a new workflow. Set the trigger to the equivalent event from the legacy Trigger.

Step 4: Add the Campaign steps as Workflow actions

Add each Campaign step as a Workflow action with the appropriate Wait before it. Copy the message content carefully, checking merge tag syntax.

Step 5: Add improvements

Add conditional branches for reply-received, add tag actions, create tasks at the end of the sequence. Upgrade while migrating.

Step 6: Test the Workflow

Test with a test contact. Verify each step fires at the right time with the right content.

Step 7: Activate the Workflow

Activate the new Workflow. It runs alongside the legacy pair temporarily.

Step 8: Deactivate the legacy Trigger

Deactivate the Trigger first. No new contacts enter the legacy Campaign.

The Campaign runs out for any contacts currently in progress.

Step 9: Retire the Campaign

Once no contacts remain active in the legacy Campaign sequence, it can be archived or left dormant. The automation is now fully in Workflow Builder.

How Does It Connect to HighLevel?

• Triggers (Legacy): Legacy Triggers are the companion feature. Campaigns and Triggers always worked as a pair – the Trigger detected the event, the Campaign delivered the sequence. Migrating one requires migrating the other.
• Workflow Builder: Workflow Builder is the direct replacement. All legacy Campaign functionality exists in Workflow Builder with additional capabilities. Every Campaign migration ends in Workflow Builder.
• Email Campaign Automation: Email Campaign Automation is the current bulk email tool that shares the “campaign” name. Understanding the distinction prevents confusing the two when working with accounts that have both systems present.
• SMS Marketing Automation: The SMS message steps in legacy Campaigns are now handled by SMS Marketing Automation within Workflow Builder. Migrated Campaigns replace their SMS steps with equivalent Workflow Builder SMS actions.
• Snapshot Manager: Older Snapshots may contain legacy Campaign automations. Updating snapshots to Workflow Builder automations is important for clean new client onboarding.

Common Questions

What are Campaigns in HighLevel (legacy)?

Pre-built linear message sequences – SMS, email, call, and voicemail steps with timing delays – fired by legacy Triggers when qualifying events occurred. The action component of the original HighLevel automation system.

How are legacy Campaigns different from Email Campaign Automation in HighLevel?

Legacy Campaigns were automation sequences fired by individual contact events. Email Campaign Automation is a bulk email broadcast tool sending to a list on a scheduled date.

Same name, completely different systems.

What could a legacy Campaign contain in HighLevel?

SMS message steps, email message steps, call actions, and voicemail drop steps – each with a timing delay from the previous step. No conditional branching, no tag actions, no pipeline updates.

Can I still use legacy Campaigns in HighLevel?

Existing ones continue to function in older accounts. New legacy Campaigns cannot be created in most current configurations.

All new automation should use Workflow Builder.

Where do I find legacy Campaigns in HighLevel?

In older sub-accounts, under a Campaigns section in the navigation – separate from the Marketing section. Not visible in newer accounts where only Workflow Builder is available.

How do I migrate a legacy Campaign to Workflow Builder in HighLevel?

Document each Campaign step. Identify the Trigger firing it.

Rebuild both as a single Workflow Builder workflow. Test, activate, deactivate the legacy Trigger.

To Wrap It Up

Legacy Campaigns represent HighLevel’s first generation of automation – functional for their time, but limited by the constraints of a simpler system. Understanding them is relevant for anyone working with older HighLevel accounts or trying to understand why an automation is firing without a corresponding Workflow Builder workflow to explain it.

The key distinction that saves the most confusion: legacy Campaigns (automation sequences) and current Email Campaign Automation (bulk broadcasts) are completely different systems. Encountering the Campaigns section in an older account and assuming it is the same as the Marketing email broadcasts is a common mistake that leads to misunderstanding what is actually running in the account.

For active legacy Campaigns, the migration path is clear and the migration adds value beyond just moving platforms. Every legacy Campaign that moves to Workflow Builder can be improved – conditional logic that stops the sequence when a contact replies, tag actions that update the contact’s status, task creation for human follow-up at the end of the sequence.

The migration is an upgrade in both system and capability.

1. Navigate to the Campaigns section in any legacy sub-account and list all active Campaigns
2. For each Campaign, document the full step sequence and timing
3. Find the Trigger connected to each Campaign
4. Rebuild as a Workflow Builder workflow – trigger plus action steps plus improvements
5. Test, activate, deactivate the legacy Trigger
6. Allow any contacts in progress in the old Campaign to complete or manually transition them
7. Update any snapshot templates that contain legacy Campaign automations

Pay particular attention to the straight-line problem when migrating. The most important improvement a legacy Campaign migration can add is the stop condition – a branch that exits the sequence when a contact replies, books an appointment, or becomes a customer.

Every legacy Campaign that was sending follow-up messages to contacts who had already converted is a problem the migration can fix. Add the condition; make the sequence smarter than the legacy version was.