Skip to content
Get a quote

Spotler CRM to Salesforce migration

We migrate Contacts, Companies, Opportunities, and Activities from Spotler CRM into Salesforce with Company-to-Contact relationships preserved via ID resolution, pipeline stages explicitly mapped before import, and every Spotler custom field created in Salesforce before any record data moves.

Short answer

FlitStack AI migrates contacts, accounts, opportunities, opportunity stage + record types, task and events from Spotler CRM to Salesforce, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 3-5 weeks.

By

Source Spotler CRM
DestinationSalesforce
ContactAccountOpportunityOpportunity Stage + Record TypeTask, Event
Mapped field by field · sample run · one-click rollback

What moves from Spotler CRM to Salesforce?

Moving from Spotler CRM to Salesforce is a structural migration across two fundamentally different architectures.

Read the full summary

Spotler CRM uses flat relational tables with Contacts linked to Companies and Opportunities carrying pipeline stage and value fields. Salesforce uses a relational model with Accounts, Contacts, Leads, and Opportunities as distinct objects, each with its own field structure and relationship graph. We extract Spotler data via CSV or live API reads, resolve the Company-ID foreign key at migration time so each Contact lands attached to the correct Account, and map Spotler pipeline stage names to Salesforce stage values on the corresponding Opportunity. Custom fields and dropdown lists require explicit schema mapping because Spotler allows free-form field creation with no enforced naming convention. Workflows, Quotations, Cases, and MailSync configurations do not migrate as platform-native features; we deliver a written inventory of each for the customer's admin to rebuild in Salesforce. Historical activity records (calls, emails, meetings, tasks) migrate as Salesforce Tasks and Events with parent-record Lookups preserved. Document metadata migrates alongside records, but document files require separate storage capacity planning against the target Salesforce edition's file limits.

1:1

Contact → Contact

Spotler Contact records map to Salesforce Contact objects.

How it maps

Email address is the dedupe key. Each Contact's company_id foreign key resolves to the Salesforce Account record created in the prior phase, establishing the Contact-to-Account Lookup relationship. Standard fields (FirstName, LastName, Email, Phone, MailingAddress) migrate directly; custom properties require pre-created Salesforce custom fields.

1:1

Company → Account

Spotler Company records map to Salesforce Account objects.

How it maps

The company_id serves as the internal identifier and is preserved as a custom field spotler_company_id__c for audit. Account is the parent object created before Contact import so that AccountId Lookup is satisfied at the moment of Contact insert. Industry, size, and address fields migrate to standard Account fields where named equivalents exist.

1:1

Opportunity → Opportunity

Spotler Opportunity records map to Salesforce Opportunity objects.

How it maps

The Spotler pipeline stage name maps to Salesforce StageName using the customer-specific stage mapping collected during scoping. Deal value migrates to Amount; expected close date to CloseDate; assigned owner to OwnerId via the User lookup. Closed-Won and Closed-Lost reason fields migrate to custom Opportunity fields if they exist in the Spotler configuration.

configuration

Opportunity → Opportunity Stage + Record Type

Spotler pipeline stages map to Salesforce Opportunity Stage values via an explicit configuration table.

How it maps

If Spotler uses multiple pipelines, each pipeline becomes a Salesforce Record Type on Opportunity with a corresponding Sales Process that whitelists only the applicable stage values. Probability percentages round to Salesforce-allowed integers.

1:1

Activity (Task, Call, Meeting, Note) → Task, Event

Spotler Activities link to Contacts or Companies and carry type, date, duration, and description.

How it maps

Tasks migrate as Salesforce Task records with Status, Priority, and ActivityDate preserved. Call-type activities set TaskSubtype=Call with duration in CallDurationInSeconds. Meeting-type activities migrate as Salesforce Event records with StartDateTime and EndDateTime preserved. Notes migrate as Salesforce Note records linked via ContentDocumentLink to the parent Contact, Account, or Opportunity.

1:1

Quotation → Quote

Spotler Quotations (Professional and Enterprise plans) carry line items, pricing, and status.

How it maps

