CRM migration
Field-level mapping, validation, and rollback between Marketing Star and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
Marketing Star
Source
Freshsales
Destination
Compatibility
4 of 8
objects map 1:1 between Marketing Star and Freshsales.
Complexity
BStandard
Timeline
2-3 weeks
Overview
Moving from Marketing Star to Freshsales is a structural migration from a marketing automation tool into a sales-focused CRM. Marketing Star organizes data around Contacts, Lists, and Campaigns with tier-based send and list caps; Freshsales uses the standard CRM model of Leads, Contacts, Accounts, and Deals with per-user licensing and AI-powered lead scoring. We resolve Marketing Star's required-email-or-phone validation at the profiling stage, chunk oversized lists against Freshsales' contact limits per tier, and map campaign membership to Freshsales' tag and territory system. Automation Workflows, SMS opt-in configurations, QR code triggers, and Landing Pages do not migrate as code; we deliver a written inventory of these for the customer's admin to rebuild in Freshsales Workflows and Freddy AI.
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 Marketing Star 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.
Marketing Star
Contact
Freshsales
Lead or Contact (split required)
1:manyMarketing Star Contacts map to either Freshsales Lead (for unqualified prospects) or Contact (for qualified buyers attached to an Account). We compute the split during scoping using any available engagement data: contacts with campaign open or click history become Leads; contacts with explicit sales qualification signals become Contacts with an Account. Marketing Star's email-or-mobile-phone requirement maps to Freshsales Contact's required email field and separate mobile phone property.
Marketing Star
List
Freshsales
Tag
lossyMarketing Star Lists map to Freshsales tags on Contact and Lead records. We export each list as a distinct tag value (e.g., list_name as tag) and apply bulk tag assignments during migration. For organizations with over 100 lists, we recommend grouping related lists under a tag prefix convention to avoid tag proliferation in Freshsales. Alternatively, if the customer uses Freshsales' territory or team assignment feature, we map list ownership to territory records.
Marketing Star
Campaign
Freshsales
Activity Timeline + Tag
1:manyMarketing Star Campaigns (email, SMS, QR code sends) do not have a direct Freshsales equivalent because Freshsales is a CRM, not a campaign automation platform. We map campaign history to the Contact or Lead activity timeline as a Campaign Activity record with the campaign name, send date, and outcome (delivered, opened, clicked, bounced). For organizations that rely on campaign attribution, we add a custom field campaign_source__c on Contact to preserve the originating Marketing Star campaign name.
Marketing Star
Form
Freshsales
Custom Fields on Contact or Lead
1:1Marketing Star Form submissions populate contact properties. We extract form field names and their corresponding values and map them to Freshsales custom fields on Contact or Lead. If the source form uses a field not present in Freshsales, we create the custom field before migration. Form submission timestamp migrates as a custom property (e.g., form_submitted_date__c) for attribution and lead scoring.
Marketing Star
SMS Contact
Freshsales
Contact Mobile Phone + Opt-in Fields
1:1Marketing Star SMS contacts are distinguished by mobile phone number and SMS opt-in status. We preserve SMS consent in a custom field sms_consent__c (boolean) and sms_opt_in_date__c (date) on Freshsales Contact. Freshsales Growth and above include built-in SMS capabilities via Freshcaller integration, which the customer can configure post-migration.
Marketing Star
QR Code
Freshsales
Custom Field or UTM Mapping
1:1Marketing Star QR codes track physical-to-digital attribution and link to Campaigns or Forms. We export QR code metadata (redirect URL, campaign association, creation date) and map it to Freshsales custom fields on Contact (utm_source__c, qr_code_id__c) to preserve attribution data. Full QR code management is a Marketing Star feature without a Freshsales native equivalent.
Marketing Star
Landing Page
Freshsales
Static Asset Export (URL Redirect Document)
1:1Landing pages are only available on Marketing Star Ultimate tier. We export page content as static HTML or a URL redirect configuration document. Freshsales does not host landing pages natively; we recommend the customer host redirects on their website or use a dedicated landing page tool (HubSpot, WordPress, or a Freshworks partner) post-migration. The migration deliverable includes a mapping of each Marketing Star landing page URL to its replacement URL.
Marketing Star
Automation Workflow
Freshsales
Workflow Documentation (not migrated)
lossyMarketing Star Automation Workflows (triggers, delays, CRM actions) do not migrate to Freshsales Workflows as code. We document every active workflow with its trigger, conditions, sequence of actions, and send-time logic, and deliver a written workflow inventory with recommended Freshsales Workflow equivalents. The customer's admin rebuilds them in Freshsales Workflow Builder (available from Growth plan) post-migration.
| Marketing Star | Freshsales | Compatibility | |
|---|---|---|---|
| Contact | Lead or Contact (split required)1:many | Fully supported | |
| List | Taglossy | Fully supported | |
| Campaign | Activity Timeline + Tag1:many | Fully supported | |
| Form | Custom Fields on Contact or Lead1:1 | Fully supported | |
| SMS Contact | Contact Mobile Phone + Opt-in Fields1:1 | Fully supported | |
| QR Code | Custom Field or UTM Mapping1:1 | Fully supported | |
| Landing Page | Static Asset Export (URL Redirect Document)1:1 | Fully supported | |
| Automation Workflow | Workflow Documentation (not migrated)lossy | Fully supported |
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.
Marketing Star gotchas
Import requires email or mobile phone on every record
List size caps hard-stop uploads
Landing pages not available below Ultimate tier
Annual billing discount not applied during migrations
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
Discovery and data profiling
We extract a full Marketing Star export including Contacts, Lists, Campaigns, Forms, SMS opt-in status, and QR code metadata. During profiling we identify records missing both email and mobile phone, list sizes that exceed Freshsales Growth tier limits, and custom form fields requiring Freshsales custom field creation. We also catalog active Automation Workflows and Landing Pages. The discovery output is a written migration scope document with record counts, a data quality report, and a list of custom field creations required in Freshsales.
Schema design and Freshsales configuration
We configure the destination Freshsales instance: custom fields on Contact and Lead for Marketing Star properties that have no direct equivalent (campaign_source__c, sms_consent__c, qr_code_id__c, form_submitted_date__c), tag groups for list membership translation, and any territory or team structure requested by the customer. We set up Freshsales Workflows prerequisites (Growth plan or above) and confirm the customer's plan supports the required contact volume. Schema configuration happens in the customer's Freshsales Sandbox or trial environment first.
Data cleansing and split logic
We cleanse the Marketing Star export: deduplicate contacts by email address, validate phone number formats, resolve records missing email (route to Lead or flag for enrichment), and apply the contact-to-Lead-or-Contact split logic based on engagement history. Lists are translated to tag assignments. Large lists exceeding the target Freshsales tier are chunked into multiple import batches or escalated to a higher tier recommendation. The cleansed export is validated against the source record count before import begins.
Test migration and reconciliation
We run a test migration using a 10-15% sample of production data into Freshsales. The customer reconciles record counts (Contacts imported, Leads imported, tags applied, custom fields populated), spot-checks 20-30 records field-by-field against the Marketing Star source, and approves the mapping before production migration begins. Any field mapping corrections, custom field additions, or split logic adjustments happen here.
Production migration in dependency order
We run production migration in record order: custom fields (deployed to Freshsales), then Contacts and Leads (with split logic applied), then tag assignments (bulk-applied after contact import), then campaign attribution data (custom fields on contacts), then Form submission records, then SMS consent fields. Each phase emits a reconciliation report showing source count, imported count, and skipped count with reasons.
Cutover, delta sync, and automation handoff
We freeze Marketing Star writes during cutover, run a final delta migration of any records created or modified during the migration window, then enable Freshsales as the system of record. We deliver the Automation Workflow inventory and Landing Page redirect map to the customer's admin team. We support a three-day hypercare window where we resolve any reconciliation issues. Workflow rebuild, SMS tool configuration, and landing page hosting are outside standard scope and require separate planning.
Platform deep dives
Marketing Star
Source
Strengths
Weaknesses
Freshsales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 3 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Marketing Star and Freshsales.
Object compatibility
3 of 8 objects need a mapping; the rest are 1:1.
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
Marketing Star: Not publicly documented.
Data volume sensitivity
Marketing Star 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 Marketing Star to Freshsales migration scoping. Not seeing yours? Book a call.
Walk through your Marketing Star 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 Marketing Star
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.