Affiliate-only MoveOver guide

Run MoveOver. Watch it land in Votel.

A step-by-step walkthrough of what actually happens during a MoveOver run from GoHighLevel (GHL) to Votel: what you choose, what writes straight into Votel, what stays in your local archive, and how to check the result before you switch anything on. Access is available only to registered All Things Votel affiliates.

This is one run, not a two-step export and import. Sign in to HighLevel or your agency's white-label domain and switch into the sub-account you want to migrate before you open the extension: MoveOver reads whichever HighLevel location is open in the tab, so the account you see there is the account it migrates. With your own Votel API key connected, MoveOver writes the categories you choose straight into your Votel account while it runs, and keeps a local archive of everything it read either way. Votel shows what it can import, what it will change or skip, and the record count for each section before you switch anything on.

01
Chrome extension2 minutes, first run only

Open MoveOver and connect Votel

The first time you run a migration, add your own Votel API key and your MoveOver license key to the extension.

  1. Click the Chrome extensions icon, then open MoveOver.
  2. Paste your MoveOver license key if you have not already.
  3. In Votel, open Settings → API Keys, create a key, and paste it into MoveOver.
  4. Turn on Send contacts to Votel and Migrate automations to Votel so this run writes into your Votel account instead of only the archive.
Your Votel API key stays in your browser

MoveOver reads your HighLevel session and writes into Votel using your own key. Nothing passes through our servers.

02
Chrome extension2–5 minutes

Choose what to migrate and start the run

Select the categories and, where offered, individual records for this run.

  1. Review the categories in the extension against the 23 asset types MoveOver supports.
  2. Select the categories and records you want this run to include: a whole group, one type, or a single item.
  3. Click Export.
You pick what moves

Nothing you leave unchecked is sent to Votel. It stays out of both the archive and your Votel account.

03
From 15 minutes to 2 hours

Let it finish

Keep the tab open while MoveOver reads the selected records from HighLevel and writes them into Votel.

  1. Leave the HighLevel tab open until the run reports complete.
  2. For each category with a Votel toggle on, MoveOver writes it into your Votel account as it goes, switched off until you review it.
  3. Every category, whether or not its Votel toggle is on, is also saved into your local archive.
  4. When it finishes, MoveOver saves the migration report and the archive to your Downloads folder.
Websites and funnels take the longest

MoveOver opens each funnel and website page in its own background tab to capture it, which is normal and is why that category is usually the slowest part of the run.

04
ReportMost important check

Open your report before you touch anything in Votel

The report is where you decide what to activate: what went into Votel, what needs a decision, and what stayed in the archive.

A real MoveOver report Overview: stat cards for contacts, workflows, custom fields, tags and email templates, the Into Votel by type bars, and the Workflows at a glance tiles.
The Overview: what moved, and how many of each. From a real report; your own numbers will differ.
  1. Read the Overview: what went into Votel, by type.
  2. Open Workflows at a glance: how many arrived unchanged, how many were modified to keep contacts mid-sequence, and how many need a look.
  3. Read the Action items view for anything with no direct Votel equivalent: what it was, what it is now, and what to do.
One workflow card from the same report: the Action needed table above two maps, the GoHighLevel (GHL) original on the left and the Votel build on the right with the orange Added by MoveOver block.
Every workflow card opens that workflow directly in Votel.
See a real one

Every run gets a report like this, kept in your MoveOver library on this site. Open the full example report ↗

05
Votel

Switch on workflows and place contacts

Workflows arrive in Votel switched off. Review each one, switch it on when it is ready, then place contacts.

  1. Open a workflow from the report and compare the before-and-after map: the HighLevel original beside what MoveOver built in Votel.
  2. Resolve anything the report flagged as an action item for that workflow.
  3. Switch the workflow on in Votel.
  4. Press Place contacts once the workflows you want are switched on.
Contacts resume, they do not restart

A contact who was waiting for day 3 in HighLevel resumes at day 3 in Votel, not from the top of the sequence.

06
VotelProof

Verify what landed, or undo the run

Check the run against Votel directly, or remove exactly what it created.

  1. Compare the report's read-back numbers (tags, fields, templates, workflows, and a random sample of contacts) against your Votel account.
  2. New to this: send only your 500 most recent contacts first, check the result in Votel, then run the rest.
  3. If something needs to stop, stop the run at any point. What already landed in Votel stays; the rest goes into your archive.
  4. To reverse a completed run, type UNDO. MoveOver removes exactly what that run created, in the right order, and nothing that was already in Votel.
The report names the account

It states which Votel account it wrote to, so you can confirm the run reached the right place.

Migration complete

You moved over!

Your selected HighLevel records are in Votel. Keep the report and the archive as your record of the run.

Migration handoff check

Before calling the move complete, confirm the destination and keep your records.

1. SaveKeep the report and the local archive as your migration record.
2. ConfirmThe report names the Votel account it wrote to.
3. ActivateWorkflows you want are switched on and contacts are placed.
4. VerifySpot-check contacts and workflows in Votel, or use the report's own read-back numbers.
About this guide. This walkthrough describes MoveOver 3.32 and is updated when the product changes. Your own run's categories, warnings and record counts will differ from the example report shown here.