CRM migration
Field-level mapping, validation, and rollback between Spotler Mail+ and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
Spotler Mail+
Source
Freshsales
Destination
Compatibility
6 of 8
objects map 1:1 between Spotler Mail+ and Freshsales.
Complexity
BStandard
Timeline
3-5 weeks
Overview
Moving from Spotler Mail+ to Freshsales is a structural shift from an email-first marketing platform to a unified sales CRM. Spotler Mail+ stores records as Contacts with Tags, Scores, and field-level custom data across text, numeric, currency, list, and date types; Freshsales uses the standard CRM model of Contacts linked to Accounts with Deals for pipeline management and Freddy AI for lead scoring. We migrate contact records with all typed custom fields resolved, subscription status mapped to Freshsales contact properties, and segmentation membership stored as label fields. Mailing interaction history (opens, clicks, delivery stats) is constrained by Spotler's 24-month anonymization policy; we scope and export within that window only. Workflows, automation sequences, landing pages, and form logic do not migrate as code; we deliver a written inventory of these for the customer's admin to rebuild in Freshsales or the broader Freshworks suite.
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 Spotler Mail+ 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.
Spotler Mail+
Contact
Freshsales
Contact
1:1Spotler Mail+ Contacts map directly to Freshsales Contacts. Standard fields (first name, last name, email, phone, address) map 1:1. Spotler custom fields of type text, numeric, currency, and date migrate to Freshsales custom fields of equivalent type. We validate field type compatibility during scoping and flag list fields and permission fields for transformation since these require picklist or multi-select configuration in Freshsales before import.
Spotler Mail+
Tag
Freshsales
Contact (label field)
1:1Spotler Mail+ tags stored as contact-level attributes map 1:1 to Freshsales contact label fields or contact custom text fields. We extract tag names as pipe-delimited values or create individual label assignments depending on the customer's segmentation preference. Tags used for behavioral classification migrate as custom multi-select picklist fields in Freshsales.
Spotler Mail+
Score
Freshsales
Contact (numeric custom field)
1:1Lead scoring values in Spotler Mail+ are numeric contact properties. We create a numeric custom field in Freshsales (e.g., spotler_score__c) and migrate the raw score value. Note that Freshsales Freddy AI will recalculate scores based on activity within Freshsales; the Spotler score is preserved as a baseline for comparison during the transition period.
Spotler Mail+
Audience/Segmentation
Freshsales
Contact (filter view or tag)
1:manySpotler Mail+ segmentation rules (built from selections, exclusions, refinements, behavioral data) cannot be exported as logic. We extract the resulting contact sets from each active segment and store segment membership as label fields or custom picklist values on each Contact in Freshsales. The customer's admin rebuilds segment logic as Freshsales filter views or contact lists post-migration.
Spotler Mail+
Mailing (send history)
Freshsales
Task or Note (activity record)
1:1Spotler Mail+ mailing subject lines, send dates, and recipient counts migrate as Task records on each Contact representing the send event. Opens, clicks, and delivery stats migrate within the 24-month window only; records older than 24 months are unavailable from Spotler regardless of export method. We notify the customer upfront if their requested scope exceeds this window.
Spotler Mail+
Form Request
Freshsales
Note or custom field on Contact
lossyForm submissions in Spotler Mail+ export as flat records rather than relational question-response data. We denormalize form responses into contact custom fields or related Note records depending on field count and structure. Survey closure rules and quota-triggered logic do not export; these are documented for the customer to recreate as Freshsales web forms or Freshdesk custom fields if needed.
Spotler Mail+
Template
Freshsales
HTML/CSS asset package
1:1Email templates from Spotler Mail+ are platform-native assets with drag-and-drop layout that do not export as portable format. We extract template content, embedded images, and inline styles as HTML/CSS asset packages and deliver them alongside the contact migration. The customer's admin reassembles templates in Freshsales email editor or a third-party tool of their choice.
Spotler Mail+
Workflow Automation
Freshsales
No transfer (documented for rebuild)
1:1Spotler Mail+ automated campaign logic (triggers, drip sequences, behavioral actions) is platform-native and cannot be exported as executable rules. We do not migrate Workflows as code. We deliver a written inventory of each active automation with its trigger, conditions, actions, and recommended Freshsales workflow equivalent. The customer's admin or a Freshworks partner rebuilds them post-migration.
| Spotler Mail+ | Freshsales | Compatibility | |
|---|---|---|---|
| Contact | Contact1:1 | Fully supported | |
| Tag | Contact (label field)1:1 | Fully supported | |
| Score | Contact (numeric custom field)1:1 | Fully supported | |
| Audience/Segmentation | Contact (filter view or tag)1:many | Fully supported | |
| Mailing (send history) | Task or Note (activity record)1:1 | Fully supported | |
| Form Request | Note or custom field on Contactlossy | Fully supported | |
| Template | HTML/CSS asset package1:1 | Fully supported | |
| Workflow Automation | No transfer (documented for rebuild)1:1 | 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.
Spotler Mail+ gotchas
Mailing interaction data is purged after 24 months
Import file structure is strict and column-name-sensitive
Form and survey results export as flat records, not relational data
Multi-brand capability is tier-gated to MailPro
API does not expose a bulk export endpoint for contact history
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 audit
We audit the source Spotler Mail+ portal for contact volume, active custom fields and their types (text, numeric, currency, list, date, permission), active tags and scoring values, audience segment definitions and member counts, mailing campaign count and send history window, form submissions and survey responses, and active workflow count. We confirm the customer's Spotler tier (Mail+ or MailPro) since multi-brand support and advanced approval workflows are gated to MailPro and affect what object classes are available for export.
Field mapping and Freshsales schema preparation
We build the field mapping matrix mapping each Spotler custom field to a typed Freshsales contact field. List fields and permission fields are flagged for picklist configuration or transformation. We create the destination custom fields in Freshsales before any data import. We also create the spotler_score__c, spotler_tags__c, and segment membership fields on Contact to receive migrated behavioral data. If the customer uses Freshsales Enterprise, we configure custom objects for any Spotler data that does not fit the standard Contact schema.
Pagination scripting and API extraction
We implement a scripted extraction using Spotler Mail+'s REST API with cursor-based pagination to pull all contact records including tags, scores, and custom field values. The script applies exponential backoff on rate-limit responses and checkpoints progress to handle large databases without data loss. We extract segment membership by querying each active segment's contact set. We run the mailing history extraction scoped to the 24-month window only and confirm record counts with the customer before proceeding.
Contact migration with dedupe validation
We import contacts into Freshsales using the REST API with batch chunking. Email address is used as the primary dedupe key to prevent duplicate contacts. Tags are mapped to Freshsales label fields or custom multi-select picklist values. Scores are written to the spotler_score__c numeric field. Segment membership is written to segment-specific custom fields or label fields. Permission and consent fields map to Freshsales HasOptedOutOfEmail and custom GDPR fields. We run a reconciliation count comparing Spotler contact total to Freshsales contact total before proceeding.
Engagement history and form data import
We import mailing send history as Task records on each Contact representing the send event. Within the 24-month window, open and click counts migrate as custom fields on the Task. Form submission data denormalizes into contact custom fields or related Note records. We validate that form field names map to Freshsales field names and flag any unmapped fields for customer review. Survey closure rules and behavioral automation triggers do not migrate and are documented for rebuild.
Cutover, validation, and automation rebuild handoff
We freeze Spotler Mail+ writes during cutover, run a final delta migration of any records modified during the migration window, then enable Freshsales as the system of record. We deliver the written inventory of Spotler Mail+ workflow automations, landing pages, and template assets with recommended Freshsales equivalents. We support a one-week hypercare window for reconciliation issues. We do not rebuild Spotler workflows as Freshsales workflows inside the migration scope; that is a separate engagement or an internal admin task.
Platform deep dives
Spotler Mail+
Source
Strengths
Weaknesses
Freshsales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 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 Spotler Mail+ and Freshsales.
Object compatibility
2 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
Spotler Mail+: Not publicly documented in the available API documentation.
Data volume sensitivity
Spotler Mail+ 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 Spotler Mail+ to Freshsales migration scoping. Not seeing yours? Book a call.
Walk through your Spotler Mail+ 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 Spotler Mail+
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.
