Migrate from Spotler CRM to Salesforce Sales Cloud

Spotler Contact records map to Salesforce Contact objects. 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.

Spotler Company records map to Salesforce Account objects. 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.

Spotler Opportunity records map to Salesforce Opportunity objects. 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.

Spotler pipeline stages map to Salesforce Opportunity Stage values via an explicit configuration table. 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.

Spotler Activities link to Contacts or Companies and carry type, date, duration, and description. 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.

Spotler Quotations (Professional and Enterprise plans) carry line items, pricing, and status. 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.

Spotler Cases (Professional and Enterprise) with priority, status, and SLA assignment data map to Salesforce Case records. The Spotler case-contact link resolves to Salesforce Contact via the email dedupe key. If the destination Salesforce org does not include Service Cloud, Cases migrate as Salesforce Tasks with a custom case_type__c field to preserve the classification.

Spotler free-form custom fields on Contacts, Companies, and Opportunities require explicit schema pre-creation in Salesforce before any record data imports. We export the field definition table (field name, type, dropdown list reference) and create matching Salesforce custom fields with appropriate field types (Text, Number, Picklist, Date, Checkbox). Dropdown list values map explicitly per value to avoid silent data loss.

Spotler Users (name, email, role, group membership) map to Salesforce User records by email match. Permission levels (Admin, Standard, Read-only) map to Salesforce profile assignments. Any Spotler Owner referenced on a Contact, Company, or Opportunity without a matching Salesforce User is held in a reconciliation queue for the customer's admin to provision before record import resumes.

Spotler tags applied to Contacts and Companies migrate to Salesforce custom multi-select picklist fields on Contact and Account. If tags are used for segmentation logic, they migrate to Salesforce Topics with TopicAssignment records. The customer chooses the target field strategy during scoping.

Spotler documents attached to Contacts, Companies, and Opportunities export as ContentDocument metadata (filename, size, linked record, upload date). We do not transfer the binary file payload unless the destination Salesforce edition's storage allocation accommodates the total volume (5GB Professional, unlimited on Enterprise). Storage is scoped during discovery.

Spotler Workflow definitions store automation logic referencing field IDs and object logic that do not export. We document each workflow's trigger, conditions, and actions during discovery and produce a workflow specification document. The customer or a Salesforce partner rebuilds automations in Salesforce Flow using this specification. Complex multi-step workflows are flagged for manual review before go-live.