Migrate from Makesbridge to HighLevel

Makesbridge Subscribers map directly to GoHighLevel Contacts. Standard fields (firstName, lastName, email, phone) map to their GoHighLevel equivalents. Custom field values migrate as GoHighLevel Custom Field entries attached to each Contact. The migration uses Makesbridge's individual subscriber GET endpoint in paginated batches; parallel sessions stay within Makesbridge's implicit rate limits to minimize wall-clock time. Duplicate detection runs on email address as the primary key.

Makesbridge Hot Lists are high-priority subscriber groups surfaced by the lead scoring engine. Each Hot List membership maps to a GoHighLevel Tag (e.g., 'Hot List - Q1 Priority') applied to the Contact record. We export all Hot List assignments at migration time and apply the corresponding Tags during the Contact load. Hot List priority order (if ranked) can be stored as a numeric custom field on the Contact for segmentation in GoHighLevel.

Makesbridge Lists are named audience groups. Each list maps to a GoHighLevel Tag named after the source List (e.g., 'List - Webinar Attendees'). A Contact can belong to multiple Makesbridge Lists and will receive multiple Tags at the destination. Tags are additive rather than exclusive, matching Makesbridge's list membership model.

Makesbridge Segments are dynamic rule-based subsets of Lists, but the rule definitions are not exportable via the API. We export the evaluated subscriber set at migration time and apply a descriptive Tag (e.g., 'Segment - High Intent Behavior') to each Contact in the set. The customer's admin recreates the segment logic as a GoHighLevel Filter or a Workflow enrollment condition post-migration using the exported Tag as a starting filter.

Makesbridge supports unlimited custom fields per subscriber. We retrieve the full custom field schema via the Makesbridge API, map field names to GoHighLevel Custom Field API names, and validate type compatibility before import. Text fields map to GoHighLevel text Custom Fields; numeric fields map to number Custom Fields; date fields map to date Custom Fields. Picklist or multi-select fields require a GoHighLevel Custom Field of type 'TEXT' with enumerated values, which we configure during schema setup. Field type mismatches (e.g., a Makesbridge free-text field receiving a value outside GoHighLevel's picklist) are logged and skipped with a reconciliation note rather than causing a silent coercion.

Makesbridge Campaigns (individual email sends or sequences) migrate as GoHighLevel Campaigns with campaign name, status, send date, subject line, and aggregate metrics (send count, open count, click count) preserved as custom fields. The email body HTML migrates as a GoHighLevel Template for reuse. Makesbridge's iframe-based Salesforce integration means any campaign performance data entered in Salesforce will not be present in Makesbridge; we work from Makesbridge as the system of record for campaign history.

Makesbridge email templates and drag-and-drop layouts export as HTML with embedded style blocks. We reconstruct these in GoHighLevel using the GoHighLevel Template editor or raw HTML import, mapping compatible blocks to GoHighLevel's template structure. Images hosted at external URLs are preserved as-is; any Makesbridge-hosted image assets are downloaded and re-uploaded to GoHighLevel's media library to avoid broken links.

Makesbridge Forms capture subscriber records and map field inputs to custom fields. We export form structure, field mappings, and the form HTML. Custom form fields must align with GoHighLevel Custom Field definitions; any field in a Makesbridge Form without a matching GoHighLevel Custom Field is created before migration begins to avoid silent drops on import.

Makesbridge computes lead scores per Subscriber based on behavior and demographic triggers. We export the current score value for each Subscriber as a numeric custom field (e.g., 'Lead Score') on the corresponding GoHighLevel Contact. GoHighLevel does not have a native lead scoring engine, so the migrated score values are static at migration time. The customer's admin can use GoHighLevel Workflows to build dynamic scoring logic or use the migrated values as-is for segmentation.

Makesbridge Workflows store automation sequences in a text-based format with no documented export schema. We extract step sequences, trigger conditions, delay settings, and action descriptions as structured text and deliver them as a written workflow inventory document. The customer's admin uses this document to rebuild each Workflow in GoHighLevel's visual Workflow builder. Workflows are not re-imported as code because Makesbridge's format is not compatible with GoHighLevel's automation engine.