MoveOver migration report: Bright Path Agency

Steps1

Mapped0

Approximated2

Left as a note0

Added by MoveOver0

To configure2

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
slack_message "Send notification to Slack"	a Slack step that needs the Slack integration connected in Votel	Connect Slack under Settings > Integrations, then pick the channel on the step.
trigger inbound_webhook "Inbound Webhook"	a Votel webhook trigger; Votel gives it a NEW URL when the workflow is switched on	In Votel, switch the workflow on, open its trigger and copy the new webhook URL; update the system that posts to HighLevel's URL (HighLevel trigger id unknown) to post to Votel's instead.
2 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

1. BrightPath Rebooted - 5 Emails campaign - [v2 templates Ready]

Steps16

Mapped11

Approximated5

Left as a note0

Added by MoveOver0

To configure0

What MoveOver changed

Nothing: every step translated exactly and nothing is left to configure.

Map (as in HighLevel; nothing added)

1. Pitch Deck Entry Emails - Sequence 1 [DRAFT]

Steps14

Mapped8

Approximated6

Left as a note0

Added by MoveOver0

To configure2

Hand-offsenrolls 2. Starter Plan's Ecosystem [v2 NEW TEMPS]

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
2 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

2. Pitch Deck Ecosystem [DRAFT]

Steps19

Mapped10

Approximated9

Left as a note0

Added by MoveOver0

To configure12

Hand-offsenrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHED

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
12 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

Academy Waitlist

Steps9

Mapped4

Approximated5

Left as a note0

Added by MoveOver0

To configure4

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
4 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

BACKUP - Bright Path Tools - Purchase made on site - Before Migration Routing Fix - 2026-08-31

Steps8

Mapped7

Approximated6

Left as a note0

Added by MoveOver0

To configure0

Hand-offsenrolls 2. Starter Plan's Ecosystem [v2 NEW TEMPS]enrolls 2. Starter Plan's Ecosystem [v2 NEW TEMPS]enrolls 2. Pro Plan's Ecosystem [v2 NEW TEMPS]enrolls 2. Bookkeeping's Ecosystem [v2 NEW TEMPS]enrolls 2. Snapshot Pack's Ecosystem [v2 NEW TEMPS]enrolls 2. Funnel Kit's Ecosystem [INTRO TO ALL OTHER APPS BUT Funnel Kit] - v2 NEW TEMPS

What MoveOver changed, and why

Feeder workflow "Tag Purchased sm on site" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Tag Purchased sl on site" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Tag Purchased sf on site" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Tag Purchased ss on site" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Tag Purchased sc on site" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.

Map (as in HighLevel; nothing added)

BACKUP - Bright Path Tools Inbound FREE - Before Migrator Fix - 2026-08-31

Steps16

Mapped7

Approximated9

Left as a note0

Added by MoveOver0

To configure14

Hand-offsenrolls 1. Bookkeeping Entry Emails - Sequence 1 - [v2 NEW TEMPS]]enrolls TO REMOVE - OLD Audit Service WEBHOOK - MIGRATE 10 CONTACTS FIRSTenrolls 1. Pro Plan Entry Emails - Sequence 1 - [v2 NEW TEMPS]enrolls 1. Starter Plan Entry Emails - Sequence 1 [v2 NEW TEMPS]enrolls 1. Snapshot Pack Entry Emails - Sequence 1 - [v2 NEW TEMPS]enrolls (01) Coaching Program Entry Emails - Sequence 1 - [v2 NEW TEMPS]enrolls (01) Audit Service Entry Emails - Sequence 1 - v2 NEW TEMPS

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
if_else "yes"	a condition that never matches (branch on the inbound webhook payload (source))	Rebuild the condition in Votel on a field that exists there, or remove the branch.
trigger inbound_webhook "Inbound Webhook"	a Votel webhook trigger; Votel gives it a NEW URL when the workflow is switched on	In Votel, switch the workflow on, open its trigger and copy the new webhook URL; update the system that posts to HighLevel's URL (HighLevel trigger id unknown) to post to Votel's instead.
14 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

Backup - Event Launch Pre-launch Emails Sequence (Non-buyers)

Steps23

Mapped12

Approximated11

Left as a note0

Added by MoveOver0

To configure0

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
event_start_date "Set Event Start Date from Contact Field"	the date set on the following wait	Check the following wait carries the right date.
wait "Wait 14 Day Before Event"	GoHighLevel wait type "appointment" replaced by a 1-day wait	Set the wait to what you need (Votel has no "wait until the appointment").
wait "Wait 13 Day Before Event"	GoHighLevel wait type "appointment" replaced by a 1-day wait	Set the wait to what you need (Votel has no "wait until the appointment").
wait "Wait 12 Day Before Event"	GoHighLevel wait type "appointment" replaced by a 1-day wait	Set the wait to what you need (Votel has no "wait until the appointment").
wait "Wait 11 Day Before Event"	GoHighLevel wait type "appointment" replaced by a 1-day wait	Set the wait to what you need (Votel has no "wait until the appointment").
wait "Wait 10 Day Before Event"	GoHighLevel wait type "appointment" replaced by a 1-day wait	Set the wait to what you need (Votel has no "wait until the appointment").
wait "Wait 9 Day Before Event"	GoHighLevel wait type "appointment" replaced by a 1-day wait	Set the wait to what you need (Votel has no "wait until the appointment").
wait "Wait 8 Day Before Event"	GoHighLevel wait type "appointment" replaced by a 1-day wait	Set the wait to what you need (Votel has no "wait until the appointment").
wait "Wait 7 Day Before Event"	GoHighLevel wait type "appointment" replaced by a 1-day wait	Set the wait to what you need (Votel has no "wait until the appointment").
wait "Wait 3 Day Before Event"	GoHighLevel wait type "appointment" replaced by a 1-day wait	Set the wait to what you need (Votel has no "wait until the appointment").
wait "Wait 1 Day Before Event"	GoHighLevel wait type "appointment" replaced by a 1-day wait	Set the wait to what you need (Votel has no "wait until the appointment").

Map (as in HighLevel; nothing added)

BACKUP - Migration Purchase During Intro - Before Routing Fix - 2026-08-31

Steps5

Mapped3

Approximated3

Left as a note0

Added by MoveOver0

To configure0

Hand-offsremoves from TO REMOVE - OLD Audit Service WEBHOOK - MIGRATE 10 CONTACTS FIRSTenrolls 2. Migration Service's Ecosystem [v2 NEW TEMPS]

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
if_else "yes"	a condition that never matches (branch on which trigger fired (no Votel equivalent))	Votel runs one trigger per workflow, so "which trigger fired" cannot be asked: put the branch's steps in the feeder workflow for that trigger, or remove the branch.

Map (as in HighLevel; nothing added)

BACKUP 2026-09-01 - Bookkeeping Cross-Ecosystem Purchase Router

Steps17

Mapped6

Approximated12

Left as a note0

Added by MoveOver0

To configure0

Hand-offsremoves from 2. Funnel Kit's Ecosystem [INTRO TO ALL OTHER APPS BUT Funnel Kit] - v2 NEW TEMPSenrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Pro Plan's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Snapshot Pack's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Starter Plan's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Migration Service's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from BACKUP 2026-09-01 - Bookkeeping Cross-Ecosystem Purchase Router

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
remove_from_workflow "REMOVE FROM THIS FLOW"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
if_else "yes"	a condition that never matches (branch on which trigger fired (no Votel equivalent))	Votel runs one trigger per workflow, so "which trigger fired" cannot be asked: put the branch's steps in the feeder workflow for that trigger, or remove the branch.

Map (as in HighLevel; nothing added)

BACKUP 2026-09-01 - Funnel Kit Cross-Ecosystem Purchase Router

Steps17

Mapped6

Approximated12

Left as a note0

Added by MoveOver0

To configure0

Hand-offsremoves from 2. Starter Plan's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Bookkeeping's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Pro Plan's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Snapshot Pack's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Migration Service's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from BACKUP 2026-09-01 - Funnel Kit Cross-Ecosystem Purchase Router

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
remove_from_workflow "REMOVE FROM THIS FLOW"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
if_else "yes"	a condition that never matches (branch on which trigger fired (no Votel equivalent))	Votel runs one trigger per workflow, so "which trigger fired" cannot be asked: put the branch's steps in the feeder workflow for that trigger, or remove the branch.

Map (as in HighLevel; nothing added)

BACKUP 2026-09-01 - Migration Service Cross-Ecosystem Purchase Router

Steps17

Mapped6

Approximated12

Left as a note0

Added by MoveOver0

To configure0

Hand-offsremoves from 2. Snapshot Pack's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Pro Plan's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Bookkeeping's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Funnel Kit's Ecosystem [INTRO TO ALL OTHER APPS BUT Funnel Kit] - v2 NEW TEMPSenrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Starter Plan's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from BACKUP 2026-09-01 - Migration Service Cross-Ecosystem Purchase Router

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
remove_from_workflow "REMOVE FROM THIS FLOW"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
if_else "yes"	a condition that never matches (branch on which trigger fired (no Votel equivalent))	Votel runs one trigger per workflow, so "which trigger fired" cannot be asked: put the branch's steps in the feeder workflow for that trigger, or remove the branch.

Map (as in HighLevel; nothing added)

BACKUP 2026-09-01 - Pro Plan Cross-Ecosystem Purchase Router

Steps17

Mapped6

Approximated12

Left as a note0

Added by MoveOver0

To configure0

Hand-offsremoves from 2. Funnel Kit's Ecosystem [INTRO TO ALL OTHER APPS BUT Funnel Kit] - v2 NEW TEMPSenrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Bookkeeping's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Starter Plan's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Snapshot Pack's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Migration Service's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from BACKUP 2026-09-01 - Pro Plan Cross-Ecosystem Purchase Router

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
remove_from_workflow "REMOVE FROM THIS FLOW"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
if_else "yes"	a condition that never matches (branch on which trigger fired (no Votel equivalent))	Votel runs one trigger per workflow, so "which trigger fired" cannot be asked: put the branch's steps in the feeder workflow for that trigger, or remove the branch.

Map (as in HighLevel; nothing added)

BACKUP 2026-09-01 - Snapshot Pack Cross-Ecosystem Purchase Router

Steps17

Mapped6

Approximated12

Left as a note0

Added by MoveOver0

To configure0

Hand-offsremoves from 2. Funnel Kit's Ecosystem [INTRO TO ALL OTHER APPS BUT Funnel Kit] - v2 NEW TEMPSenrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Bookkeeping's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Pro Plan's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Starter Plan's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Migration Service's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from BACKUP 2026-09-01 - Snapshot Pack Cross-Ecosystem Purchase Router

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
remove_from_workflow "REMOVE FROM THIS FLOW"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
if_else "yes"	a condition that never matches (branch on which trigger fired (no Votel equivalent))	Votel runs one trigger per workflow, so "which trigger fired" cannot be asked: put the branch's steps in the feeder workflow for that trigger, or remove the branch.

Map (as in HighLevel; nothing added)

BACKUP 2026-09-01 - Starter Plan Cross-Ecosystem Purchase Router

Steps17

Mapped6

Approximated12

Left as a note0

Added by MoveOver0

To configure0

Hand-offsremoves from 2. Snapshot Pack's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Pro Plan's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Bookkeeping's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Funnel Kit's Ecosystem [INTRO TO ALL OTHER APPS BUT Funnel Kit] - v2 NEW TEMPSenrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Migration Service's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from BACKUP 2026-09-01 - Starter Plan Cross-Ecosystem Purchase Router

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
remove_from_workflow "REMOVE FROM THIS FLOW"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
if_else "yes"	a condition that never matches (branch on which trigger fired (no Votel equivalent))	Votel runs one trigger per workflow, so "which trigger fired" cannot be asked: put the branch's steps in the feeder workflow for that trigger, or remove the branch.

Map (as in HighLevel; nothing added)

Black Friday Email Sequence

Steps5

Mapped3

Approximated2

Left as a note0

Added by MoveOver0

To configure2

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
2 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

Bounced

manual⚠ 1 step not translatedOpen in Votel ↗

Steps1

Mapped0

Approximated0

Left as a note1

Added by MoveOver0