They map to Salesforce Quote records on Sales Cloud Professional and above. Each quotation's line items map to QuoteLineItem records with resolved Pricebook2, Product2, Quantity, and UnitPrice. Quotation PDFs do not transfer as attachments; they are documented for manual re-upload if required.

What moves12 objects
Spotler CRMSalesforce
  • ContactContact1:1
  • CompanyAccount1:1
  • OpportunityOpportunity1:1
  • OpportunityOpportunity Stagetransformed
  • ActivityTask, Event1:1
  • QuotationQuote1:1

+ 6 more in the mapping below

How Spotler CRM and Salesforce differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

DimensionSpotler CRMSalesforce
Lead modelSingle Contact object with Lifecycle Stage tracked as a propertySeparate Lead and Contact objects; unqualified prospects become Leads, qualified buyers become Contacts under Accounts
Account and Company structureCompanies as standalone records linked to Contacts via company_idAccounts as parent records; Contacts live as child records under Accounts with a Lookup relationship
Pipeline configurationSingle pipeline per Spotler plan with configurable stagesUnlimited Opportunity record types and sales processes from Professional tier without setup fees
Custom objectsCustom fields available on all plans; no separate custom object conceptFormal Custom Objects with __c suffix available from Professional tier ($80/user/mo)
QuotationsProfessional and Enterprise plans onlyStandard Quote object available on Professional and above as part of Sales Cloud
Pricing modelPer-user pricing with company record caps (1,000 Starter, 5,000 Professional)Per-user with unlimited records from Professional; $1,500 annual minimum applies at 5-user minimum
Workflow automationWorkflow automations available on Professional; no export mechanismSalesforce Flow with record-triggered, scheduled, and screen variants from Professional

What to watch for in a Spotler CRM to Salesforce migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

Plan-tier company record caps can silently block inbound records

Spotler enforces company account limits per plan tier (Starter 1,000, Professional 5,000).

How we handle it

When migrating into Salesforce, we map Spotler Company records to Salesforce Accounts without Salesforce-level record caps, but we flag customers who are also evaluating other destinations with per-account billing to avoid billing shock. During outbound scoping, we confirm the full company count against the target Spotler plan before attempting any inbound migration. Records exceeding the cap during a reverse migration are rejected silently and cause import failures.

medium

MailSync email configuration does not transfer between CRMs

Spotler's two-way MailSync synchronises email threads with Contact records and maintains a link between the CRM record and the email account.

How we handle it

This configuration belongs exclusively to the source Spotler environment and cannot be exported. During migration, email conversation history is preserved as Activity records. We notify the customer that MailSync must be re-connected in Salesforce and provide the step-by-step reconnect guide. The Salesforce Outlook Gmail Integration or a third-party email sync app is required post-migration.

medium

Dropdown list values require explicit per-value mapping

Spotler dropdown lists are defined separately in settings and stored as reference IDs in the data export.

How we handle it

Salesforce stores picklist values as metadata tied to specific field definitions. We export the Spotler field definition table alongside the data export and create matching Salesforce picklist fields before importing record values. If Spotler uses values that have no Salesforce equivalent, we flag each one explicitly to prevent silent data loss rather than allowing the import to drop unrecognized values.

medium

Document binary transfer requires storage capacity planning

Spotler document storage limits vary by plan (100MB Free, 1GB Starter, 5GB Professional, unlimited Enterprise).

How we handle it

Salesforce Storage Allocation is org-wide and shared across all object types. We calculate total document volume during scoping and compare it against the destination Salesforce edition's storage. If total document payload exceeds the target limit, we migrate document metadata (filename, linked record, upload date, file size) without binary files and stage document migration as a separate batch with customer-approved storage expansion.

medium

Salesforce validation rules and field-level security can block imports

Salesforce orgs commonly enforce validation rules (required formats, conditional required fields, picklist whitelists) and field-level security that prevent the migration user from writing records unless explicitly bypassed.

How we handle it

We coordinate with the customer's Salesforce admin before migration to grant the migration user the Bulk API permission set and temporarily adjust or extend validation rules with a migration-context bypass. Skipping this step results in partial record rejection on first import.

