Migrate from Makesbridge to Pipedrive

Makesbridge Subscribers map directly to Pipedrive People. Standard fields (name, email, phone) map to Pipedrive's name, email, and phone fields. Custom field values migrate as Pipedrive custom fields on the Person record. The HubSpot-style Hot List priority flag (high-value prospect designation) migrates as a custom checkbox or picklist field on the Person. We paginate through Makesbridge's individual subscriber API calls and batch inserts into Pipedrive using the Burst API limit for the customer's plan tier (20-120 requests per 2-second window).

Makesbridge stores company data as subscriber properties rather than a distinct object. If a subscriber has a company name, domain, or address fields, we create a corresponding Pipedrive Organization record and link the Person to it via the org_id field. Company properties (industry, size, revenue tier) map to Organization custom fields. Organizations are created before Person inserts to satisfy the lookup dependency.

Makesbridge Lists are named audience groups that can be applied to multiple Subscribers. We export list memberships and create corresponding Pipedrive Tags on each Person record. Tags are created dynamically during migration so that a Person added to three Lists in Makesbridge appears with three Tags in Pipedrive. Tag names preserve the Makesbridge list name exactly.

Makesbridge Segments are defined by dynamic rules (behavior triggers, field conditions) that are not exportable via the API. We export the evaluated subscriber set at migration time as a static list snapshot. Each subscriber in the evaluated set receives a Tag matching the segment name. The customer should plan to recreate segment logic in Pipedrive using filter views or CRM-native segmentation features post-migration.

Makesbridge Campaign metadata (name, send date, subject line, open/send metrics) migrates as a Pipedrive Campaign record. The campaign-level aggregate metrics (open rate, click rate, send count) are stored as notes on the campaign or as custom fields on the campaign. Email HTML content is preserved as an attachment on the campaign record. Template assignments are documented in the campaign note for manual reconstruction if the customer wants to reuse email content in Pipedrive-connected tools (such as email sequences via a Sales Engagement add-on).

Makesbridge stores automation workflows in a text-based format without a documented export schema. We extract step sequences, delay settings, and trigger conditions as structured text. Workflows cannot be re-imported into Pipedrive Automations because the logic models differ. We deliver a written inventory document for each active Workflow with trigger type, conditions, actions, and a recommended Pipedrive Automation equivalent. The customer's Pipedrive admin or a consultant rebuilds them post-migration. This document is included in standard migration scope.

Makesbridge Hot Lists are high-priority subscriber groups surfaced by the lead scoring engine. We export Hot List membership and set a custom field on each Person record (a checkbox labeled Hot_List_Member__c or a picklist labeled Lead_Priority__c with values matching the Hot List names). The original lead score value migrates as a separate custom numeric field (Lead_Score__c) on the Person record for reporting and segmentation in Pipedrive.

Makesbridge supports unlimited custom fields per Subscriber. We retrieve the full custom field schema via the API and map field names and types to Pipedrive custom fields. Text fields map to Pipedrive text fields, numeric fields to number fields, date fields to date fields, and picklist values to Pipedrive picklists. Field type differences (e.g., a Makesbridge free-text field containing comma-separated values that should map to a Pipedrive multi-select picklist) are resolved during scoping with the customer's data governance lead.

Makesbridge computes lead scores per Subscriber based on behavior and demographic triggers. We export the current score value and write it to a custom numeric field (Lead_Score__c) on the corresponding Pipedrive Person record. Pipedrive does not have a native lead scoring engine; the score is preserved as a data point for the customer's sales team to use in manual prioritization or in Pipedrive Automations with condition-based triggers (e.g., 'if Lead_Score__c > 80, assign to senior rep').

Tags applied to Makesbridge Subscribers are exported as individual tag strings per contact and mapped to Pipedrive Tags on the Person record. Tag names are preserved exactly. If a subscriber has multiple Tags, each becomes a separate Pipedrive Tag on that Person. Tags serve as the primary audience segmentation mechanism in Pipedrive for campaigns and filters.

Makesbridge tracks email opens, clicks, and bounce events internally, but these granular activity records are not accessible via the public API. Only campaign-level aggregate metrics (open rate, click rate, bounce rate, send count) are available. We preserve these aggregates as custom fields on the associated Pipedrive Campaign record and as a summary note on each Person who received a campaign email. Individual open/click timelines cannot be reconstructed at the contact level.

Makesbridge user accounts (Owner and User roles) can be exported and mapped to Pipedrive User records. We match by email address. Admin and editor role designations are preserved as a custom text property on the Person record for reassignment reference. User provisioning in Pipedrive is a manual step coordinated with the customer's admin before migration begins.