To configure0

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
internal-delete-contact "Delete Contact"	a note on the contact at this point of the workflow ("MoveOver could not translate this GoHighLevel step"); the workflow continues past it	Delete the contact by hand when that point is reached, or leave it.

Map (as in HighLevel; nothing added)

BPA - Pitch

Steps1

Mapped0

Approximated1

Left as a note0

Added by MoveOver0

To configure1

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
1 item Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

Email Warmup Workflow

Steps5

Mapped3

Approximated2

Left as a note0

Added by MoveOver0

To configure2

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
2 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

Event Launch Pre-launch Emails Sequence (Non-buyers)

Steps1

Mapped1

Approximated0

Left as a note0

Added by MoveOver0

To configure0

What MoveOver changed

Nothing: every step translated exactly and nothing is left to configure.

Map (as in HighLevel; nothing added)

Flash Sale

Steps3

Mapped1

Approximated2

Left as a note0

Added by MoveOver0

To configure3

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
sms "SMS"	SMS template not found in the Message Templates export	Paste the SMS text on the step.
3 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

Funnel Kit AI - New Signup

Steps3

Mapped1

Approximated3

Left as a note0

Added by MoveOver0

To configure5

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
create_update_contact "Create Contact"	an update-contact step (fields skipped: name)	Check the fields on the step; the ones listed were skipped.
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
trigger inbound_webhook "Inbound Webhook"	a Votel webhook trigger; Votel gives it a NEW URL when the workflow is switched on	In Votel, switch the workflow on, open its trigger and copy the new webhook URL; update the system that posts to HighLevel's URL (HighLevel trigger id unknown) to post to Votel's instead.
5 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

Growth Intensive 2026 — Master Send Sequence

Steps103

Mapped57

Approximated47

Left as a note0

Added by MoveOver0

To configure3

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
3 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

Migration Service - Welcome

Steps2

Mapped1

Approximated2

Left as a note0

Added by MoveOver0

To configure2

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
trigger two_step_form_submission "Order Form Submission"	a Votel form trigger that fires on ANY form submission	Restrict the trigger to the right form in Votel, or the workflow starts on every form submission.
2 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

Partner Landing Page

Steps1

Mapped0

Approximated2

Left as a note0

Added by MoveOver0

To configure2

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
2 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

Partner Webhook

Steps4

Mapped2

Approximated2

Left as a note0

Added by MoveOver0

To configure3

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
if_else "yes"	a condition that never matches (branch on the inbound webhook payload (business_email))	Rebuild the condition in Votel on a field that exists there, or remove the branch.
trigger inbound_webhook "Inbound Webhook"	a Votel webhook trigger; Votel gives it a NEW URL when the workflow is switched on	In Votel, switch the workflow on, open its trigger and copy the new webhook URL; update the system that posts to HighLevel's URL (HighLevel trigger id unknown) to post to Votel's instead.
3 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

Replied to Growth Intensive 2026 — Master Send Sequence

sms_inboundOpen in Votel ↗

Steps2

Mapped2

Approximated1

Left as a note0

Added by MoveOver0

To configure4

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
slack_message "Send notification to Slack"	a Slack step that needs the Slack integration connected in Votel	Connect Slack under Settings > Integrations, then pick the channel on the step.
4 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

Saas website From Submitted Workflow

Steps2

Mapped1

Approximated2

Left as a note0

Added by MoveOver0

To configure3

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
3 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

Starter - New Lead: Purchase META

Steps2

Mapped1

Approximated2

Left as a note0

Added by MoveOver0

To configure3

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
facebook_conversion_api "Meta Conversion API"	a Facebook conversion step that needs the pixel connected in Votel	Connect the Facebook pixel under Settings > Integrations, then pick it on the step.
trigger two_step_form_submission "Order Form Submission"	a Votel form trigger that fires on ANY form submission	Restrict the trigger to the right form in Votel, or the workflow starts on every form submission.
3 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

Starter - New Lead:Registration

Steps2

Mapped1

Approximated2

Left as a note0

Added by MoveOver0

To configure3

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
facebook_conversion_api "Meta Conversion API"	a Facebook conversion step that needs the pixel connected in Votel	Connect the Facebook pixel under Settings > Integrations, then pick it on the step.
3 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

Task Overdue Escalation

scheduleOpen in Votel ↗

Steps4

Mapped2

Approximated3

Left as a note0

Added by MoveOver0

To configure5

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
internal_notification "Send Overdue SMS Reminder"	an internal notification with NO recipient	Pick the team member who should receive it.
if_else "Check if task is still incomplete"	a condition that never matches (branch on task state; branch on date/time)	Rebuild the condition in Votel on a field that exists there, or remove the branch.
trigger task_due_date_reminder "Task Due Date Passed"	a daily schedule	Set the schedule's time; it runs daily instead of on the reminder.
5 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

Templates - Funnels

Steps2

Mapped2

Approximated1

Left as a note0

Added by MoveOver0

To configure3

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
trigger inbound_webhook "Inbound Webhook"	a Votel webhook trigger; Votel gives it a NEW URL when the workflow is switched on	In Votel, switch the workflow on, open its trigger and copy the new webhook URL; update the system that posts to HighLevel's URL (HighLevel trigger id unknown) to post to Votel's instead.
3 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

Templates- Link Tree Style Funnel

Steps2

Mapped2

Approximated1

Left as a note0

Added by MoveOver0

To configure0

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
trigger form_submission "Form Submitted"	a Votel form trigger (form(s) 5hJDDXvU0mCkitRDfToF not found by name; fires on any form)	Pick the right form on the trigger in Votel.

Map (as in HighLevel; nothing added)

test 1

scheduleOpen in Votel ↗

Steps1

Mapped1

Approximated1

Left as a note0

Added by MoveOver0

To configure2

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
trigger birthday_reminder "Birthday Reminder"	a daily schedule	Set the schedule's time; it runs daily instead of on the reminder.
2 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

Test for Alex

Steps2

Mapped0

Approximated2

Left as a note0

Added by MoveOver0

To configure0

What MoveOver changed

Nothing: every step translated exactly and nothing is left to configure.

Map (as in HighLevel; nothing added)

Waitlist Funnel Kit AI

form⚠ 1 step not translatedOpen in Votel ↗

Steps3

Mapped1

Approximated2

Left as a note1

Added by MoveOver0

To configure2

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
math_operation "Math Operation"	a note on the contact at this point of the workflow ("MoveOver could not translate this GoHighLevel step"); the workflow continues past it	Rebuild the calculation with a "set and format variables" step.
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
2 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

Email Core

GHL migration: Email CoreOpen agent ↗19

Click Event

manual⚠ 1 step not translatedOpen in Votel ↗

Steps11

Mapped8

Approximated1

Left as a note1

Added by MoveOver0

To configure5

Hand-offsenrolls Open Event

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
add_to_workflow "Add to Workflow - Open Event"	child workflow "Open Event" resolved in a second pass	Check this step: child workflow "Open Event" resolved in a second pass.
trigger mailgun_email_event "Email Events - Click"	no trigger created; the workflow has no way to start from this event	Votel has no trigger for email opens, clicks, bounces or unsubscribes; decide whether this workflow is still needed.
5 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

Days Since Last Click - 14 Days

field_conditionOpen in Votel ↗

Steps9

Mapped4

Approximated6

Left as a note0

Added by MoveOver0

To configure4

Hand-offsremoves from Days Since Last Click - 30 Daysremoves from Days Since Last Click - 60 Daysremoves from Days Since Last Click - 90 Daysenrolls Days Since Last Open - 14 Daysenrolls Days Since Last Click - 30 Days

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
remove_from_workflow "Remove from Workflow - 30 Day Check"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "Remove from Workflow - 60 Day Check"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "Remove from Workflow - 90 Day Check"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
add_to_workflow "Add to Workflow - 14 Day Open"	child workflow "Days Since Last Open - 14 Days" resolved in a second pass	Check this step: child workflow "Days Since Last Open - 14 Days" resolved in a second pass.
add_to_workflow "Add to Workflow - 30 Day Check"	child workflow "Days Since Last Click - 30 Days" resolved in a second pass	Check this step: child workflow "Days Since Last Click - 30 Days" resolved in a second pass.
trigger contact_changed "Click Event Field Updated"	"changed" became "is not empty" on click_event	Check the condition: "changed" became "is not empty".
4 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

Days Since Last Click - 30 Days

manualModified for continuityOpen in Votel ↗

Steps8

Mapped4

Approximated1

Left as a note0

Added by MoveOver3

To configure4

Hand-offsenrolls Days Since Last Click - 60 Days

Action needed: what changed, and what to do

Resume router added in front of the workflow: 2 resume points (s0_wait_15_days_14_day_clicks, s3_wait_16_days_total_of_31). A contact placed by MoveOver waits until its HighLevel due time, then continues at that step; every other contact skips the router.

Was (HighLevel)	Now (Votel)	What to do
add_to_workflow "Add to Workflow - 60 Day Check"	child workflow "Days Since Last Click - 60 Days" resolved in a second pass	Check this step: child workflow "Days Since Last Click - 60 Days" resolved in a second pass.
4 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Maps: the HighLevel original (left) and as built in Votel, with the added block (right)

In HighLevel

In Votel router added

Days Since Last Click - 60 Days

manualModified for continuityOpen in Votel ↗

Steps6

Mapped3

Approximated1

Left as a note0

Added by MoveOver2

To configure3

Hand-offsenrolls Days Since Last Click - 90 Days

Action needed: what changed, and what to do

Resume router added in front of the workflow: 1 resume point (s2_wait_30_days_total_of_61). A contact placed by MoveOver waits until its HighLevel due time, then continues at that step; every other contact skips the router.

Was (HighLevel)	Now (Votel)	What to do
add_to_workflow "Add to Workflow - 90 Day Check"	child workflow "Days Since Last Click - 90 Days" resolved in a second pass	Check this step: child workflow "Days Since Last Click - 90 Days" resolved in a second pass.
3 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Maps: the HighLevel original (left) and as built in Votel, with the added block (right)

In HighLevel

In Votel router added

Days Since Last Click - 90 Days

manualModified for continuityOpen in Votel ↗

Steps6

Mapped4

Approximated0

Left as a note0

Added by MoveOver2

To configure1

Action needed: what changed, and what to do

Resume router added in front of the workflow: 1 resume point (s2_wait_30_days_total_of_91). A contact placed by MoveOver waits until its HighLevel due time, then continues at that step; every other contact skips the router.

Was (HighLevel)	Now (Votel)	What to do
1 item Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Maps: the HighLevel original (left) and as built in Votel, with the added block (right)

In HighLevel

In Votel router added

Days Since Last Open - 14 Days

field_conditionOpen in Votel ↗

Steps8

Mapped4

Approximated5

Left as a note0

Added by MoveOver0

To configure2

Hand-offsremoves from Days Since Last Open - 30 Daysremoves from Days Since Last Open - 60 Daysremoves from Days Since Last Open - 90 Daysenrolls Days Since Last Open - 30 Days

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
remove_from_workflow "Remove from Workflow - 30 Day Check"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "Remove from Workflow - 60 Day Check"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "Remove from Workflow - 90 Day Check"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
add_to_workflow "Add to Workflow - 30 Day Check"	child workflow "Days Since Last Open - 30 Days" resolved in a second pass	Check this step: child workflow "Days Since Last Open - 30 Days" resolved in a second pass.
trigger contact_changed "Open Event Field Updated"	"changed" became "is not empty" on open_event	Check the condition: "changed" became "is not empty".
2 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

Days Since Last Open - 30 Days

manualModified for continuityOpen in Votel ↗

Steps7

Mapped4

Approximated1

Left as a note0

Added by MoveOver2

To configure3

Hand-offsenrolls Days Since Last Open - 60 Days

Action needed: what changed, and what to do

Resume router added in front of the workflow: 1 resume point (s0_wait_15_days_14_day_opens). A contact placed by MoveOver waits until its HighLevel due time, then continues at that step; every other contact skips the router.

Was (HighLevel)	Now (Votel)	What to do
add_to_workflow "Add to Workflow - 60 Day Check"	child workflow "Days Since Last Open - 60 Days" resolved in a second pass	Check this step: child workflow "Days Since Last Open - 60 Days" resolved in a second pass.
3 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Maps: the HighLevel original (left) and as built in Votel, with the added block (right)

In HighLevel

In Votel router added