How the migration runs

  1. Discovery and data audit

    We audit the source Spotler CRM environment across plan tier, active object count (Contacts, Companies, Opportunities, Activities), custom field definitions, dropdown list values, pipeline stage names, active workflows, quotation and case volumes, and MailSync usage.

    What this step covers

    We pair this with a Salesforce edition recommendation: Professional ($80/user, 5-user minimum) covers most migrations without custom objects; Enterprise ($165/user) is required if the customer needs record-triggered Flow at scale or advanced reporting types. The discovery output is a written migration scope, field mapping draft, and Salesforce edition recommendation.

  2. Schema pre-creation in Salesforce

    We create the destination schema in Salesforce before any data moves.

    What this step covers

    This includes pre-creating all custom fields on Contact, Account, and Opportunity with type-mapped Salesforce field types; building Opportunity Record Types and Sales Processes per Spotler pipeline; creating picklist value sets for dropdown lists; and configuring any custom objects required. Schema is deployed into a Salesforce Sandbox first for validation and signed off by the customer's admin before production migration begins.

  3. Sandbox migration and reconciliation

    We run a full migration into a Salesforce Sandbox using production-like data volumes.

    What this step covers

    The customer's RevOps lead reconciles record counts per object, spot-checks 25-50 random records against the Spotler source, validates that Contact-to-Account relationships are correctly resolved, and confirms that pipeline stage names map correctly to Salesforce Stage values. Mapping corrections are made in the Sandbox environment before production migration begins.

  4. Owner and User reconciliation

    We extract every distinct Spotler Owner referenced on Contact, Company, Opportunity, and Activity record and match by email against the destination Salesforce org's User table.

    What this step covers

    Owners without a matching Salesforce User enter a reconciliation queue. The customer's Salesforce admin provisions any missing Users before record import resumes, because OwnerId references are required on most standard objects at insert time.

  5. Production migration in dependency order

    We run production migration in record-dependency order: Accounts (from Spotler Companies with spotler_company_id__c preserved), Contacts (with AccountId Lookup resolved), Opportunities (with AccountId, OwnerId, and RecordTypeId resolved), Products and Pricebook entries (if migrating quotations), Quote records, Activity history (Tasks and Events via Salesforce Bulk API with parent-record Lookups), Cases, and Tags.

    What this step covers

    Each phase emits a row-count reconciliation report before the next phase begins.

  6. Cutover, validation, and workflow rebuild handoff

    We freeze Spotler writes during cutover, run a final delta migration of any records modified during the migration window, then enable Salesforce as the system of record.

    What this step covers

    We deliver the workflow specification document listing every Spotler workflow with its trigger, conditions, and actions, plus a recommended Salesforce Flow equivalent. We provide the MailSync reconnect guide and document attachment re-upload steps. We support a one-week hypercare window for reconciliation issues. We do not rebuild Spotler workflows as Salesforce Flow inside the migration scope.

Spotler CRM Salesforce
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · SalesforceRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

3-5 weeksTypical, smaller accounts
7-12 weeksLarge or heavily customised accounts

A quote scales with record volume, custom field count, and automation rebuild scope. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Spotler CRM to Salesforce →

