Migrate from Makesbridge to Microsoft Dynamics 365 Sales

Makesbridge Subscribers map to Salesforce Lead or Contact in Dynamics 365. Subscribers with a lifecycle stage indicating a qualified prospect map to Contact attached to an Account; all others map to Lead. We determine the split at migration time using the subscriber's lifecycle stage and subscription status, preserve the original lifecycle stage in a custom field on both Lead and Contact, and create the Account record before Contact import to satisfy the lookup dependency. Subscribers without an email address are flagged for manual review because Dynamics 365 requires an email for Lead creation.

Makesbridge Lists are named audience groups. We export the list name and the subscriber membership set at migration time. Each list maps to a Dynamics 365 custom field on the Lead or Contact (a multi-select picklist or text field holding the list names) or to a Marketing Audience if the destination org includes Dynamics 365 Marketing. The customer selects the target strategy during scoping. List names with special characters are normalized to alphanumeric and underscore for the Dynamics 365 API field name.

Makesbridge Segments are dynamic subscriber subsets based on behavior or demographic rules. The segment rule definitions are not accessible via the Makesbridge API. We export the evaluated subscriber set as a static list snapshot at migration time and map it as a custom field value or a static Marketing Audience in Dynamics 365. The customer should plan to recreate the dynamic segment logic as a Dynamics 365 Marketing segment or a Power Automate workflow post-migration using the exported subscriber data as a reference.

Makesbridge Campaigns (email sends or sequences) map to Dynamics 365 Campaign. Campaign name, subject line, send date, and campaign status migrate as standard Campaign fields. Campaign-level aggregate metrics (open rate, click rate, send count, bounce count) migrate as custom fields on the Campaign record. The HTML email content for each campaign is preserved as an attachment or content document for reference. Email template assignments are noted separately for reconstruction in Dynamics 365 Marketing or a third-party email tool.

Makesbridge workflows are stored in a text-based format without a documented export schema for the automation logic itself. We extract the step sequence, trigger conditions, delay settings, and action descriptions as a structured migration artifact document. This document is delivered to the customer's admin team as the basis for manual reconstruction in Dynamics 365 using Power Automate or Microsoft Dynamics 365 Sales 's built-in process automation tools. Workflows are not migrated as executable code.

Hot Lists in Makesbridge are high-priority subscriber groups surfaced by the lead scoring engine. We export Hot List memberships and map them to a custom field on the Lead or Contact record (a text or picklist field indicating the Hot List name and priority level). If multiple Hot Lists exist, the highest priority designation takes precedence. The customer can convert this to a Lead Score field or a priority flag in Dynamics 365 during post-migration configuration.

Makesbridge supports unlimited custom fields per subscriber. We retrieve the full custom field schema via the API, including field name, type, and any list or validation constraints. Each Makesbridge custom field is mapped to a Dynamics 365 custom field with the closest matching type (text fields map to nvarchar, numeric fields to decimal or integer, date fields to datetime). Picklist values are mapped to Dynamics 365 picklist OptionSet values. Field type differences (e.g., a Makesbridge rich-text field mapping to a Dynamics 365 ntext field) are documented in the schema mapping deliverable for admin review before import.

Lead scoring values computed by Makesbridge migrate as a custom numeric field (decimal or integer) on the Lead or Contact record in Dynamics 365. The field is named hs_lead_score__c to indicate the source system. Historical score snapshots are migrated as-is; ongoing score updates require a Power Automate flow or a dedicated scoring tool post-migration to maintain real-time scoring behavior.

Makesbridge does not store file attachments as standalone objects. Any file referenced in a campaign is a URL link to an external source. We preserve these URLs as custom text fields on the related Campaign record in Dynamics 365. File attachment objects themselves cannot be migrated. The customer should verify that the external URLs remain accessible post-migration.

Makesbridge user accounts (Owner and User roles) can be exported and mapped to the Dynamics 365 User object by email match. Admin and editor role assignments from Makesbridge are preserved as a custom property on the User record for reassignment planning. Any Makesbridge Owner without a matching Dynamics 365 User is held in a reconciliation queue for the customer's admin to provision before record import resumes.