Days Since Last Open - 60 Days

manualModified for continuityOpen in Votel ↗

Steps6

Mapped3

Approximated1

Left as a note0

Added by MoveOver2

To configure3

Hand-offsenrolls Days Since Last Open - 90 Days

Action needed: what changed, and what to do

Resume router added in front of the workflow: 1 resume point (s2_wait_30_days_total_of_61). A contact placed by MoveOver waits until its HighLevel due time, then continues at that step; every other contact skips the router.

Was (HighLevel)	Now (Votel)	What to do
add_to_workflow "Add to Workflow - 90 Day Check"	child workflow "Days Since Last Open - 90 Days" resolved in a second pass	Check this step: child workflow "Days Since Last Open - 90 Days" resolved in a second pass.
3 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Maps: the HighLevel original (left) and as built in Votel, with the added block (right)

In HighLevel

In Votel router added

Days Since Last Open - 90 Days

manualModified for continuityOpen in Votel ↗

Steps7

Mapped5

Approximated0

Left as a note0

Added by MoveOver2

To configure1

Action needed: what changed, and what to do

Resume router added in front of the workflow: 1 resume point (s2_wait_30_days_total_of_91). A contact placed by MoveOver waits until its HighLevel due time, then continues at that step; every other contact skips the router.

Was (HighLevel)	Now (Votel)	What to do
1 item Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Maps: the HighLevel original (left) and as built in Votel, with the added block (right)

In HighLevel

In Votel router added

Days Since Last Reply - 14 Days

field_conditionOpen in Votel ↗

Steps9

Mapped4

Approximated6

Left as a note0

Added by MoveOver0

To configure2

Hand-offsremoves from Days Since Last Reply - 30 Daysremoves from Days Since Last Reply - 60 Daysremoves from Days Since Last Reply - 90 Daysenrolls Days Since Last Open - 14 Daysenrolls Days Since Last Reply - 30 Days

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
remove_from_workflow "Remove from Workflow - 30 Day Check"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "Remove from Workflow - 60 Day Check"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "Remove from Workflow - 90 Day Check"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
add_to_workflow "Add to Workflow - 30 Day Check"	child workflow "Days Since Last Reply - 30 Days" resolved in a second pass	Check this step: child workflow "Days Since Last Reply - 30 Days" resolved in a second pass.
trigger contact_changed "Reply Event Field Updated"	"changed" became "is not empty" on reply_event	Check the condition: "changed" became "is not empty".
2 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

Days Since Last Reply - 30 Days

manualModified for continuityOpen in Votel ↗

Steps8

Mapped4

Approximated1

Left as a note0

Added by MoveOver3

To configure4

Hand-offsenrolls Days Since Last Reply - 60 Days

Action needed: what changed, and what to do

Resume router added in front of the workflow: 2 resume points (s0_wait_15_days_14_day_replies, s3_wait_16_days_total_of_31). A contact placed by MoveOver waits until its HighLevel due time, then continues at that step; every other contact skips the router.

Was (HighLevel)	Now (Votel)	What to do
add_to_workflow "Add to Workflow - 60 Day Check"	child workflow "Days Since Last Reply - 60 Days" resolved in a second pass	Check this step: child workflow "Days Since Last Reply - 60 Days" resolved in a second pass.
4 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Maps: the HighLevel original (left) and as built in Votel, with the added block (right)

In HighLevel

In Votel router added

Days Since Last Reply - 60 Days

manualModified for continuityOpen in Votel ↗

Steps6

Mapped3

Approximated1

Left as a note0

Added by MoveOver2

To configure3

Hand-offsenrolls Days Since Last Reply - 90 Days

Action needed: what changed, and what to do

Resume router added in front of the workflow: 1 resume point (s2_wait_30_days_total_of_61). A contact placed by MoveOver waits until its HighLevel due time, then continues at that step; every other contact skips the router.

Was (HighLevel)	Now (Votel)	What to do
add_to_workflow "Add to Workflow - 90 Day Check"	child workflow "Days Since Last Reply - 90 Days" resolved in a second pass	Check this step: child workflow "Days Since Last Reply - 90 Days" resolved in a second pass.
3 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Maps: the HighLevel original (left) and as built in Votel, with the added block (right)

In HighLevel

In Votel router added

Days Since Last Reply - 90 Days

manualModified for continuityOpen in Votel ↗

Steps6

Mapped4

Approximated0

Left as a note0

Added by MoveOver2

To configure1

Action needed: what changed, and what to do

Resume router added in front of the workflow: 1 resume point (s2_wait_30_days_total_of_91). A contact placed by MoveOver waits until its HighLevel due time, then continues at that step; every other contact skips the router.

Was (HighLevel)	Now (Votel)	What to do
1 item Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Maps: the HighLevel original (left) and as built in Votel, with the added block (right)

In HighLevel

In Votel router added

Email Event: Bounced

manual⚠ 1 step not translatedOpen in Votel ↗

Steps2

Mapped2

Approximated0

Left as a note1

Added by MoveOver0

To configure1

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
trigger mailgun_email_event "Email Events - Bounced"	no trigger created; the workflow has no way to start from this event	Votel has no trigger for email opens, clicks, bounces or unsubscribes; decide whether this workflow is still needed.
1 item Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

Email Event: Complained/SPAM

manual⚠ 1 step not translatedOpen in Votel ↗

Steps2

Mapped2

Approximated0

Left as a note1

Added by MoveOver0

To configure1

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
trigger mailgun_email_event "Email Events - Complained/SPAM"	no trigger created; the workflow has no way to start from this event	Votel has no trigger for email opens, clicks, bounces or unsubscribes; decide whether this workflow is still needed.
1 item Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

Email Event: Unsubscribed

manual⚠ 1 step not translatedOpen in Votel ↗

Steps2

Mapped2

Approximated0

Left as a note1

Added by MoveOver0

To configure1

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
trigger mailgun_email_event "Email Events - Unsubscribed"	no trigger created; the workflow has no way to start from this event	Votel has no trigger for email opens, clicks, bounces or unsubscribes; decide whether this workflow is still needed.
1 item Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

For DND - Clear 14/30/60/90 Day Opens/Clicks/Replies

field_conditionOpen in Votel ↗

Steps1

Mapped1

Approximated1

Left as a note0

Added by MoveOver0

To configure0

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
trigger dnd_contact "Contact DND - Email"	a do-not-email field condition	Check this step: DND trigger approximated as do_not_email set.

Map (as in HighLevel; nothing added)

Open Event

manual⚠ 1 step not translatedOpen in Votel ↗

Steps7

Mapped6

Approximated0

Left as a note1

Added by MoveOver0

To configure3

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
trigger mailgun_email_event "Email Events - Open"	no trigger created; the workflow has no way to start from this event	Votel has no trigger for email opens, clicks, bounces or unsubscribes; decide whether this workflow is still needed.
3 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

Reply Event

email_inboundOpen in Votel ↗

Steps11

Mapped8

Approximated2

Left as a note0

Added by MoveOver0

To configure6

Hand-offsenrolls Open Event

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
trigger customer_reply "Customer Replied - Email"	an inbound-message trigger without a channel picked	Pick the channel to watch on the trigger.
6 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

Starter Plan

GHL migration: Starter PlanOpen agent ↗10

[Starter] - Cancel Subscription

Steps3

Mapped3

Approximated1

Left as a note0

Added by MoveOver0

To configure3

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
3 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

[Starter] - Free Credits

Steps39

Mapped38

Approximated9

Left as a note0

Added by MoveOver0

To configure47

Action needed: what changed, and what to do

Feeder workflow "[FREE] 10 Credit" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "[FREE] 3 Credit" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "[FREE] 20 Credit" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "[FREE] 2 Credit" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "[FREE] 25 Credit" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "[FREE] 4 Credit" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "[FREE] 5 Credit" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "[FREE] 1 Credit" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.

Was (HighLevel)	Now (Votel)	What to do
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
47 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

[Starter] - NEW Sign Up

Steps22

Mapped16

Approximated13

Left as a note0

Added by MoveOver0

To configure20

Action needed: what changed, and what to do

Feeder workflow "[PAID] 2 Credit" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Unlimited" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "[PAID] 50 Credits" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Starter" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Pro" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "[PAID] 20 Credits" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "[PAID] 10 Credits" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.

Was (HighLevel)	Now (Votel)	What to do
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
if_else "yes"	a condition that never matches (branch on which trigger fired (no Votel equivalent))	Votel runs one trigger per workflow, so "which trigger fired" cannot be asked: put the branch's steps in the feeder workflow for that trigger, or remove the branch.
trigger two_step_form_submission "Agency"	a Votel form trigger that fires on ANY form submission	Restrict the trigger to the right form in Votel, or the workflow starts on every form submission.
trigger two_step_form_submission "[PAID] 2 Credit"	a Votel form trigger that fires on ANY form submission	Restrict the trigger to the right form in Votel, or the workflow starts on every form submission.
trigger two_step_form_submission "Unlimited"	a Votel form trigger that fires on ANY form submission	Restrict the trigger to the right form in Votel, or the workflow starts on every form submission.
trigger two_step_form_submission "[PAID] 50 Credits"	a Votel form trigger that fires on ANY form submission	Restrict the trigger to the right form in Votel, or the workflow starts on every form submission.
trigger two_step_form_submission "Starter"	a Votel form trigger that fires on ANY form submission	Restrict the trigger to the right form in Votel, or the workflow starts on every form submission.
trigger two_step_form_submission "Pro"	a Votel form trigger that fires on ANY form submission	Restrict the trigger to the right form in Votel, or the workflow starts on every form submission.
trigger two_step_form_submission "[PAID] 20 Credits"	a Votel form trigger that fires on ANY form submission	Restrict the trigger to the right form in Votel, or the workflow starts on every form submission.
trigger two_step_form_submission "[PAID] 10 Credits"	a Votel form trigger that fires on ANY form submission	Restrict the trigger to the right form in Votel, or the workflow starts on every form submission.
20 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

[Starter] - New Sign Up - Main

Steps28

Mapped21

Approximated11

Left as a note0

Added by MoveOver0

To configure25

Action needed: what changed, and what to do

Feeder workflow "20 Credits" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "100 Credits" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "50 Credits" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "10 Credits" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.

Was (HighLevel)	Now (Votel)	What to do
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
if_else "yes"	a condition that never matches (branch on which trigger fired (no Votel equivalent))	Votel runs one trigger per workflow, so "which trigger fired" cannot be asked: put the branch's steps in the feeder workflow for that trigger, or remove the branch.
trigger two_step_form_submission "2 Credit"	a Votel form trigger that fires on ANY form submission	Restrict the trigger to the right form in Votel, or the workflow starts on every form submission.
trigger two_step_form_submission "20 Credits"	a Votel form trigger that fires on ANY form submission	Restrict the trigger to the right form in Votel, or the workflow starts on every form submission.
trigger two_step_form_submission "100 Credits"	a Votel form trigger that fires on ANY form submission	Restrict the trigger to the right form in Votel, or the workflow starts on every form submission.
trigger two_step_form_submission "50 Credits"	a Votel form trigger that fires on ANY form submission	Restrict the trigger to the right form in Votel, or the workflow starts on every form submission.
trigger two_step_form_submission "10 Credits"	a Votel form trigger that fires on ANY form submission	Restrict the trigger to the right form in Votel, or the workflow starts on every form submission.
25 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

[Starter] - Reinstate Subscription

Steps4

Mapped4

Approximated1

Left as a note0

Added by MoveOver0

To configure3

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
3 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

[Starter] - Sign Up - [May 26]

Steps33

Mapped25

Approximated13

Left as a note0

Added by MoveOver0

To configure30

Action needed: what changed, and what to do

Feeder workflow "12 Credits" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "30 Credits" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "60 Credits" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "2 Credit" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "100 Credits" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.