Why teams move from Spotler CRM to Salesforce

  • Spotler enforces plan-tier company record caps that Salesforce does not impose. Starter caps at 1,000 Companies and Professional at 5,000, forcing expensive upgrades before other enterprise features are available. Salesforce Professional ($80/user) carries no per-account record limit, making it more predictable for mid-market teams that exceeded Spotler's ceiling.
  • Spotler's third-party integration ecosystem is significantly smaller than Salesforce's AppExchange with over 9,000 listings. Teams requiring native ERP connectors, CPQ, contract lifecycle management, or advanced revenue intelligence tools move to Salesforce because those integrations are first-party or AppExchange-certified rather than Zapier-routed third-party routes.
  • Spotler reaches a feature ceiling for teams requiring advanced reporting, territory management, and custom fiscal period forecasting. G2 and Capterra reviewers note Spotler lacks the customisation depth required by rapidly growing B2B teams, while Salesforce's reporting engine supports multi-dimensional pipeline analysis across territories and product lines without exporting to a data warehouse.
  • Salesforce's Einstein 1 platform adds AI-powered forecasting, lead scoring, and revenue intelligence features that Spotler CRM does not offer at any tier. Teams moving to Salesforce for data-driven sales operations cite AI-assisted insights as a driver alongside the platform's scale, with Einstein Copilot available on Sales Cloud Professional and above.
  • Marketing add-on pricing on Spotler (Simple at $26/month, Advanced at $55/month) stacks on top of the base CRM licence and increases total cost for teams needing full automation. Salesforce Sales Cloud Professional bundles advanced sales features without add-on tiers, and Salesforce Marketing Cloud Account Engagement (Pardot) offers a unified GTM stack for teams requiring both sales and marketing automation on one platform.

Questions, answered

Spotler CRM to Salesforce migration questions

How long does a Spotler CRM to Salesforce migration take?

Most migrations land between three and five weeks for accounts under 10,000 Contacts and 2,000 Companies with straightforward pipeline stages and no custom objects. Migrations with quotation line-item structures, large activity histories (over 200,000 activity records), or multiple Spotler pipelines move to seven to twelve weeks because of parent-record ID resolution, bulk API time, and workflow specification documentation.

Do Spotler Workflows, Quotations, and Cases migrate to Salesforce?

Spotler Workflows do not migrate to Salesforce Flow as they are different automation models with different trigger types and action libraries. We deliver a written workflow specification document for the customer's admin to rebuild in Salesforce Flow. Spotler Quotations (Professional and Enterprise) map to Salesforce Quote objects with line items as QuoteLineItem records; quotation PDFs are documented for manual re-upload. Spotler Cases map to Salesforce Case records if the destination org includes Service Cloud licensing.

Can we keep Spotler for marketing while moving sales to Salesforce?

A hybrid stack is viable if the customer uses Spotler primarily for its email marketing and automation features. We configure a HubSpot-to-Salesforce-style bidirectional sync during migration so that new leads from Spotler marketing flows into Salesforce as Leads or Contacts, and Salesforce Opportunities sync back to Spotler for attribution tracking. The customer continues paying for Spotler marketing at the marketing layer while moving sales seat licensing to Salesforce.

Do we lose historical activity data (calls, emails, meetings, tasks) during migration?

No. We migrate the full activity history through the Salesforce Bulk API with parent-record resolution. Calls land as Task with TaskSubtype=Call and CallDurationInSeconds preserved; emails land as Salesforce EmailMessage records linked to Tasks; meetings land as Event records; tasks land as Task records. Activity timeline ordering is preserved by setting ActivityDate to the original Spotler timestamp. Notes migrate as Salesforce Note records linked via ContentDocumentLink to the parent Contact, Account, or Opportunity.

What happens to our Spotler custom fields and dropdown lists?

Spotler allows free-form custom field creation without enforced naming conventions, and dropdown lists are defined separately as reference IDs in the data export. We export the field definition table alongside the data and pre-create every matching Salesforce custom field with the correct field type (Text, Number, Picklist, Date, Checkbox) before importing any record values. Dropdown list values are mapped explicitly per value to avoid silent data loss where Spotler and Salesforce picklist structures differ.

What is the minimum Salesforce edition required for this migration?

Salesforce Professional ($80/user/month, 5-user minimum) is sufficient for most Spotler CRM migrations without custom objects or complex quoting requirements. Professional includes the Quote object, custom fields, and record types. Enterprise ($165/user/month) is recommended if the customer requires record-triggered Flow at scale, advanced reporting types, territory management, or custom fiscal period forecasting. Unlimited ($300/user/month) only if 24x7 support and unlimited custom apps are required.

Get a quote

Moving from Spotler CRM to Salesforce?

Tell us roughly how many records and objects you have. We scope the mapping and the Salesforce setup with you, then send a quote.

Get a quote