CRM migration
Field-level mapping, validation, and rollback between Makesbridge and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
Makesbridge
Source
Freshsales
Destination
Compatibility
5 of 9
objects map 1:1 between Makesbridge and Freshsales.
Complexity
CModerate
Timeline
2-4 weeks
Overview
Moving from Makesbridge to Freshsales is a migration from a marketing automation platform to a sales CRM. Makesbridge organizes data around Subscribers, Lists, and Campaigns with a text-based workflow builder and iframe Salesforce integration. Freshsales is a sales CRM from Freshworks built around Contacts, Accounts, Deals, and Leads with Freddy AI for contact scoring and built-in phone and email. The structural difference is that Makesbridge holds all contacts in a single Subscriber object, while Freshsales splits prospects into Leads and converts them to Contacts attached to Accounts. We resolve that split during scoping using available contact data fields, preserve Makesbridge Hot List memberships as priority flags on Freshsales contacts, and map unlimited custom fields to Freshsales custom fields. We cannot migrate individual email opens, clicks, or bounce events because Makesbridge does not expose granular activity via its public API — only campaign-level aggregates are available. Workflows and automation sequences do not migrate as code; we deliver a documented artifact of every workflow step for the customer's admin to rebuild in Freshsales.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Makesbridge object lands in Freshsales, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Makesbridge
Subscriber
Freshsales
Lead and Contact (split by email domain and field completeness)
1:manyMakesbridge Subscribers map to Freshsales Lead for prospects without an associated Account and to Contact for qualified contacts. We evaluate each Subscriber at migration time using the presence of company name, deal context, or Hot List flag to determine placement. Subscribers with a company name and any deal-related data map to a Contact under a parent Account; all others map to Lead. The original Makesbridge subscriber ID is preserved in a custom field mb_subscriber_id__c on both Lead and Contact for audit.
Makesbridge
Lists
Freshsales
Audience (or Tags on Contact)
lossyMakesbridge Lists are named audience groups that hold subscriber memberships. We export list names and member email addresses, then create Freshsales Audiences from each list or apply list names as Tags on the migrated Contact or Lead records. The choice between Audience and Tags is made during scoping based on how the customer uses list segmentation in Makesbridge. Hot List is handled separately as a priority flag.
Makesbridge
Hot Lists
Freshsales
Contact custom field (priority_flag)
1:1Makesbridge Hot Lists are high-priority subscriber groups surfaced by the lead scoring engine. We export Hot List memberships and write a mb_hot_list__c custom field on the Contact object with a boolean or multi-select value indicating the Hot List assignment. If the customer uses multiple Hot Lists, we map each as a separate multi-select option value on the custom field.
Makesbridge
Custom Fields
Freshsales
Custom fields on Lead, Contact, Account, Deal
lossyMakesbridge supports unlimited custom fields per Subscriber. We retrieve the full custom field schema via the Makesbridge API, retrieve the field types and values for each Subscriber, then pre-create Freshsales custom fields of matching type before migration. Text fields map to Freshsales text, numeric scores to number fields, dates to date fields, and picklist values to Freshsales picklist. Custom field names are normalized to Freshsales API naming conventions. Each custom field requires individual Freshsales admin configuration on the target object.
Makesbridge
Tags
Freshsales
Tags on Contact or Lead
1:1Makesbridge tags applied to subscribers are exported as individual tag strings per contact record. We map these directly to Freshsales Tags, which are a native label feature on Contact and Lead objects. Tags preserve the segmentation logic applied in Makesbridge for use in Freshsales views and filters.
Makesbridge
Campaigns
Freshsales
Campaigns with email template HTML
1:1Makesbridge Campaigns are email sends or drip sequences. We export campaign metadata (name, status, send dates, subject line) and the HTML content of each email. Campaign-level aggregate metrics (open rate, click rate, send count) are preserved as custom fields on the Freshsales Campaign record. The email HTML is provided as a separate migration artifact for the customer's team to recreate as Freshsales email templates. Template assignment logic is documented for manual reconstruction.
Makesbridge
Lead Scores
Freshsales
Custom numeric field on Contact
1:1Makesbridge lead scoring values are computed per Subscriber based on behavior and data triggers. We export the current score value and write it to a custom numeric field mb_lead_score__c on the migrated Contact or Lead. Note that Freshsales' Freddy AI contact scoring is trained from scratch on migrated contact data and does not carry over any Makesbridge scoring model; the mb_lead_score__c field preserves the historical score as a reference point.
Makesbridge
Users
Freshsales
User (reconciliation required)
1:1Makesbridge user accounts (Owner and User role assignments) are exported and matched by email to Freshsales User records. Any Makesbridge user without a matching Freshsales User is flagged in a reconciliation queue for the customer's admin to provision before the Contact and Deal migration resumes. Owner assignments on Deals and Contacts are resolved via this lookup at migration time.
Makesbridge
Workflows
Freshsales
Workflow documentation artifact (no automated migration)
lossyMakesbridge workflows are stored in a text-based format without a documented export schema for automation logic. We extract step sequences, delay settings, trigger conditions, and action types as structured text and deliver a written migration artifact documenting every active workflow for manual reconstruction in Freshsales. The customer's Freshsales admin rebuilds these as visual workflows using the documented sequence as a reference. This object is marked as configuration-only because the automation itself cannot be re-imported into Freshsales.
| Makesbridge | Freshsales | Compatibility | |
|---|---|---|---|
| Subscriber | Lead and Contact (split by email domain and field completeness)1:many | Fully supported | |
| Lists | Audience (or Tags on Contact)lossy | Fully supported | |
| Hot Lists | Contact custom field (priority_flag)1:1 | Fully supported | |
| Custom Fields | Custom fields on Lead, Contact, Account, Deallossy | Mapping required | |
| Tags | Tags on Contact or Lead1:1 | Fully supported | |
| Campaigns | Campaigns with email template HTML1:1 | Mapping required | |
| Lead Scores | Custom numeric field on Contact1:1 | Mapping required | |
| Users | User (reconciliation required)1:1 | Mapping required | |
| Workflows | Workflow documentation artifact (no automated migration)lossy | Mapping required |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Makesbridge gotchas
Iframe-based Salesforce integration causes field sync misalignment
No bulk export API — large subscriber lists take multiple sessions
Workflows are not programmatically portable
Activity history is not accessible via API
Segment logic cannot be exported — only evaluated member sets
Freshsales gotchas
Freddy AI is Pro-tier only despite heavy marketing
Post-migration emails and sequences are disabled
Bot session credits are a one-time 500-session allocation
Phone credits charged per minute with no cap
File storage limits scale with plan tier
Pair-specific challenges
Migration approach
Scoping and schema design
We audit the Makesbridge account for subscriber volume, custom field schema (field names, types, and values), list structure and count, Hot List assignments, active campaign metadata, and workflow count. We pair this with a Freshsales readiness assessment: which plan tier (Free, Growth, Pro, Enterprise) supports the target data model, which custom fields need to be pre-created, and whether Leads should be created as a pre-stage or contacts should land directly. The scoping output is a written migration scope document with the object mapping, custom field list, and Freshsales plan recommendation.
Custom field provisioning in Freshsales
Before any data is extracted from Makesbridge, we create the custom fields in Freshsales that correspond to Makesbridge custom fields. Each Makesbridge custom field is evaluated for type compatibility with Freshsales (text, number, date, picklist, multi-select, checkbox, phone, URL). Fields are created on the target object (Lead, Contact, Account, or Deal) based on the scoping decision. This step must complete before subscriber export begins because Freshsales requires field IDs for mapping during the data load phase.
Makesbridge data extraction and transformation
We extract subscriber records from Makesbridge via individual API calls, paginating through the full subscriber set. Custom field values are extracted alongside standard fields. List memberships are captured as a separate export mapping subscriber email to list name. Hot List assignments are captured with the subscriber email and Hot List name. Campaign metadata and email HTML are extracted for each active and historical campaign. Workflows are documented as text artifacts. Activity aggregates (campaign-level open rates, click rates) are captured. All extracts are written to a staging area for transformation before load.
Data transformation and split logic application
We apply the split logic determined during scoping: subscribers with company name and deal context become Contacts under parent Accounts; remaining subscribers become Leads. Makesbridge lead scores are written to mb_lead_score__c. Hot List assignments are resolved to the mb_hot_list__c custom field. Tag strings are mapped to Freshsales Tags. Email address is used as the primary dedupe key across all records. Any subscriber with a duplicate email is flagged in a reconciliation report for the customer to resolve before load.
Staged migration and reconciliation into Freshsales Sandbox
We run a full migration into a Freshsales Sandbox using production-equivalent data volume. The customer reconciles record counts (Leads in, Contacts in, Accounts in, Deals in), spot-checks 25-50 records against Makesbridge source data, and validates custom field values and Hot List flags. Owner assignments are reconciled: Makesbridge owners without a matching Freshsales User are flagged for the customer to provision. The customer signs off the sandbox migration before production migration begins.
Production migration, cutover, and handoff
We run the production migration in dependency order: Accounts first (from Makesbridge company names where present), then Leads and Contacts with AccountId resolved, Deals with OwnerId and ContactId resolved, Tags, and Hot List flags. We run a delta pass to capture any records modified in Makesbridge during the migration window. We freeze Makesbridge writes at cutover and enable Freshsales as the system of record. We deliver the workflow documentation artifact and the campaign email HTML artifact to the customer. We support a five-day hypercare window for reconciliation issues. Automation rebuild in Freshsales is outside standard scope.
Platform deep dives
Makesbridge
Source
Strengths
Weaknesses
Freshsales
Destination
Strengths
Weaknesses
Complexity grading
Moderate CRM migration. 1 of 8 objects need a manual workaround.
Overall complexity
Moderate migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Makesbridge and Freshsales.
Object compatibility
1 of 8 objects need a manual workaround.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Makesbridge: Not publicly documented. Makesbridge does not publish rate-limit ceilings on its developer pages..
Data volume sensitivity
Makesbridge doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Makesbridge to Freshsales migration scoping. Not seeing yours? Book a call.
Walk through your Makesbridge to Freshsales migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Makesbridge
Other ways to arrive at Freshsales
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.