Consolidating Two GoHighLevel Accounts: Calendars by Lead Source and 259 Migrated Contacts
By Alex Regueiro · October 25, 2026 · 5 min read
When contacts live in two GoHighLevel accounts, no automation can see the whole picture. That was the position of a short-term-rental management and acquisitions owner who had a legacy account, a primary account, and leads arriving from different platforms in different shapes.
60-second check
Take the 2-minute AI readiness survey →
Talk it through
Book a call with the Reshape team →
We consolidated the setup on a review call. The steps below apply to real estate agents and investors who add a second account or a second lead source and end up splitting their data across both.
The situation
Contacts were spread across the legacy GoHighLevel account and the primary one. Leads also came in from more than one platform, and each platform described a lead differently. One captured an investment range, another a minimum, so the same kind of person looked different depending on where they came from.
Two smaller problems sat on top. Emails sent from GoHighLevel lacked the owner's signature, and the quality of a new lead was unclear.
What was broken
Workflows only act on the contacts inside the account they run in, so a split database meant any automation we built would miss part of the list. Mismatched fields meant a lead's key numbers could land in the wrong place or nowhere. And an email with no signature reads less like a message from the owner.
What we built
The work covered five pieces.
- Calendars cloned once per lead source, all sharing the same availability, with Google Calendar and Calendly connected. Each source gets its own scheduling link, and the owner still has one set of open hours.
- Contact migration: 259 contacts exported from the legacy account and imported into the primary one, so workflows and automations run against a single contact database.
- Notification preferences, Gmail sync and the email signature set up inside GoHighLevel, so outbound email looks like it came from the owner.
- Custom contact fields built from the structure of each lead source's CSV export.
- Voicemail audio edited into an intro video for the automated touchpoint sequence.
What changed
This call did not report a result, and it was setup work, so there was nothing to measure yet. What differs is the structure underneath. There is one contact database in place of two. Each lead source has its own booking link without splitting the owner's availability. Each source's fields match what that platform actually sends.
Before you merge accounts
This section is advice for your own setup. Export a sample from every lead source first and read the column headers before you design fields, because the names on the forms are rarely the names in the data. Count contacts before and after the import so you know nothing was dropped. And give every calendar the same availability source, so you never double-book yourself.
Keep a short written list of which fields mean the same thing across your lead sources, so the next person who edits a form does not quietly break the mapping.
Frequently asked questions
Should I merge a legacy GoHighLevel account into my main one?
If automations need to see every contact, yes. Workflows only act on contacts in their own account, so a second account hides part of your list. Export the old contacts, import them into the primary account, and confirm the counts match before you retire anything.
Why clone calendars by lead source?
A cloned calendar per source gives each source its own scheduling link while every link draws from one availability. You can tailor the link and the booking page to where the lead came from without maintaining several separate schedules.
How do you set up custom fields for lead sources that capture different data?
Start from the real exports, not the form screens. Read each CSV, list what each source collects, such as an investment range or a minimum, and create contact fields that match. Then map each source's columns to those fields so the data lands consistently.
Why does the email signature matter in GoHighLevel?
Email sent from the CRM without a signature looks automated and can undercut the personal tone of an owner-led business. Setting the signature in the profile settings makes every outbound message carry the same sign-off as email sent from a regular inbox.
If your contacts, calendars and lead sources do not line up in one place, book a 30-minute AI follow-up and reporting audit. We look at how your accounts are laid out and show you where data is splitting.