Was (HighLevel)	Now (Votel)	What to do
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
if_else "yes"	a condition that never matches (branch on which trigger fired (no Votel equivalent))	Votel runs one trigger per workflow, so "which trigger fired" cannot be asked: put the branch's steps in the feeder workflow for that trigger, or remove the branch.
trigger two_step_form_submission "300 Credits"	a Votel form trigger that fires on ANY form submission	Restrict the trigger to the right form in Votel, or the workflow starts on every form submission.
trigger two_step_form_submission "12 Credits"	a Votel form trigger that fires on ANY form submission	Restrict the trigger to the right form in Votel, or the workflow starts on every form submission.
trigger two_step_form_submission "30 Credits"	a Votel form trigger that fires on ANY form submission	Restrict the trigger to the right form in Votel, or the workflow starts on every form submission.
trigger two_step_form_submission "60 Credits"	a Votel form trigger that fires on ANY form submission	Restrict the trigger to the right form in Votel, or the workflow starts on every form submission.
trigger two_step_form_submission "2 Credit"	a Votel form trigger that fires on ANY form submission	Restrict the trigger to the right form in Votel, or the workflow starts on every form submission.
trigger two_step_form_submission "100 Credits"	a Votel form trigger that fires on ANY form submission	Restrict the trigger to the right form in Votel, or the workflow starts on every form submission.
30 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

[Starter] - Top Up - PPC

Steps15

Mapped10

Approximated7

Left as a note0

Added by MoveOver0

To configure18

Action needed: what changed, and what to do

Feeder workflow "TopUP 2 Credit" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "TopUP 10 Credits" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.

Was (HighLevel)	Now (Votel)	What to do
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
if_else "yes"	a condition that never matches (branch on which trigger fired (no Votel equivalent))	Votel runs one trigger per workflow, so "which trigger fired" cannot be asked: put the branch's steps in the feeder workflow for that trigger, or remove the branch.
trigger two_step_form_submission "TopUP 20 Credit"	a Votel form trigger that fires on ANY form submission	Restrict the trigger to the right form in Votel, or the workflow starts on every form submission.
trigger two_step_form_submission "TopUP 2 Credit"	a Votel form trigger that fires on ANY form submission	Restrict the trigger to the right form in Votel, or the workflow starts on every form submission.
trigger two_step_form_submission "TopUP 10 Credits"	a Votel form trigger that fires on ANY form submission	Restrict the trigger to the right form in Votel, or the workflow starts on every form submission.
18 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

[Starter]-2-Pro-xCredit

manual⚠ 4 steps not translatedOpen in Votel ↗

Steps19

Mapped13

Approximated5

Left as a note4

Added by MoveOver0

To configure24

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
if_else "yes"	a condition that never matches (branch on which trigger fired (no Votel equivalent))	Votel runs one trigger per workflow, so "which trigger fired" cannot be asked: put the branch's steps in the feeder workflow for that trigger, or remove the branch.
trigger payment_received "Pro - 3 Extra Credits"	no trigger created; the workflow has no way to start from this event	Add the Votel trigger for a purchase (product purchased / Stripe) to this workflow, then switch it on.
trigger payment_received "Pro - 2 Extra Credits"	no trigger created; the workflow has no way to start from this event	Add the Votel trigger for a purchase (product purchased / Stripe) to this workflow, then switch it on.
trigger payment_received "Pro - 1 Extra Credit"	no trigger created; the workflow has no way to start from this event	Add the Votel trigger for a purchase (product purchased / Stripe) to this workflow, then switch it on.
trigger payment_received "Pro - 4 Extra Credits"	no trigger created; the workflow has no way to start from this event	Add the Votel trigger for a purchase (product purchased / Stripe) to this workflow, then switch it on.
24 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

[Starter]-3-Agency-xCredit

manual⚠ 4 steps not translatedOpen in Votel ↗

Steps19

Mapped13

Approximated5

Left as a note4

Added by MoveOver0

To configure20

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
if_else "yes"	a condition that never matches (branch on which trigger fired (no Votel equivalent))	Votel runs one trigger per workflow, so "which trigger fired" cannot be asked: put the branch's steps in the feeder workflow for that trigger, or remove the branch.
trigger payment_received "Agency - 4 Extra Credits"	no trigger created; the workflow has no way to start from this event	Add the Votel trigger for a purchase (product purchased / Stripe) to this workflow, then switch it on.
trigger payment_received "Agency - 2 Extra Credits"	no trigger created; the workflow has no way to start from this event	Add the Votel trigger for a purchase (product purchased / Stripe) to this workflow, then switch it on.
trigger payment_received "Agency - 1 Extra Credit"	no trigger created; the workflow has no way to start from this event	Add the Votel trigger for a purchase (product purchased / Stripe) to this workflow, then switch it on.
trigger payment_received "Agency - 3 Extra Credits"	no trigger created; the workflow has no way to start from this event	Add the Votel trigger for a purchase (product purchased / Stripe) to this workflow, then switch it on.
20 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

July Promo

Steps16

Mapped8

Approximated8

Left as a note0

Added by MoveOver0

To configure6

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
event_start_date "Monday 9am"	the date set on the following wait	Check the following wait carries the right date.
wait "Wait till Monday 9am"	GoHighLevel wait type "appointment" replaced by a 1-day wait	Set the wait to what you need (Votel has no "wait until the appointment").
6 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

(00) Alex's Email Sequence - Ecosystem / (03) Pro Plan Sequence - [PUBLISHED]

GHL migration: (00) Alex's Email Sequence - Ecosystem / (03) Pro Plan Sequence - [PUBLISHED]Open agent ↗9

1. Pro - If purchase is done in ENTRY SEQUENCE 1 - [READY - USE THIS]

Steps5

Mapped3

Approximated3

Left as a note0

Added by MoveOver0

To configure0

Hand-offsremoves from 1. Pro Plan Entry Emails - Sequence 1 - [v2 NEW TEMPS]enrolls 2. Pro Plan's Ecosystem [v2 NEW TEMPS]

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
if_else "yes"	a condition that never matches (branch on which trigger fired (no Votel equivalent))	Votel runs one trigger per workflow, so "which trigger fired" cannot be asked: put the branch's steps in the feeder workflow for that trigger, or remove the branch.

Map (as in HighLevel; nothing added)

1. Pro - If purchase is done in ENTRY SEQUENCE 1 - [READY]

Steps14

Mapped10

Approximated8

Left as a note0

Added by MoveOver0

To configure0

Hand-offsremoves from 1. Pro Plan Entry Emails - Sequence 1 - [v2 NEW TEMPS]enrolls 2. Pro Plan's Ecosystem [v2 NEW TEMPS]removes from 1. Pro Plan Entry Emails - Sequence 1 - [v2 NEW TEMPS]enrolls 2. Pro Plan's Ecosystem [v2 NEW TEMPS]removes from 1. Pro Plan Entry Emails - Sequence 1 - [v2 NEW TEMPS]enrolls 2. Pro Plan's Ecosystem [v2 NEW TEMPS]removes from 1. Pro Plan Entry Emails - Sequence 1 - [v2 NEW TEMPS]enrolls 2. Pro Plan's Ecosystem [v2 NEW TEMPS]

What MoveOver changed, and why

Feeder workflow "Contact Tag is: plan_enterprise" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Contact Tag is: plan_unlimited" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Contact Tag Entered Pro Plan" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Contact Tag is: plan_saas" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.

Map (as in HighLevel; nothing added)

1. Pro Plan Entry Emails - Sequence 1 - [v2 NEW TEMPS]

manualModified for continuityOpen in Votel ↗

Steps16

Mapped8

Approximated6

Left as a note0

Added by MoveOver2

To configure5

Hand-offsenrolls 2. Pro Plan's Ecosystem [v2 NEW TEMPS]

Action needed: what changed, and what to do

Resume router added in front of the workflow: 1 resume point (s3_wait_5_days). A contact placed by MoveOver waits until its HighLevel due time, then continues at that step; every other contact skips the router.

Was (HighLevel)	Now (Votel)	What to do
add_to_workflow "Add to Workflow - Pro ECO"	child workflow "2. Pro Plan's Ecosystem [v2 NEW TEMPS]" resolved in a second pass	Check this step: child workflow "2. Pro Plan's Ecosystem [v2 NEW TEMPS]" resolved in a second pass.
5 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Maps: the HighLevel original (left) and as built in Votel, with the added block (right)

In HighLevel

In Votel router added

2. Pro Plan Purchase In other APPS ECOSYSTEM - [READY - USE THIS]

Steps25

Mapped10

Approximated16

Left as a note0

Added by MoveOver0

To configure0

Hand-offsremoves from 2. Funnel Kit's Ecosystem [INTRO TO ALL OTHER APPS BUT Funnel Kit] - v2 NEW TEMPSenrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Bookkeeping's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Starter Plan's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Snapshot Pack's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Migration Service's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from (02) Audit Service Ecosystem v2 NEW TEMPSenrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from (02) Coaching Program Ecosystem - v2 NEW TEMPSenrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Pro Plan Purchase In other APPS ECOSYSTEM - [READY - USE THIS]

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
remove_from_workflow "Remove from Workflow - Bookkeeping ECOSYSTEM WORKFLOW (SELECT once it is done)"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "Remove from Workflow - Snapshot Pack ECOSYSTEM WORKFLOW (SELECT once it is done)"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "Remove from Workflow - Migration Service ECOSYSTEM WORKFLOW (SELECT once it is done)"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "Remove from Audit Service Ecosystem"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "Remove from Coaching Program Ecosystem"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "REMOVE FROM THIS FLOW"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
if_else "yes"	a condition that never matches (branch on which trigger fired (no Votel equivalent))	Votel runs one trigger per workflow, so "which trigger fired" cannot be asked: put the branch's steps in the feeder workflow for that trigger, or remove the branch.

Map (as in HighLevel; nothing added)

2. Pro Plan SAAS Purchase In other APPS ECOSYSTEM - DELETE

Steps17

Mapped12

Approximated10

Left as a note0

Added by MoveOver0

To configure0

Action needed: what changed, and what to do

Feeder workflow "Contact Tag: SC_Eco_In" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Contact Tag: SM_Eco_In" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Contact Tag: SAAS PLAN" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Contact Tag: Sl_Eco_In" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Contact Tag: SS_Eco_In" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.

Was (HighLevel)	Now (Votel)	What to do
remove_from_workflow "Remove from Workflow - Bookkeeping ECOSYSTEM WORKFLOW (SELECT once it is done)"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "Remove from Workflow - Snapshot Pack ECOSYSTEM WORKFLOW (SELECT once it is done)"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "Remove from Workflow - Migration Service ECOSYSTEM WORKFLOW (SELECT once it is done)"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.

Map (as in HighLevel; nothing added)

2. Pro Plan's Ecosystem [v2 NEW TEMPS]

Steps19

Mapped10

Approximated9

Left as a note0

Added by MoveOver0

To configure16

Hand-offsenrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHED

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
16 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

3. Pro Plan GROUP Purchase In other APPS ECOSYSTEM - [READY]

Steps17

Mapped12

Approximated10

Left as a note0

Added by MoveOver0

To configure0

Action needed: what changed, and what to do

Feeder workflow "Contact Tag: GROUP PLAN" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Contact Tag: SC_Eco_In" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Contact Tag: SM_Eco_In" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Contact Tag: SF_Eco_In" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Contact Tag: SS_Eco_In" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.

Was (HighLevel)	Now (Votel)	What to do
remove_from_workflow "Remove from Workflow - Bookkeeping ECOSYSTEM WORKFLOW (SELECT once it is done)"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "Remove from Workflow - Snapshot Pack ECOSYSTEM WORKFLOW (SELECT once it is done)"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "Remove from Workflow - Migration Service'S ECOSYSTEM WORKFLOW (SELECT once it is done)"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.

Map (as in HighLevel; nothing added)

4. Pro Plan ENTERPRISE Purchase In other APPS ECOSYSTEM - [READY]

Steps17

Mapped11

Approximated10

Left as a note0

Added by MoveOver0

To configure0

Action needed: what changed, and what to do

Feeder workflow "Contact Tag: SF_Eco_In" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Contact Tag: SS_Eco_In" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Contact Tag: ENTERPRISE PLAN" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Contact Tag: Sm_Eco_In" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.

Was (HighLevel)	Now (Votel)	What to do
remove_from_workflow "Remove from Workflow - Bookkeeping ECOSYSTEM WORKFLOW (SELECT once it is done)"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "Remove from Workflow - Snapshot Pack ECOSYSTEM WORKFLOW (SELECT once it is done)"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "Remove from Workflow - Migration Service'S ECOSYSTEM WORKFLOW (SELECT once it is done)"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.

Map (as in HighLevel; nothing added)

