Migrate from Makesbridge to Salesforce Sales Cloud

Makesbridge Subscribers map to Salesforce Lead or Contact depending on their lifecycle status and Hot List assignment. Subscribers with active engagement history and Hot List membership are mapped to Salesforce Contact tied to an Account. Subscribers with no engagement history or no Hot List assignment are mapped to Salesforce Lead. We preserve the original Makesbridge subscriber ID in a custom field mb_subscriber_id__c on both Lead and Contact for audit and cross-reference. All custom field values transfer to custom Lead or Contact fields of matching type.

Makesbridge Hot List memberships are high-priority designations surfaced by the lead scoring engine. We export each Hot List as a Salesforce Campaign and assign the corresponding Subscribers as Campaign Members at migration time. We also set a custom boolean field hot_list_member__c on the Contact record for quick filtering without joining to Campaign Members. If a subscriber belongs to multiple Hot Lists, they receive multiple Campaign Member records.

Makesbridge Lists are named audience groups that hold Subscribers. Each list maps to a Salesforce Campaign. The list name becomes the Campaign Name; the list description maps to Campaign Description. Subscribers assigned to the list become Campaign Members with Status = Sent to reflect the marketing context. List-level aggregate metrics (subscriber count, growth rate) are preserved as Campaign custom fields.

Makesbridge Segments are dynamic subsets of Lists based on behavior triggers or demographic rules. The segment rule definitions are not exportable via the Makesbridge API — only the evaluated subscriber set is available at migration time. We export the evaluated member set as a static Salesforce Campaign with all qualifying Subscribers assigned as Campaign Members. The customer receives a written segment logic document describing the rule conditions for manual recreation in Salesforce using Campaign criteria or Flow criteria.

Makesbridge Campaigns represent individual email sends or drip sequences. Campaign metadata (name, status, send date, subject line) maps directly to Salesforce Campaign fields. Campaign-level aggregate metrics — open rate, click rate, bounce rate, send count — migrate as custom fields on the Salesforce Campaign. The HTML content of each email is preserved and attached to the Campaign record as a ContentDocument for reference.

The HTML content of each Makesbridge email is exported and stored as a Salesforce ContentDocument linked to the corresponding Campaign via ContentDocumentLink. The customer's marketing team uses this content to reconstruct email templates in Salesforce using Salesforce Content Builder or a compatible email tool. Email template structure (subject lines, body blocks, images, links) is preserved verbatim.

Makesbridge computes lead scores per Subscriber based on behavior and demographic triggers. We export the current numeric score as a custom field mb_lead_score__c on the Salesforce Contact record. The scoring model itself — the weight rules and behavior triggers — is not exportable; we document the model as a written artifact so the customer's admin can reconstruct it as Salesforce Flow criteria or a custom scoring app from the AppExchange.

Makesbridge supports unlimited custom fields per Subscriber. We retrieve the full custom field schema via the API and map each field to a Salesforce custom field of the equivalent type (Text, Number, Date, Picklist, Checkbox, etc.). Field type differences — such as Makesbridge text fields that should map to Salesforce picklists — are resolved during scoping against the destination org's field type definitions. Custom field API names receive the mb_ prefix to avoid namespace collisions with existing Salesforce fields.

Makesbridge user accounts (Owner and User roles) are exported by email and mapped to Salesforce User records. We match by email address. Any Makesbridge Owner without a matching Salesforce User is held in a reconciliation queue until the customer's admin provisions the User in Salesforce. Role and permission metadata from Makesbridge is documented as a written artifact for the customer's admin to reapply using Salesforce Profiles and Permission Sets.

Makesbridge tags applied to Subscribers are exported as individual tag strings per record. Tags with fewer than 150 unique values per field migrate to a Salesforce multi-select picklist on Contact. Tags with high cardinality or those used for dynamic segmentation migrate to a custom text field mb_tags__c as a semicolon-delimited string for parsing in Salesforce Reports or Flow.

Makesbridge Forms capture new Subscriber records and map form fields to custom fields. We export the form structure and field mappings as a written artifact. Custom form fields are aligned with the destination custom field definitions created during schema design. We do not migrate Forms as a functional feature; the customer rebuilds forms using Salesforce Web-to-Lead, Experience Cloud, or a third-party form tool post-migration.

Makesbridge Workflows define automation sequences with step order, delays, and trigger conditions stored in a text-based format. We extract the step sequences and trigger logic as a structured written document with step descriptions, delay durations, condition branches, and action types listed in sequence. This document is delivered to the customer's admin for manual reconstruction in Salesforce Flow. Workflows cannot be re-imported directly into Salesforce. If the customer requires automated workflow recreation as a separate scope, our professional services team handles that as a distinct engagement.