Migrate from Regal.io to HighLevel

Regal Contacts map directly to GoHighLevel Contacts. The primary mapping key is phone number (regal's required field) to GoHighLevel's phone field. We validate phone number presence in the source export: any Regal Contact without a phone number will migrate as a GoHighLevel Contact but will not trigger SMS or calling automations. Standard attributes (name, email, address) map to GoHighLevel's native Contact fields; custom attributes map to GoHighLevel Custom Fields that we provision before import.

Regal's tenant-specific custom contact attributes (profile fields, segmentation properties) map to GoHighLevel Custom Fields on the Contact object. We extract the full attribute schema from Regal's API during discovery, provision matching custom fields in GoHighLevel (text, number, date, dropdown, or checkbox type) before migration, and map values field-by-field. Attributes that drive Journey trigger conditions are flagged as high-priority for admin to recreate in GoHighLevel Workflows post-migration.

Regal Events (behavioral interactions: calls made, SMS sent, email opened, Journey steps completed) are not native GoHighLevel objects. We flatten the event history and reassociate it with the migrated Contact as a combination of GoHighLevel Activity records (for calls and tasks) and Notes (for behavioral log entries). Each event type from Regal maps to a corresponding GoHighLevel activity type, with the original timestamp and event properties preserved in the note body or custom fields.

Regal Campaigns (outbound programs with list selection, cadence, and goal metrics) map to GoHighLevel Campaigns. Campaign membership (which Contacts were assigned to which Campaign) migrates via GoHighLevel's Campaign Members. Note that cadence logic and list-refresh rules are platform-specific and will not carry over; we document the original cadence parameters and goal metrics so the admin can recreate the schedule in GoHighLevel's Workflow or Opportunity triggering logic.

Call transcripts and recordings export from Regal's media storage as structured text and audio files. Transcripts migrate as GoHighLevel Notes attached to the Contact record with a custom field recording_url__c pointing to the audio file URL (if available). Audio file availability depends on Regal's retention policy at time of export. We flag any transcripts that cannot be retrieved due to retention expiry before migration begins.

SMS conversation threads reassociate with the migrated GoHighLevel Contact using the phone number as the linking key. Thread continuity in GoHighLevel relies on the conversation being attached to the correct Contact ID; we resolve this during the contact import phase. Email threads similarly migrate as Conversation records linked to the Contact.

Regal's CNAM (Caller ID Name) registration per campaign is exported as carrier configuration details. GoHighLevel supports branded caller ID through its built-in phone number provisioning, but CNAM registration must be reconfigured in GoHighLevel's account settings post-migration. We deliver a document listing each registered carrier, number range, and CNAM assignment for the admin to re-enter.

Regal's live integrations with Segment, HubSpot, Salesforce, Braze, and Iterable define which contacts are synced and how. We document active integration endpoints, sync direction, and field mapping during discovery so the migration plan includes re-establishing equivalent integrations in GoHighLevel (via Zapier, native integrations, or GoHighLevel's API). The CDP-native sync model from Regal does not have a direct GoHighLevel equivalent and requires manual reconfiguration.