Migrate from Spotler CRM to Microsoft Dynamics 365 Sales

Spotler Contact records map directly to Dynamics 365 Contact. Email address is the primary dedupe key used during import. Standard fields (firstname, lastname, email, telephone, address) map to the equivalent Dynamics Contact attributes. We export all custom Contact properties alongside the standard fields and recreate them as typed Dataverse custom columns before importing, using the Spotler field definition table to assign the correct column type (text, number, date, picklist). The Spotler company_id foreign key is preserved as a reference for Account linkage during the Company import phase.

Spotler Company records map to Dynamics 365 Account. The company name is the dedupe key, and the Spotler industry and company size fields map to the Account's Industry and NumberOfEmployees attributes. We import Account records first so that AccountId is available when Contact records are inserted, satisfying the parent lookup constraint. Any Spotler company with no linked Contacts is imported as a standalone Account with no relationship to migrate.

Spotler Opportunities map to Dynamics 365 Opportunity. The Spotler dealstage freeform text field is the most critical mapping challenge: Spotler allows any string as a pipeline stage name per pipeline, while Dynamics requires controlled picklist values defined in a Sales Process. We collect all distinct dealstage values during discovery, create corresponding StageName picklist items in Dynamics, and configure a Sales Process that scopes the relevant stages before Opportunity records are imported. Estimated close date and deal value map directly to EstimatedCloseDate and EstimatedValue.

Spotler's multiple pipeline support maps to Dynamics 365 Record Types on Opportunity. Each Spotler pipeline becomes a Record Type with its own Page Layout and Sales Process. The Sales Process whitelists the pipeline's stage values and sets probability percentages per stage. If Spotler has three pipelines with different stage names, we create three Record Types in Dynamics and map each Spotler deal to its corresponding Record Type during import using the pipeline assignment field.

Spotler stores all activity types (calls, emails, meetings, tasks, notes) in a single Activities table with an activity type field. We split this table at migration time: calls and tasks become Dynamics Task records with TaskSubtype set to Call where applicable; meetings become Dynamics Event records with StartDateTime, EndDateTime, and Location preserved. The related Contact or Company ID from Spotler maps to the Regarding (object) lookup in Dynamics via parent-record resolution. Activity timestamps are preserved as the original Spotler recorded date.

Spotler Quotations are available on Professional and Enterprise plans. Microsoft Dynamics 365 Sales does not include a native Quote object by default on Starter; it requires Sales Professional ($65/user/month) or above. We configure the standard Quote entity (quotedetail, quantity, unitprice) in Dynamics, map Spotler quotation line items to QuoteDetail records, and preserve quotation status (draft, sent, accepted, rejected) as a custom picklist field. PDF attachments from Spotler migrate as Note records attached to the Quote. Quotations with complex pricing rules or conditional discounts require a manual review step before migration.

Spotler Cases migrate to Dynamics 365 Case if the destination org includes Service Cloud or Sales Enterprise with case management enabled. Case priority, status, and SLA assignment from Spotler map to the equivalent Case fields. Case conversations migrate as EmailMessage records linked to the Case. Cases with nested SLA rules or escalation workflows cannot carry that logic; we document the SLA configuration separately for the customer's admin to rebuild in Dynamics SLA configuration.

Spotler allows freeform custom field creation with no enforced naming conventions, and dropdown list values are stored as reference IDs separate from the data export. We export the field definition table (field name, type, short description, and all dropdown list values) alongside the record data, create equivalent typed Dataverse columns on the target entity before importing records, and map each dropdown value ID to the corresponding Dynamics option label. Any Spotler custom field that cannot be cleanly typed (for example, a field storing mixed JSON-like values) is flagged for manual review and migrated as a text column with a note in the migration spec.

Spotler Owners (users assigned to Contacts, Companies, and Opportunities) map to Dynamics 365 User records. We match by email address. Owners without a matching User in the Dynamics destination are placed in a reconciliation queue for the customer's admin to provision before record import proceeds, because OwnerId is a required reference on Opportunity and other standard entities.

Spotler uses both static lists and dynamic segments, and tags apply to individual records. We export tag names per Contact and list membership as separate tables. Tags migrate as either Dynamics Topics (with TopicAssignment records linked to Contact) or as multi-select picklist fields on the Contact entity, depending on the customer's preference confirmed during scoping. Dynamic segments require a separate rebuild brief as they cannot be migrated as data.