5. Pro Plan UNLIMITED Purchase In other APPS ECOSYSTEM - [READY]

Steps17

Mapped12

Approximated10

Left as a note0

Added by MoveOver0

To configure0

Action needed: what changed, and what to do

Feeder workflow "Contact Tag: SC_Eco_In" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Contact Tag: UNLIMITED PLAN" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Contact Tag: SF_Eco_In" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Contact Tag: SL_Eco_In" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Contact Tag: Sm_Eco_In" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.

Was (HighLevel)	Now (Votel)	What to do
remove_from_workflow "Remove from Workflow - Bookkeeping ECOSYSTEM WORKFLOW (SELECT once it is done)"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "Remove from Workflow - Snapshot Pack ECOSYSTEM WORKFLOW (SELECT once it is done)"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "Remove from Workflow - Migration Service'S ECOSYSTEM WORKFLOW (SELECT once it is done)"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.

Map (as in HighLevel; nothing added)

Pro Plan

GHL migration: Pro PlanOpen agent ↗7

[MAY 2026] Pro Plan - Generate License Keys

Steps20

Mapped12

Approximated13

Left as a note0

Added by MoveOver0

To configure14

Action needed: what changed, and what to do

Feeder workflow "Unlimited Monthly" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Team Monthly" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Team Annual" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Unlimited Annual" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Solo Monthly" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.

Was (HighLevel)	Now (Votel)	What to do
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
if_else "yes"	a condition that never matches (branch on which trigger fired (no Votel equivalent))	Votel runs one trigger per workflow, so "which trigger fired" cannot be asked: put the branch's steps in the feeder workflow for that trigger, or remove the branch.
trigger two_step_form_submission "Solo Annual"	a Votel form trigger that fires on ANY form submission	Restrict the trigger to the right form in Votel, or the workflow starts on every form submission.
trigger two_step_form_submission "Unlimited Monthly"	a Votel form trigger that fires on ANY form submission	Restrict the trigger to the right form in Votel, or the workflow starts on every form submission.
trigger two_step_form_submission "Team Monthly"	a Votel form trigger that fires on ANY form submission	Restrict the trigger to the right form in Votel, or the workflow starts on every form submission.
trigger two_step_form_submission "Team Annual"	a Votel form trigger that fires on ANY form submission	Restrict the trigger to the right form in Votel, or the workflow starts on every form submission.
trigger two_step_form_submission "Unlimited Annual"	a Votel form trigger that fires on ANY form submission	Restrict the trigger to the right form in Votel, or the workflow starts on every form submission.
trigger two_step_form_submission "Solo Monthly"	a Votel form trigger that fires on ANY form submission	Restrict the trigger to the right form in Votel, or the workflow starts on every form submission.
14 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

[Pro] - Cancel Subscription

Steps3

Mapped3

Approximated1

Left as a note0

Added by MoveOver0

To configure3

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
3 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

Contact Us

Steps2

Mapped0

Approximated3

Left as a note0

Added by MoveOver0

To configure3

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
3 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

Free - Generate API Keys

Steps17

Mapped21

Approximated0

Left as a note0

Added by MoveOver0

To configure25

Action needed: what changed, and what to do

Feeder workflow "Tag = unlimited" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Tag = group" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Tag = free_saas" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Tag = Free_Free" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.

Was (HighLevel)	Now (Votel)	What to do
25 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

Generate License Keys

Steps45

Mapped27

Approximated23

Left as a note0

Added by MoveOver0

To configure40

Hand-offsenrolls Welcome Emailenrolls Welcome Email

Action needed: what changed, and what to do

Feeder workflow "Inbound Webhook" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "SaaS" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Group" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Free" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Enterprise" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.

Was (HighLevel)	Now (Votel)	What to do
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
add_to_workflow "Add to Free Welcome Email"	child workflow "Welcome Email" resolved in a second pass	Check this step: child workflow "Welcome Email" resolved in a second pass.
if_else "yes"	a condition that never matches (branch on a webhook response (9.response.id))	Rebuild the condition in Votel on a field that exists there, or remove the branch.
internal_notification "Internal Notification"	an internal notification with NO recipient	Pick the team member who should receive it.
add_to_workflow "Add to Free Welcome Email"	child workflow "Welcome Email" resolved in a second pass	Check this step: child workflow "Welcome Email" resolved in a second pass.
if_else "yes"	a condition that never matches (branch on which trigger fired (no Votel equivalent); branch on the inbound webhook payload (email))	Votel runs one trigger per workflow, so "which trigger fired" cannot be asked: put the branch's steps in the feeder workflow for that trigger, or remove the branch.
trigger two_step_form_submission "Unlimited"	a Votel form trigger that fires on ANY form submission	Restrict the trigger to the right form in Votel, or the workflow starts on every form submission.
trigger inbound_webhook "Inbound Webhook"	a Votel webhook trigger; Votel gives it a NEW URL when the workflow is switched on	In Votel, switch the workflow on, open its trigger and copy the new webhook URL; update the system that posts to HighLevel's URL (HighLevel trigger id unknown) to post to Votel's instead.
trigger two_step_form_submission "SaaS"	a Votel form trigger that fires on ANY form submission	Restrict the trigger to the right form in Votel, or the workflow starts on every form submission.
trigger two_step_form_submission "Group"	a Votel form trigger that fires on ANY form submission	Restrict the trigger to the right form in Votel, or the workflow starts on every form submission.
trigger two_step_form_submission "Enterprise"	a Votel form trigger that fires on ANY form submission	Restrict the trigger to the right form in Votel, or the workflow starts on every form submission.
40 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

Reset API Key & Count

Steps3

Mapped4

Approximated1

Left as a note0

Added by MoveOver0

To configure3

Action needed: what changed, and what to do

Feeder workflow "Contact Tag" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.

Was (HighLevel)	Now (Votel)	What to do
3 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

Welcome Email

Steps2

Mapped1

Approximated1

Left as a note0

Added by MoveOver0

To configure1

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
1 item Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

(00) Alex's Email Sequence - Ecosystem / (02) Funnel Kit Sequence - [PUBLISHED]

GHL migration: (00) Alex's Email Sequence - Ecosystem / (02) Funnel Kit Sequence - [PUBLISHED]Open agent ↗6

0. Funnel Purchase + Tag - Inbound Webhook trigger [READY]

Steps2

Mapped1

Approximated2

Left as a note0

Added by MoveOver0

To configure0

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
create_update_contact "Create Contact"	an update-contact step (fields skipped: name)	Check the fields on the step; the ones listed were skipped.
trigger inbound_webhook "Inbound Webhook - Funnel Kit SIGN UP"	a Votel webhook trigger; Votel gives it a NEW URL when the workflow is switched on	In Votel, switch the workflow on, open its trigger and copy the new webhook URL; update the system that posts to HighLevel's URL (HighLevel trigger id unknown) to post to Votel's instead.

Map (as in HighLevel; nothing added)

00. Funnel Inbound Webhook - Opt-In form [READY]

Steps2

Mapped0

Approximated3

Left as a note0

Added by MoveOver0

To configure2

Hand-offsenrolls 1. Funnel Kit Entry Emails - Sequence 1 [v2 TEMPLATE READY]

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
create_update_contact "Create contact"	an update-contact step (fields skipped: name)	Check the fields on the step; the ones listed were skipped.
add_to_workflow "Add to : 1. Funnel Kit Entry Emails - Sequence 1"	child workflow "1. Funnel Kit Entry Emails - Sequence 1 [v2 TEMPLATE READY]" resolved in a second pass	Check this step: child workflow "1. Funnel Kit Entry Emails - Sequence 1 [v2 TEMPLATE READY]" resolved in a second pass.
trigger inbound_webhook "Funnel Opt-in Inbound Webhook"	a Votel webhook trigger; Votel gives it a NEW URL when the workflow is switched on	In Votel, switch the workflow on, open its trigger and copy the new webhook URL; update the system that posts to HighLevel's URL (HighLevel trigger id unknown) to post to Votel's instead.
2 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

1. Funnel - If purchase is done in ENTRY SEQUENCE 1 - [READY]

Steps5

Mapped3

Approximated3

Left as a note0

Added by MoveOver0

To configure0

Hand-offsremoves from 1. Funnel Kit Entry Emails - Sequence 1 [v2 TEMPLATE READY]enrolls 2. Funnel Kit's Ecosystem [INTRO TO ALL OTHER APPS BUT Funnel Kit] - v2 NEW TEMPS

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
if_else "yes"	a condition that never matches (branch on which trigger fired (no Votel equivalent))	Votel runs one trigger per workflow, so "which trigger fired" cannot be asked: put the branch's steps in the feeder workflow for that trigger, or remove the branch.

Map (as in HighLevel; nothing added)

1. Funnel Kit Entry Emails - Sequence 1 [v2 TEMPLATE READY]

Steps13

Mapped7

Approximated6

Left as a note0

Added by MoveOver0

To configure4

Hand-offsenrolls 2. Funnel Kit's Ecosystem [INTRO TO ALL OTHER APPS BUT Funnel Kit] - v2 NEW TEMPS

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
add_to_workflow "Add to Workflow -Funnel Kit ECO"	child workflow "2. Funnel Kit's Ecosystem [INTRO TO ALL OTHER APPS BUT Funnel Kit] - v2 NEW TEMPS" resolved in a second pass	Check this step: child workflow "2. Funnel Kit's Ecosystem [INTRO TO ALL OTHER APPS BUT Funnel Kit] - v2 NEW TEMPS" resolved in a second pass.
4 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

2. Funnel Kit Purchase In other Tool's ECOSYSTEM - [READY}

Steps25

Mapped10

Approximated16

Left as a note0

Added by MoveOver0

To configure0

Hand-offsremoves from 2. Starter Plan's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Bookkeeping's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Pro Plan's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Snapshot Pack's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Migration Service's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from (02) Audit Service Ecosystem v2 NEW TEMPSenrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from (02) Coaching Program Ecosystem - v2 NEW TEMPSenrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Funnel Kit Purchase In other Tool's ECOSYSTEM - [READY}

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
remove_from_workflow "Remove from Workflow - Bookkeeping'S ECOSYSTEM WORKFLOW (SELECT once it is done)"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "Remove from Workflow - Pro Plan'S ECOSYSTEM WORKFLOW (SELECT once it is done)"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "Remove from Workflow - Snapshot Pack'S ECOSYSTEM WORKFLOW (SELECT once it is done)"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "Remove from Workflow - Migration Service'S ECOSYSTEM WORKFLOW (SELECT once it is done)"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "Remove from Audit Service Ecosystem"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "Remove from Coaching Program Ecosystem"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "REMOVE FROM THIS FLOW"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
if_else "yes"	a condition that never matches (branch on which trigger fired (no Votel equivalent))	Votel runs one trigger per workflow, so "which trigger fired" cannot be asked: put the branch's steps in the feeder workflow for that trigger, or remove the branch.

Map (as in HighLevel; nothing added)

2. Funnel Kit's Ecosystem [INTRO TO ALL OTHER APPS BUT Funnel Kit] - v2 NEW TEMPS

Steps19

Mapped10

Approximated9

Left as a note0

Added by MoveOver0

To configure14

Hand-offsenrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHED

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
14 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

(00) Alex's Email Sequence - Ecosystem / (07) Audit Service Sequence [New] -PUBLISHED

GHL migration: (00) Alex's Email Sequence - Ecosystem / (07) Audit Service Sequence [New] -PUBLISHEDOpen agent ↗5

(01) Audit Service Entry Emails - Sequence 1 - v2 NEW TEMPS

manualModified for continuityOpen in Votel ↗

Steps16

Mapped8

Approximated6

Left as a note0

Added by MoveOver2

To configure3

Hand-offsenrolls (02) Audit Service Ecosystem v2 NEW TEMPS

Action needed: what changed, and what to do

Resume router added in front of the workflow: 1 resume point (s9_wait_2_days). A contact placed by MoveOver waits until its HighLevel due time, then continues at that step; every other contact skips the router.

Was (HighLevel)	Now (Votel)	What to do
add_to_workflow "Add to Audit Service Ecosystem"	child workflow "(02) Audit Service Ecosystem v2 NEW TEMPS" resolved in a second pass	Check this step: child workflow "(02) Audit Service Ecosystem v2 NEW TEMPS" resolved in a second pass.
3 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Maps: the HighLevel original (left) and as built in Votel, with the added block (right)

