CRM migration
Field-level mapping, validation, and rollback between Spotler CRM and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
Spotler CRM
Source
Freshsales
Destination
Compatibility
9 of 11
objects map 1:1 between Spotler CRM and Freshsales.
Complexity
BStandard
Timeline
2-4 weeks
Overview
Moving from Spotler CRM to Freshsales is an outbound data migration from a UK-focused SMB CRM into a Freshworks-native AI-powered CRM that serves a significantly larger customer base. Spotler CRM stores Contacts, Companies, Opportunities, and Activities in flat relational tables with company_id foreign keys linking records; we preserve these relationships by resolving parent-record IDs during export and re-establishing them at import time. The platform lacks a public REST API on lower tiers, so we use Spotler CRM's CSV export with UTF-8 encoding and configurable field selection, then transform the export into Freshsales import format. Dropdown list values require explicit mapping because Spotler stores them as reference IDs separate from field definitions. Document attachments migrate as metadata records with a warning flag if total volume exceeds the target Freshsales plan storage. Quotations, Cases, Workflows, and Reports do not migrate as code; we deliver a written inventory of these 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 Spotler CRM 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 CRM
Contact
Freshsales
Contact
1:1Spotler Contact records map directly to Freshsales Contact by email as the unique identifier. Standard fields (first_name, last_name, email, phone, mobile, job_title, address fields) map to Freshsales Contact fields. Custom properties on Spotler Contacts migrate to Freshsales custom Contact fields, but only after the destination schema is pre-created with matching field types. Dropdown list values require explicit mapping because Spotler stores them as reference IDs in the export and as value labels in Freshsales.
Spotler CRM
Company
Freshsales
Account
1:1Spotler Company records map to Freshsales Account. The company_name maps to account_name, industry maps to industry, number_of_employees maps to employees, and address fields map to the address compound field. Company-to-Contact linkage via company_id foreign key is preserved by resolving the company_id to the Freshsales Account ID at Contact import time. Spotler plan-tier company caps (1,000 Starter, 5,000 Professional) do not apply to the destination, but we verify the customer is not at the cap during scoping to avoid unexpected export truncation.
Spotler CRM
Opportunity
Freshsales
Deal
1:1Spotler Opportunity records map to Freshsales Deal. Pipeline stage from Spotler migrates as the Deal status value in Freshsales, and deal_value maps to deal_value. The Spotler Owner (sales rep) resolves by email against Freshsales User records. If the owner is inactive or absent in Freshsales, we flag the record for the admin to provision the User before the Deal import phase. Closed-won and closed-lost reasons migrate to custom deal fields.
Spotler CRM
Activity (Task)
Freshsales
Task
1:1Spotler Tasks linked to Contacts or Companies migrate to Freshsales Task records with the parent Contact or Account lookup resolved at migration time. Activity date, subject, description, and completion status map directly. Spotler stores activity type (call, email, meeting, note, task) as a string field; we map this to the appropriate Freshsales task type and set task_subtype where applicable.
Spotler CRM
Activity (Call)
Freshsales
Task (Call subtype)
1:1Spotler call activity records with duration and disposition notes migrate to Freshsales Task with type set to Call and Call Duration stored in a custom field. The related Contact or Company lookup resolves via email match against the migrated Contact and Account records. Call recordings stored as document attachments on Spotler migrate as Freshsales Document records linked to the task.
Spotler CRM
Activity (Meeting)
Freshsales
Task (Meeting subtype)
1:1Spotler meeting activities with location, start time, and end time map to Freshsales Task with type set to Meeting. Attendee information is preserved as a custom multi-line text field since Freshsales does not have a native EventAttendee equivalent at the base tier. The related Contact or Account lookup resolves at migration time.
Spotler CRM
Activity (Note)
Freshsales
Note
1:1Spotler notes attached to Contacts or Companies migrate to Freshsales Note records linked via the appropriate parent object lookup. Rich text formatting in Spotler notes converts to plain text in Freshsales. Notes without a valid parent Contact or Account are held in a reconciliation queue for the admin to assign post-migration.
Spotler CRM
Quotation
Freshsales
Quote
1:1Spotler Quotations (Professional and Enterprise only) export as a header record with line items as a separate table. We merge these into Freshsales Quote format, preserving line item descriptions, quantities, and prices. Quote status migrates as a custom field. The parent Deal lookup resolves by matching the Spotler opportunity_id to the migrated Freshsales Deal.
Spotler CRM
Case
Freshsales
Ticket
1:1Spotler Cases (Professional and Enterprise) map to Freshsales Ticket if the destination plan includes the Service module. Case priority and status map to Freshsales Ticket priority and status. Case owner resolves by email against Freshsales User records. Conversation threads on Cases migrate as Note records attached to the Ticket.
Spotler CRM
Custom Fields and Dropdown Lists
Freshsales
Custom Fields
lossySpotler allows free-form custom field creation without enforced naming conventions, and dropdown list values are stored as reference IDs separate from field definitions. We export the Spotler field definition table alongside the data export, then pre-create all custom fields in Freshsales before importing record values. Each dropdown list value is mapped explicitly from Spotler reference ID to Freshsales label so that no silent data loss occurs during import. Dropdown values that have no Freshsales equivalent are flagged for the admin to define before final import.
Spotler CRM
Tag
Freshsales
Tag
lossySpotler tags applied to Contacts and Companies export as a comma-separated string per record. We parse these into individual Freshsales Tags and create Tag records linked to the migrated Contact and Account. Tags used for list segmentation export as list membership records and are recreated as Freshsales contact lists.
| Spotler CRM | Freshsales | Compatibility | |
|---|---|---|---|
| Contact | Contact1:1 | Fully supported | |
| Company | Account1:1 | Fully supported | |
| Opportunity | Deal1:1 | Fully supported | |
| Activity (Task) | Task1:1 | Fully supported | |
| Activity (Call) | Task (Call subtype)1:1 | Fully supported | |
| Activity (Meeting) | Task (Meeting subtype)1:1 | Fully supported | |
| Activity (Note) | Note1:1 | Fully supported | |
| Quotation | Quote1:1 | Fully supported | |
| Case | Ticket1:1 | Fully supported | |
| Custom Fields and Dropdown Lists | Custom Fieldslossy | Mapping required | |
| Tag | Taglossy | 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 CRM gotchas
Plan-tier company record caps block migrations at scale
Workflow definitions do not export and must be rebuilt
Document storage limits vary by plan tier
Custom fields require explicit schema mapping between environments
Two-way MailSync configuration does not transfer between CRMs
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 CSV export scoping
We audit the Spotler CRM account to count Contacts, Companies, Opportunities, Activities, Custom Fields, Dropdown Lists, Quotations, Cases, and Documents. We identify the Spotler plan tier to confirm record caps are not in effect and verify which objects are available (Quotations and Cases require Professional or Enterprise). We run a trial CSV export from the Spotler UI to validate field selection, encoding, and export completeness before committing to the full extraction plan. The discovery output is a written scope document with record counts per object and a list of dropdown fields requiring explicit value mapping.
Field mapping and dropdown value preparation
We export the Spotler field definition table alongside the data export and build the explicit dropdown ID-to-label mapping. We compare Spotler field types against Freshsales field types (text, number, date, picklist, multi-select picklist) and flag any mismatches. We pre-create the Freshsales custom field schema before any data import begins, ensuring that Freshsales field IDs are available for the data transform step. This phase also includes running a data quality report to identify duplicate email addresses, missing required fields, and malformed records.
Freshsales account preparation and sandbox import
We create a Freshsales sandbox environment or use a trial account for validation. We pre-provision User accounts matching the Spotler Owner email addresses so that OwnerId lookups resolve at migration time. We create any required custom fields, dropdown value sets, Deal pipelines, and account territories in Freshsales before importing data. We then run a full sandbox migration with production-like record volume to validate field mapping, dropdown value transformation, parent-record lookups, and data quality. Any mapping corrections are made here before the production migration.
Data extraction from Spotler CRM
We export data from Spotler CRM using the CSV export mechanism with UTF-8 encoding enforced. Exports run per object in dependency order: Companies first (no dependencies), then Contacts (with Company ID resolution), then Opportunities (with Owner ID resolution), then Activities (Tasks, Calls, Meetings, Notes with parent record resolution), then Quotations, Cases, and Tags. Documents are retrieved via the Spotler document API in batches, with total volume calculated against the destination plan storage limit before file bytes are staged. Each export produces a row-count reconciliation report.
Data transformation and import into Freshsales
We transform each Spotler export file into Freshsales CSV import format, applying the dropdown ID-to-label mapping, date format normalisation (DD/MM/YYYY to MM/DD/YYYY where the account locale differs), phone number standardisation, and email deduping on the unique identifier. We import in Freshsales dependency order: Accounts, Contacts, Deals, Tasks, Notes, Quotes, Tickets, and Tags. Each phase emits an import error report that we resolve before proceeding to the next phase. Duplicate email records are flagged for the admin to merge manually post-migration.
Validation, cutover, and Workflow rebuild handoff
We run a reconciliation report comparing Spotler record counts against Freshsales record counts for each object. We spot-check 25-50 records across objects for field-level accuracy. We deliver the Workflow and Automation specification document to the customer's admin team for rebuild in Freshsales. We do not rebuild Spotler Workflows as Freshsales automations inside the migration scope. We provide a one-week hypercare window for reconciliation issues. MailSync reconnection guidance is delivered separately on the day of cutover.
Platform deep dives
Spotler CRM
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 CRM 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 CRM: Specific RPS limits are not publicly documented, but Spotler exposes per-user call quotas with configurable Usage Alerts and Failed Call Alerts under Settings > Integrations > API V4 to monitor consumption against the contracted ceiling..
Data volume sensitivity
Spotler CRM 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 CRM to Freshsales migration scoping. Not seeing yours? Book a call.
Walk through your Spotler CRM 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 CRM
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.