Migrate from Spin CRM to Microsoft Dynamics 365 Sales

Spin CRM Leads map directly to Dynamics 365 Lead. Standard fields (full name, email, phone, company, status, owner) migrate via CSV column mapping. Spin CRM's custom fields on Leads require explicit inclusion in the CSV export settings before extraction; we review column headers against the customer's reported custom field list and request a re-export if columns are missing. The migration user must verify that all custom Lead fields are present in the CSV before import proceeds.

Spin CRM Contacts map to Dynamics 365 Contact, preserving name, email, phone, job title, and custom fields. The contact-to-company relationship in Spin CRM resolves to AccountId on Contact after Account migration completes. If Spin CRM's export does not expose the company foreign key directly, we match Contacts to Accounts by company name during the transform phase. Custom fields follow the same visibility verification process as Lead custom fields.

Spin CRM Company records map to Dynamics 365 Account. Company name becomes Account Name; address fields map to Address composite fields; industry maps to Industry picklist. We export Companies first to establish the AccountId anchor before importing Contacts, ensuring that Contact records have a valid parent AccountId at insert time rather than requiring a post-import reconciliation pass.

Spin CRM Deals map to Dynamics 365 Opportunity. Each Deal carries a value, stage, owner, expected close date, and Contact/Company associations. We extract the current Spin CRM stage configuration (stage names, order, and probabilities) during scoping and replicate it as a Microsoft Dynamics 365 Sales Process with stage values that preserve the original stage names. Closed-Won and Closed-Lost stages migrate with their respective status mappings. Note that Spin CRM's flat deal model does not include a separate Opportunity Product object; if the customer uses product-line items in Spin CRM Deals, those migrate as Opportunity Product records with PricebookEntry references.

Spin CRM's fully customizable pipeline stages replicate as Microsoft Dynamics 365 Sales Process stage values. We capture the full stage sequence (name, order, probability percentage) during scoping and configure it in the destination Dynamics 365 org before any Deal or Opportunity records load. Stage probability percentages migrate to StageProbability on the Opportunity Stage picklist values. If the customer uses multiple named pipelines in Spin CRM, these map to separate Record Types on Opportunity in Dynamics 365.

Spin CRM Activity records (task reminders, call logs, meeting notes) map to Dynamics 365 Task and Event objects. Spin CRM's activity export mechanism is not explicitly documented in available sources; we attempt export via the settings-based CSV path and supplement with manual extraction where the export does not surface all activity types. Task records carry Status, Priority, and ActivityDate; call dispositions migrate to custom Task fields if present in the export. Meeting records map to Event with StartDateTime, EndDateTime, and Location preserved. We flag any activity type that cannot be extracted from Spin CRM's export mechanism and document the gap in the migration scope report.

Spin CRM supports custom fields on Leads, Contacts, Companies, and Deals, but the CSV export may not expose all custom fields unless the user explicitly adds them to the export view. We review the exported column headers against the customer's reported custom field list during the scoping phase. Any missing columns require a re-export with custom fields included. Custom field values that do not appear in the CSV are flagged and excluded from the migration scope with a written note to the customer for manual follow-up. In Dynamics 365, we pre-create matching custom fields with appropriate data types (text, number, picklist, date) before the import phase begins.

Spin CRM owner assignments on Leads, Contacts, Deals, and Activities map to Dynamics 365 OwnerId by resolving the owner's email address against the destination User table. We extract the distinct owner list from all Spin CRM exports and match against the target Dynamics 365 org's Users. Any owner without a matching Dynamics 365 User goes to a reconciliation queue for the customer's admin to provision before record import resumes. OwnerId references on all standard objects must resolve before import can complete.

Spin CRM includes document storage as a feature, but the export mechanism for attachments and document blobs is not documented in available sources. We do not attempt to migrate document content without a confirmed export path. We document the document storage gap in the migration scope and recommend that the customer's admin either downloads documents manually from Spin CRM or re-uploads them to Dynamics 365 SharePoint integration post-migration. This is an out-of-scope item for the data migration engagement.