In HighLevel

In Votel router added

(02) Audit Service Ecosystem v2 NEW TEMPS

manualModified for continuityOpen in Votel ↗

Steps22

Mapped10

Approximated9

Left as a note0

Added by MoveOver3

To configure12

Hand-offsenrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHED

Action needed: what changed, and what to do

Resume router added in front of the workflow: 2 resume points (s3_wait_2_days, s5_wait_2_days). A contact placed by MoveOver waits until its HighLevel due time, then continues at that step; every other contact skips the router.

Was (HighLevel)	Now (Votel)	What to do
12 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Maps: the HighLevel original (left) and as built in Votel, with the added block (right)

In HighLevel

In Votel router added

(03) Audit Service Signup in Another Tool's Ecosystem

Steps12

Mapped4

Approximated8

Left as a note0

Added by MoveOver0

To configure0

Hand-offsremoves from 2. Snapshot Pack's Ecosystem [v2 NEW TEMPS]removes from 2. Pro Plan's Ecosystem [v2 NEW TEMPS]removes from 2. Bookkeeping's Ecosystem [v2 NEW TEMPS]removes from 2. Funnel Kit's Ecosystem [INTRO TO ALL OTHER APPS BUT Funnel Kit] - v2 NEW TEMPSremoves from 2. Migration Service's Ecosystem [v2 NEW TEMPS]removes from 2. Starter Plan's Ecosystem [v2 NEW TEMPS]removes from (02) Coaching Program Ecosystem - v2 NEW TEMPSenrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHED

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
remove_from_workflow "Remove from Coaching Program Ecosystem"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.

Map (as in HighLevel; nothing added)

NOT NEEDED - FREE TOOL - Audit Purchase During Entry Sequence

Steps5

Mapped3

Approximated3

Left as a note0

Added by MoveOver0

To configure0

Hand-offsremoves from (01) Audit Service Entry Emails - Sequence 1 - v2 NEW TEMPSenrolls (02) Audit Service Ecosystem v2 NEW TEMPS

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
if_else "yes"	a condition that never matches (branch on which trigger fired (no Votel equivalent))	Votel runs one trigger per workflow, so "which trigger fired" cannot be asked: put the branch's steps in the feeder workflow for that trigger, or remove the branch.

Map (as in HighLevel; nothing added)

NOT NEEDED - FREE TOOL - Audit Service Purchase in Another Tool's Ecosystem

Steps17

Mapped6

Approximated12

Left as a note0

Added by MoveOver0

To configure0

Hand-offsremoves from 2. Snapshot Pack's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Pro Plan's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Bookkeeping's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Funnel Kit's Ecosystem [INTRO TO ALL OTHER APPS BUT Funnel Kit] - v2 NEW TEMPSenrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Migration Service's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from NOT NEEDED - FREE TOOL - Audit Service Purchase in Another Tool's Ecosystem

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
remove_from_workflow "REMOVE FROM THIS FLOW"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
if_else "yes"	a condition that never matches (branch on which trigger fired (no Votel equivalent))	Votel runs one trigger per workflow, so "which trigger fired" cannot be asked: put the branch's steps in the feeder workflow for that trigger, or remove the branch.

Map (as in HighLevel; nothing added)

(00) Alex's Email Sequence - Ecosystem / (08) Coaching Program Sequence [New] - PUBLISHED

GHL migration: (00) Alex's Email Sequence - Ecosystem / (08) Coaching Program Sequence [New] - PUBLISHEDOpen agent ↗5

(01) Coaching Program Entry Emails - Sequence 1 - [v2 NEW TEMPS]

manualModified for continuityOpen in Votel ↗

Steps16

Mapped8

Approximated6

Left as a note0

Added by MoveOver2

To configure3

Hand-offsenrolls (02) Coaching Program Ecosystem - v2 NEW TEMPS

Action needed: what changed, and what to do

Resume router added in front of the workflow: 1 resume point (s9_wait_2_days). A contact placed by MoveOver waits until its HighLevel due time, then continues at that step; every other contact skips the router.

Was (HighLevel)	Now (Votel)	What to do
add_to_workflow "Add to Coaching Program Ecosystem"	child workflow "(02) Coaching Program Ecosystem - v2 NEW TEMPS" resolved in a second pass	Check this step: child workflow "(02) Coaching Program Ecosystem - v2 NEW TEMPS" resolved in a second pass.
3 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Maps: the HighLevel original (left) and as built in Votel, with the added block (right)

In HighLevel

In Votel router added

(02) Coaching Program Ecosystem - v2 NEW TEMPS

Steps19

Mapped10

Approximated9

Left as a note0

Added by MoveOver0

To configure12

Hand-offsenrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHED

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
12 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

(03) Coaching Program Signup in Another Tool's Ecosystem

Steps12

Mapped4

Approximated8

Left as a note0

Added by MoveOver0

To configure0

Hand-offsremoves from 2. Snapshot Pack's Ecosystem [v2 NEW TEMPS]removes from 2. Pro Plan's Ecosystem [v2 NEW TEMPS]removes from 2. Bookkeeping's Ecosystem [v2 NEW TEMPS]removes from 2. Funnel Kit's Ecosystem [INTRO TO ALL OTHER APPS BUT Funnel Kit] - v2 NEW TEMPSremoves from 2. Migration Service's Ecosystem [v2 NEW TEMPS]removes from 2. Starter Plan's Ecosystem [v2 NEW TEMPS]removes from (02) Audit Service Ecosystem v2 NEW TEMPSenrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHED

What MoveOver changed

Nothing: every step translated exactly and nothing is left to configure.

Map (as in HighLevel; nothing added)

NOT NEEDED - FREE TOOL - Coaching Program Purchase in Another Tool's Ecosystem

Steps17

Mapped6

Approximated12

Left as a note0

Added by MoveOver0

To configure0

Hand-offsremoves from 2. Snapshot Pack's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Pro Plan's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Bookkeeping's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Funnel Kit's Ecosystem [INTRO TO ALL OTHER APPS BUT Funnel Kit] - v2 NEW TEMPSenrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Migration Service's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from NOT NEEDED - FREE TOOL - Coaching Program Purchase in Another Tool's Ecosystem

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
remove_from_workflow "REMOVE FROM THIS FLOW"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
if_else "yes"	a condition that never matches (branch on which trigger fired (no Votel equivalent))	Votel runs one trigger per workflow, so "which trigger fired" cannot be asked: put the branch's steps in the feeder workflow for that trigger, or remove the branch.

Map (as in HighLevel; nothing added)

NOT NEEDED - FREE TOOL - Coaching Purchase During Entry Sequence

Steps5

Mapped3

Approximated3

Left as a note0

Added by MoveOver0

To configure0

Hand-offsremoves from (01) Coaching Program Entry Emails - Sequence 1 - [v2 NEW TEMPS]enrolls (02) Coaching Program Ecosystem - v2 NEW TEMPS

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
if_else "yes"	a condition that never matches (branch on which trigger fired (no Votel equivalent))	Votel runs one trigger per workflow, so "which trigger fired" cannot be asked: put the branch's steps in the feeder workflow for that trigger, or remove the branch.

Map (as in HighLevel; nothing added)

Partner Program

GHL migration: Partner ProgramOpen agent ↗5

1. Lead Subscribed On

Steps2

Mapped1

Approximated2

Left as a note0

Added by MoveOver0

To configure2

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
slack_message "Send notification to Slack"	a Slack step that needs the Slack integration connected in Votel	Connect Slack under Settings > Integrations, then pick the channel on the step.
trigger inbound_webhook "Inbound Webhook"	a Votel webhook trigger; Votel gives it a NEW URL when the workflow is switched on	In Votel, switch the workflow on, open its trigger and copy the new webhook URL; update the system that posts to HighLevel's URL (HighLevel trigger id unknown) to post to Votel's instead.
2 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

2. Lead Sign On

Steps2

Mapped1

Approximated2

Left as a note0

Added by MoveOver0

To configure2

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
slack_message "Send notification to Slack"	a Slack step that needs the Slack integration connected in Votel	Connect Slack under Settings > Integrations, then pick the channel on the step.
trigger inbound_webhook "Inbound Webhook"	a Votel webhook trigger; Votel gives it a NEW URL when the workflow is switched on	In Votel, switch the workflow on, open its trigger and copy the new webhook URL; update the system that posts to HighLevel's URL (HighLevel trigger id unknown) to post to Votel's instead.
2 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

3. Lead Becomes Referral

Steps2

Mapped1

Approximated2

Left as a note0

Added by MoveOver0

To configure2

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
slack_message "Send notification to Slack"	a Slack step that needs the Slack integration connected in Votel	Connect Slack under Settings > Integrations, then pick the channel on the step.
trigger inbound_webhook "Inbound Webhook"	a Votel webhook trigger; Votel gives it a NEW URL when the workflow is switched on	In Votel, switch the workflow on, open its trigger and copy the new webhook URL; update the system that posts to HighLevel's URL (HighLevel trigger id unknown) to post to Votel's instead.
2 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

4. Reward Created On

Steps2

Mapped1

Approximated2

Left as a note0

Added by MoveOver0

To configure2

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
slack_message "Send notification to Slack"	a Slack step that needs the Slack integration connected in Votel	Connect Slack under Settings > Integrations, then pick the channel on the step.
trigger inbound_webhook "Inbound Webhook"	a Votel webhook trigger; Votel gives it a NEW URL when the workflow is switched on	In Votel, switch the workflow on, open its trigger and copy the new webhook URL; update the system that posts to HighLevel's URL (HighLevel trigger id unknown) to post to Votel's instead.
2 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

5. Lead Cancelled On

Steps2

Mapped1

Approximated2

Left as a note0

Added by MoveOver0

To configure2

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
slack_message "Send notification to Slack"	a Slack step that needs the Slack integration connected in Votel	Connect Slack under Settings > Integrations, then pick the channel on the step.
trigger inbound_webhook "Inbound Webhook"	a Votel webhook trigger; Votel gives it a NEW URL when the workflow is switched on	In Votel, switch the workflow on, open its trigger and copy the new webhook URL; update the system that posts to HighLevel's URL (HighLevel trigger id unknown) to post to Votel's instead.
2 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

(00) Alex's Email Sequence - Ecosystem / (00) Bright Path Tools Inbound Hooks [PUBLISHED]

GHL migration: (00) Alex's Email Sequence - Ecosystem / (00) Bright Path Tools Inbound Hooks [PUBLISHED]Open agent ↗4

Bright Path Tools - Purchase made on site

Steps8

Mapped7

Approximated6

Left as a note0

Added by MoveOver0

To configure12

Hand-offsenrolls 2. Migration Service's Ecosystem [v2 NEW TEMPS]enrolls 2. Starter Plan's Ecosystem [v2 NEW TEMPS]enrolls 2. Pro Plan's Ecosystem [v2 NEW TEMPS]enrolls 2. Bookkeeping's Ecosystem [v2 NEW TEMPS]enrolls 2. Snapshot Pack's Ecosystem [v2 NEW TEMPS]enrolls 2. Funnel Kit's Ecosystem [INTRO TO ALL OTHER APPS BUT Funnel Kit] - v2 NEW TEMPS

Action needed: what changed, and what to do

Feeder workflow "Tag Purchased sm on site" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Tag Purchased sc on site" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Tag Purchased se on site" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Tag Purchased sl on site" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Tag Purchased sf on site" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.

Was (HighLevel)	Now (Votel)	What to do
add_to_workflow "Add to Migration Eco"	child workflow "2. Migration Service's Ecosystem [v2 NEW TEMPS]" resolved in a second pass	Check this step: child workflow "2. Migration Service's Ecosystem [v2 NEW TEMPS]" resolved in a second pass.
add_to_workflow "Add to Starter Eco"	child workflow "2. Starter Plan's Ecosystem [v2 NEW TEMPS]" resolved in a second pass	Check this step: child workflow "2. Starter Plan's Ecosystem [v2 NEW TEMPS]" resolved in a second pass.
add_to_workflow "Add to Pro Eco"	child workflow "2. Pro Plan's Ecosystem [v2 NEW TEMPS]" resolved in a second pass	Check this step: child workflow "2. Pro Plan's Ecosystem [v2 NEW TEMPS]" resolved in a second pass.
add_to_workflow "Add to Books Eco"	child workflow "2. Bookkeeping's Ecosystem [v2 NEW TEMPS]" resolved in a second pass	Check this step: child workflow "2. Bookkeeping's Ecosystem [v2 NEW TEMPS]" resolved in a second pass.
add_to_workflow "Add to Snapshot Eco"	child workflow "2. Snapshot Pack's Ecosystem [v2 NEW TEMPS]" resolved in a second pass	Check this step: child workflow "2. Snapshot Pack's Ecosystem [v2 NEW TEMPS]" resolved in a second pass.
add_to_workflow "Add to Funnel Eco"	child workflow "2. Funnel Kit's Ecosystem [INTRO TO ALL OTHER APPS BUT Funnel Kit] - v2 NEW TEMPS" resolved in a second pass	Check this step: child workflow "2. Funnel Kit's Ecosystem [INTRO TO ALL OTHER APPS BUT Funnel Kit] - v2 NEW TEMPS" resolved in a second pass.
12 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

Bright Path Tools Inbound (FREE) - Lead Optin

Steps16

Mapped7

Approximated9

Left as a note0

Added by MoveOver0

To configure26

Hand-offsenrolls 1. Bookkeeping Entry Emails - Sequence 1 - [v2 NEW TEMPS]]enrolls 1. Migration Service Entry Emails - Sequence 1 [v2 NEW TEMPS]]enrolls 1. Pro Plan Entry Emails - Sequence 1 - [v2 NEW TEMPS]enrolls 1. Starter Plan Entry Emails - Sequence 1 [v2 NEW TEMPS]enrolls 1. Snapshot Pack Entry Emails - Sequence 1 - [v2 NEW TEMPS]enrolls (01) Coaching Program Entry Emails - Sequence 1 - [v2 NEW TEMPS]enrolls (01) Audit Service Entry Emails - Sequence 1 - v2 NEW TEMPS

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
add_to_workflow "Add to Books INTRO SEQUENCE"	child workflow "1. Bookkeeping Entry Emails - Sequence 1 - [v2 NEW TEMPS]]" resolved in a second pass	Check this step: child workflow "1. Bookkeeping Entry Emails - Sequence 1 - [v2 NEW TEMPS]]" resolved in a second pass.
add_to_workflow "Add to Migration INTRO SEQUENCE"	child workflow "1. Migration Service Entry Emails - Sequence 1 [v2 NEW TEMPS]]" resolved in a second pass	Check this step: child workflow "1. Migration Service Entry Emails - Sequence 1 [v2 NEW TEMPS]]" resolved in a second pass.
add_to_workflow "Add to Pro INTRO SEQUENCE"	child workflow "1. Pro Plan Entry Emails - Sequence 1 - [v2 NEW TEMPS]" resolved in a second pass	Check this step: child workflow "1. Pro Plan Entry Emails - Sequence 1 - [v2 NEW TEMPS]" resolved in a second pass.
add_to_workflow "Add to Starter INTRO SEQUENCE"	child workflow "1. Starter Plan Entry Emails - Sequence 1 [v2 NEW TEMPS]" resolved in a second pass	Check this step: child workflow "1. Starter Plan Entry Emails - Sequence 1 [v2 NEW TEMPS]" resolved in a second pass.
add_to_workflow "Add to Snapshot INTRO SEQUENCE"	child workflow "1. Snapshot Pack Entry Emails - Sequence 1 - [v2 NEW TEMPS]" resolved in a second pass	Check this step: child workflow "1. Snapshot Pack Entry Emails - Sequence 1 - [v2 NEW TEMPS]" resolved in a second pass.
add_to_workflow "Add to Coaching intro sequence"	child workflow "(01) Coaching Program Entry Emails - Sequence 1 - [v2 NEW TEMPS]" resolved in a second pass	Check this step: child workflow "(01) Coaching Program Entry Emails - Sequence 1 - [v2 NEW TEMPS]" resolved in a second pass.
add_to_workflow "Add to Audit INTRO SEQUENCE"	child workflow "(01) Audit Service Entry Emails - Sequence 1 - v2 NEW TEMPS" resolved in a second pass	Check this step: child workflow "(01) Audit Service Entry Emails - Sequence 1 - v2 NEW TEMPS" resolved in a second pass.
if_else "yes"	a condition that never matches (branch on the inbound webhook payload (source))	Rebuild the condition in Votel on a field that exists there, or remove the branch.
trigger inbound_webhook "Inbound Webhook"	a Votel webhook trigger; Votel gives it a NEW URL when the workflow is switched on	In Votel, switch the workflow on, open its trigger and copy the new webhook URL; update the system that posts to HighLevel's URL (HighLevel trigger id unknown) to post to Votel's instead.
26 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

Bright Path Tools Inbound (PAID) - Purchase Made

Steps12

Mapped10

Approximated2

Left as a note0

Added by MoveOver0

To configure18

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
if_else "yes"	a condition that never matches (branch on the inbound webhook payload (product))	Rebuild the condition in Votel on a field that exists there, or remove the branch.
trigger inbound_webhook "Inbound Webhook"	a Votel webhook trigger; Votel gives it a NEW URL when the workflow is switched on	In Votel, switch the workflow on, open its trigger and copy the new webhook URL; update the system that posts to HighLevel's URL (HighLevel trigger id unknown) to post to Votel's instead.
18 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

TO REMOVE - OLD Audit Service WEBHOOK - MIGRATE 10 CONTACTS FIRST

webhookModified for continuityOpen in Votel ↗

Steps6

Mapped3

Approximated2

Left as a note0

Added by MoveOver2

To configure4

Hand-offsenrolls 2. Migration Service's Ecosystem [v2 NEW TEMPS]

Action needed: what changed, and what to do

Resume router added in front of the workflow: 1 resume point (s2_wait_15_days). A contact placed by MoveOver waits until its HighLevel due time, then continues at that step; every other contact skips the router.

Was (HighLevel)	Now (Votel)	What to do
add_to_workflow "Add to Migration ECOSYSTEM"	child workflow "2. Migration Service's Ecosystem [v2 NEW TEMPS]" resolved in a second pass	Check this step: child workflow "2. Migration Service's Ecosystem [v2 NEW TEMPS]" resolved in a second pass.
trigger inbound_webhook "Inbound Webhook"	a Votel webhook trigger; Votel gives it a NEW URL when the workflow is switched on	In Votel, switch the workflow on, open its trigger and copy the new webhook URL; update the system that posts to HighLevel's URL (HighLevel trigger id unknown) to post to Votel's instead.
4 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Maps: the HighLevel original (left) and as built in Votel, with the added block (right)

In HighLevel

In Votel router added

(00) Alex's Email Sequence - Ecosystem / (01) Starter Plan Sequence -[PUBLISHED]

GHL migration: (00) Alex's Email Sequence - Ecosystem / (01) Starter Plan Sequence -[PUBLISHED]Open agent ↗4

1. Starter - If purchase is done in ENTRY SEQUENCE 1 - READY

Steps5

Mapped3

Approximated3

Left as a note0

Added by MoveOver0

To configure0

Hand-offsremoves from 1. Starter Plan Entry Emails - Sequence 1 [v2 NEW TEMPS]enrolls 2. Starter Plan's Ecosystem [v2 NEW TEMPS]

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
if_else "yes"	a condition that never matches (branch on which trigger fired (no Votel equivalent))	Votel runs one trigger per workflow, so "which trigger fired" cannot be asked: put the branch's steps in the feeder workflow for that trigger, or remove the branch.

Map (as in HighLevel; nothing added)

1. Starter Plan Entry Emails - Sequence 1 [v2 NEW TEMPS]

manualModified for continuityOpen in Votel ↗

Steps17

Mapped8

Approximated6

Left as a note0

Added by MoveOver3

To configure7

Hand-offsenrolls 2. Starter Plan's Ecosystem [v2 NEW TEMPS]

Action needed: what changed, and what to do

Resume router added in front of the workflow: 2 resume points (s3_wait_2_days, s9_wait_2_days). A contact placed by MoveOver waits until its HighLevel due time, then continues at that step; every other contact skips the router.

Was (HighLevel)	Now (Votel)	What to do
add_to_workflow "Add to Starter ECOSYSTEM"	child workflow "2. Starter Plan's Ecosystem [v2 NEW TEMPS]" resolved in a second pass	Check this step: child workflow "2. Starter Plan's Ecosystem [v2 NEW TEMPS]" resolved in a second pass.
7 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Maps: the HighLevel original (left) and as built in Votel, with the added block (right)

In HighLevel

In Votel router added

2. Starter Plan Purchase In other Tool's ECOSYSTEM - [READY]

Steps25

Mapped10

Approximated16

Left as a note0

Added by MoveOver0

To configure0

Hand-offsremoves from 2. Snapshot Pack's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Pro Plan's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Bookkeeping's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Funnel Kit's Ecosystem [INTRO TO ALL OTHER APPS BUT Funnel Kit] - v2 NEW TEMPSenrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Migration Service's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from (02) Audit Service Ecosystem v2 NEW TEMPSenrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from (02) Coaching Program Ecosystem - v2 NEW TEMPSenrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Starter Plan Purchase In other Tool's ECOSYSTEM - [READY]

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
remove_from_workflow "Remove from Workflow - Snapshot Pack'S ECOSYSTEM WORKFLOW (SELECT once it is done)"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "Remove from Workflow - Pro Plan'S ECOSYSTEM WORKFLOW (SELECT once it is done)"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "Remove from Workflow - Bookkeeping' S ECOSYSTEM WORKFLOW (SELECT once it is done)"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "Remove from Workflow - Funnel Kit' S ECOSYSTEM WORKFLOW (SELECT once it is done)"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "Remove from Workflow - Migration Service' S ECOSYSTEM WORKFLOW (SELECT once it is done)"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "Remove from Audit Service Ecosystem"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "Remove from Coaching Program Ecosystem"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "REMOVE FROM THIS FLOW"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
if_else "yes"	a condition that never matches (branch on which trigger fired (no Votel equivalent))	Votel runs one trigger per workflow, so "which trigger fired" cannot be asked: put the branch's steps in the feeder workflow for that trigger, or remove the branch.

Map (as in HighLevel; nothing added)

2. Starter Plan's Ecosystem [v2 NEW TEMPS]

manualModified for continuityOpen in Votel ↗

Steps27

Mapped10

Approximated9

Left as a note0

Added by MoveOver8

To configure19

Hand-offsenrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHED

Action needed: what changed, and what to do

Resume router added in front of the workflow: 7 resume points (s1_wait_2_days, s3_wait_2_days, s5_wait_2_days, s7_wait_2_days, s9_wait_2_days, s11_wait_2_days, s15_wait_2_days). A contact placed by MoveOver waits until its HighLevel due time, then continues at that step; every other contact skips the router.

Was (HighLevel)	Now (Votel)	What to do
19 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Maps: the HighLevel original (left) and as built in Votel, with the added block (right)

In HighLevel

In Votel router added

(00) Alex's Email Sequence - Ecosystem / (04) Snapshot Pack Sequence - [PUBLISHED]

GHL migration: (00) Alex's Email Sequence - Ecosystem / (04) Snapshot Pack Sequence - [PUBLISHED]Open agent ↗4

1. Snapshot - If purchase is done in ENTRY SEQUENCE 1 - [READY]

Steps5

Mapped3

Approximated3

Left as a note0

Added by MoveOver0

To configure0

Hand-offsremoves from 1. Snapshot Pack Entry Emails - Sequence 1 - [v2 NEW TEMPS]enrolls 2. Snapshot Pack's Ecosystem [v2 NEW TEMPS]

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
if_else "yes"	a condition that never matches (branch on which trigger fired (no Votel equivalent))	Votel runs one trigger per workflow, so "which trigger fired" cannot be asked: put the branch's steps in the feeder workflow for that trigger, or remove the branch.

Map (as in HighLevel; nothing added)

1. Snapshot Pack Entry Emails - Sequence 1 - [v2 NEW TEMPS]

manualModified for continuityOpen in Votel ↗

Steps16

Mapped8

Approximated6

Left as a note0

Added by MoveOver2

To configure6

Hand-offsenrolls 2. Snapshot Pack's Ecosystem [v2 NEW TEMPS]

Action needed: what changed, and what to do

Resume router added in front of the workflow: 1 resume point (s3_wait_5_days). A contact placed by MoveOver waits until its HighLevel due time, then continues at that step; every other contact skips the router.

Was (HighLevel)	Now (Votel)	What to do
add_to_workflow "Add to Snapshot ECOSYSTEM"	child workflow "2. Snapshot Pack's Ecosystem [v2 NEW TEMPS]" resolved in a second pass	Check this step: child workflow "2. Snapshot Pack's Ecosystem [v2 NEW TEMPS]" resolved in a second pass.
6 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Maps: the HighLevel original (left) and as built in Votel, with the added block (right)

In HighLevel

In Votel router added

2. Snapshot Pack Purchase In other Tool's ECOSYSTEM - [READY]

Steps25

Mapped10

Approximated16

Left as a note0

Added by MoveOver0

To configure0

Hand-offsremoves from 2. Funnel Kit's Ecosystem [INTRO TO ALL OTHER APPS BUT Funnel Kit] - v2 NEW TEMPSenrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Bookkeeping's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Pro Plan's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Starter Plan's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Migration Service's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from (02) Audit Service Ecosystem v2 NEW TEMPSenrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from (02) Coaching Program Ecosystem - v2 NEW TEMPSenrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Snapshot Pack Purchase In other Tool's ECOSYSTEM - [READY]

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
remove_from_workflow "Remove from Workflow - Bookkeeping'S ECOSYSTEM WORKFLOW (SELECT once it is done)"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "Remove from Workflow - Migration Service'S ECOSYSTEM WORKFLOW (SELECT once it is done)"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "Remove from Audit Service Ecosystem"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "Remove from Coaching Program Ecosystem"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "REMOVE FROM THIS FLOW"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
if_else "yes"	a condition that never matches (branch on which trigger fired (no Votel equivalent))	Votel runs one trigger per workflow, so "which trigger fired" cannot be asked: put the branch's steps in the feeder workflow for that trigger, or remove the branch.

Map (as in HighLevel; nothing added)

2. Snapshot Pack's Ecosystem [v2 NEW TEMPS]

manualModified for continuityOpen in Votel ↗

Steps22

Mapped10

Approximated9

Left as a note0

Added by MoveOver3

To configure19

Hand-offsenrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHED

Action needed: what changed, and what to do

Resume router added in front of the workflow: 2 resume points (s1_wait_2_days, s5_wait_2_days). A contact placed by MoveOver waits until its HighLevel due time, then continues at that step; every other contact skips the router.

Was (HighLevel)	Now (Votel)	What to do
19 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Maps: the HighLevel original (left) and as built in Votel, with the added block (right)

In HighLevel

In Votel router added

(00) Alex's Email Sequence - Ecosystem / (05) Bookkeeping Sequence - [PUBLISHED]

GHL migration: (00) Alex's Email Sequence - Ecosystem / (05) Bookkeeping Sequence - [PUBLISHED]Open agent ↗4

1. Bookkeeping Entry Emails - Sequence 1 - [v2 NEW TEMPS]]

manualModified for continuityOpen in Votel ↗

Steps16

Mapped8

Approximated6

Left as a note0

Added by MoveOver2

To configure3

Hand-offsenrolls 2. Bookkeeping's Ecosystem [v2 NEW TEMPS]

Action needed: what changed, and what to do

Resume router added in front of the workflow: 1 resume point (s3_wait_2_days). A contact placed by MoveOver waits until its HighLevel due time, then continues at that step; every other contact skips the router.

Was (HighLevel)	Now (Votel)	What to do
add_to_workflow "Add to Books ECOSYSTEM"	child workflow "2. Bookkeeping's Ecosystem [v2 NEW TEMPS]" resolved in a second pass	Check this step: child workflow "2. Bookkeeping's Ecosystem [v2 NEW TEMPS]" resolved in a second pass.
3 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Maps: the HighLevel original (left) and as built in Votel, with the added block (right)

In HighLevel

In Votel router added

1. Books - If purchase is done in ENTRY SEQUENCE 1 - [READY]

Steps5

Mapped3

Approximated3

Left as a note0

Added by MoveOver0

To configure0

Hand-offsremoves from 1. Bookkeeping Entry Emails - Sequence 1 - [v2 NEW TEMPS]]enrolls 2. Bookkeeping's Ecosystem [v2 NEW TEMPS]

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
if_else "yes"	a condition that never matches (branch on which trigger fired (no Votel equivalent))	Votel runs one trigger per workflow, so "which trigger fired" cannot be asked: put the branch's steps in the feeder workflow for that trigger, or remove the branch.

Map (as in HighLevel; nothing added)

2. Bookkeeping Purchase In other Tool's ECOSYSTEM - [READY]

Steps25

Mapped10

Approximated16

Left as a note0

Added by MoveOver0

To configure0

Hand-offsremoves from 2. Funnel Kit's Ecosystem [INTRO TO ALL OTHER APPS BUT Funnel Kit] - v2 NEW TEMPSenrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Pro Plan's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Snapshot Pack's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Starter Plan's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Migration Service's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from (02) Audit Service Ecosystem v2 NEW TEMPSenrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from (02) Coaching Program Ecosystem - v2 NEW TEMPSenrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Bookkeeping Purchase In other Tool's ECOSYSTEM - [READY]

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
remove_from_workflow "Remove from Workflow - Migration Service'S ECOSYSTEM WORKFLOW (SELECT once it is done)"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "Remove from Audit Service Ecosystem"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "Remove from Coaching Program Ecosystem"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "REMOVE FROM THIS FLOW"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
if_else "yes"	a condition that never matches (branch on which trigger fired (no Votel equivalent))	Votel runs one trigger per workflow, so "which trigger fired" cannot be asked: put the branch's steps in the feeder workflow for that trigger, or remove the branch.

Map (as in HighLevel; nothing added)

2. Bookkeeping's Ecosystem [v2 NEW TEMPS]

Steps19

Mapped10

Approximated9

Left as a note0

Added by MoveOver0

To configure16

Hand-offsenrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHED

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
16 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

(00) Alex's Email Sequence - Ecosystem / (06) Migration Service Sequence - [PUBLISHED]

GHL migration: (00) Alex's Email Sequence - Ecosystem / (06) Migration Service Sequence - [PUBLISHED]Open agent ↗4

1. Migration - If purchase is done in ENTRY SEQUENCE 1 - [READY]

Steps5

Mapped3

Approximated3

Left as a note0

Added by MoveOver0

To configure0

Hand-offsremoves from 1. Migration Service Entry Emails - Sequence 1 [v2 NEW TEMPS]]enrolls 2. Migration Service's Ecosystem [v2 NEW TEMPS]

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
if_else "yes"	a condition that never matches (branch on which trigger fired (no Votel equivalent))	Votel runs one trigger per workflow, so "which trigger fired" cannot be asked: put the branch's steps in the feeder workflow for that trigger, or remove the branch.

Map (as in HighLevel; nothing added)

1. Migration Service Entry Emails - Sequence 1 [v2 NEW TEMPS]]

Steps14

Mapped8

Approximated6

Left as a note0

Added by MoveOver0

To configure4

Hand-offsenrolls 2. Migration Service's Ecosystem [v2 NEW TEMPS]

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
add_to_workflow "Add to Migration Service Ecosystem"	child workflow "2. Migration Service's Ecosystem [v2 NEW TEMPS]" resolved in a second pass	Check this step: child workflow "2. Migration Service's Ecosystem [v2 NEW TEMPS]" resolved in a second pass.
4 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Map (as in HighLevel; nothing added)

2. Migration Service Purchase In other Tool's ECOSYSTEM - [READY]

Steps25

Mapped10

Approximated16

Left as a note0

Added by MoveOver0

To configure0

Hand-offsremoves from 2. Snapshot Pack's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Pro Plan's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Bookkeeping's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Funnel Kit's Ecosystem [INTRO TO ALL OTHER APPS BUT Funnel Kit] - v2 NEW TEMPSenrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Starter Plan's Ecosystem [v2 NEW TEMPS]enrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from (02) Audit Service Ecosystem v2 NEW TEMPSenrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from (02) Coaching Program Ecosystem - v2 NEW TEMPSenrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHEDremoves from 2. Migration Service Purchase In other Tool's ECOSYSTEM - [READY]

Action needed: what changed, and what to do

Was (HighLevel)	Now (Votel)	What to do
remove_from_workflow "Remove from Audit Service Ecosystem"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "Remove from Coaching Program Ecosystem"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
remove_from_workflow "REMOVE FROM THIS FLOW"	target workflows resolved in a second pass	Check this step: target workflows resolved in a second pass.
if_else "yes"	a condition that never matches (branch on which trigger fired (no Votel equivalent))	Votel runs one trigger per workflow, so "which trigger fired" cannot be asked: put the branch's steps in the feeder workflow for that trigger, or remove the branch.

Map (as in HighLevel; nothing added)

2. Migration Service's Ecosystem [v2 NEW TEMPS]

manualModified for continuityOpen in Votel ↗

Steps21

Mapped10

Approximated9

Left as a note0

Added by MoveOver2

To configure17

Hand-offsenrolls (01) MONTHLY_NEWS - v2 Temps - PUBLISHED

Action needed: what changed, and what to do

Resume router added in front of the workflow: 1 resume point (s9_wait_2_days). A contact placed by MoveOver waits until its HighLevel due time, then continues at that step; every other contact skips the router.

Was (HighLevel)	Now (Votel)	What to do
17 items Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Maps: the HighLevel original (left) and as built in Votel, with the added block (right)

In HighLevel

In Votel router added

(00) Alex's Email Sequence - Ecosystem

GHL migration: (00) Alex's Email Sequence - EcosystemOpen agent ↗3

(00) Ecosystem Duplicate-Prevention Controller

Steps26

Mapped30

Approximated7

Left as a note0

Added by MoveOver0

To configure0

Hand-offsremoves from 2. Starter Plan's Ecosystem [v2 NEW TEMPS]removes from 2. Pro Plan's Ecosystem [v2 NEW TEMPS]removes from 2. Funnel Kit's Ecosystem [INTRO TO ALL OTHER APPS BUT Funnel Kit] - v2 NEW TEMPSremoves from 2. Bookkeeping's Ecosystem [v2 NEW TEMPS]removes from 2. Migration Service's Ecosystem [v2 NEW TEMPS]removes from 2. Snapshot Pack's Ecosystem [v2 NEW TEMPS]

Action needed: what changed, and what to do

Feeder workflow "Funnel Kit ecosystem completed" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Migration Service ecosystem completed" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Funnel Kit ecosystem started" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Bookkeeping ecosystem completed" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Pro Plan ecosystem started" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Snapshot Pack ecosystem started" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Snapshot Pack ecosystem completed" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Starter Plan ecosystem completed" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Bookkeeping ecosystem started" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Migration Service ecosystem started" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.
Feeder workflow "Pro Plan ecosystem completed" added for an extra HighLevel trigger: Votel runs one trigger per workflow, so this one hands its contacts to the main workflow.

Was (HighLevel)	Now (Votel)	What to do
if_else "Protect the first active ecosystem"	a condition that never matches (branch on which trigger fired (no Votel equivalent))	Votel runs one trigger per workflow, so "which trigger fired" cannot be asked: put the branch's steps in the feeder workflow for that trigger, or remove the branch.

Map (as in HighLevel; nothing added)

(01) MONTHLY_NEWS - v2 Temps - PUBLISHED

manualModified for continuityOpen in Votel ↗

Steps40

Mapped26

Approximated12

Left as a note0

Added by MoveOver2

To configure1

Action needed: what changed, and what to do

Resume router added in front of the workflow: 1 resume point (s1_wait_30_days). A contact placed by MoveOver waits until its HighLevel due time, then continues at that step; every other contact skips the router.

Was (HighLevel)	Now (Votel)	What to do
1 item Votel flagged on this workflow	created switched off; Votel lists the items on the workflow	Open the workflow in Votel and fill in what it flags (usually the email sender or a body left as a [placeholder]) before switching it on.

Maps: the HighLevel original (left) and as built in Votel, with the added block (right)

In HighLevel

In Votel router added

NEW - Growth Summit 3 emails Sequence. (Vibe Rendered temps)