Migrate from Star CRM to Microsoft Dynamics 365 Sales

Star CRM Company records map to Microsoft Microsoft Dynamics 365 Sales Account. Company name becomes Account Name, used as the primary dedupe key during import. Address fields (street, city, state, postal code, country) map to the corresponding Address composite or individual address fields in Dynamics 365. If the Star CRM Company stores a website domain, it maps to Website. Account is imported first, before Contacts, to satisfy the AccountId lookup on the Contact object.

Star CRM Contact records map to Microsoft Dynamics 365 Sales Contact. Standard fields (FullName, Email, Phone, JobTitle, Department) migrate directly. We resolve the parent Account by matching Star CRM's Company link or company name against the imported Account records and set AccountId at migration time. Custom contact properties are flagged during discovery and mapped to pre-created Dynamics 365 custom fields.

Star CRM Deals map to Microsoft Dynamics 365 Sales Opportunity. Deal name becomes Opportunity Name; Deal value maps to Amount; pipeline stage maps to StageName via an explicit stage-mapping table built during scoping. Owner assignment resolves by email match against the User table. If Star CRM stores a Deal-to-Contact association, we preserve it by linking the Opportunity to the migrated Contact via the ContactId lookup on Opportunity.

Star CRM Activities (calls, emails, meetings, notes) map to Dynamics 365 Task and Event records. Call and task-type activities land as Task with TaskSubtype set appropriately; meeting-type activities land as Event with StartDateTime and EndDateTime preserved. Email content maps to Task description or to the EmailMessage standard object where the Dynamics 365 instance supports it. Each Activity record is linked to its parent Contact or Deal via WhoId and WhatId resolved from the migrated records.

If Star CRM distinguishes Lead records from Contact records, we export Leads separately and import them into Microsoft Dynamics 365 Sales Lead. Lead source and any custom lead properties migrate to custom fields on the Lead object. Customers choosing to merge Star CRM Leads into existing Contact records specify the merge rule during scoping; we preserve the original lead source in a custom field for reporting continuity.

Tags on Star CRM Contacts or Deals store as label text. Multi-select tag values map to a Dynamics 365 multi-select picklist field that we pre-create on the Contact or Opportunity object before import. Single-value tags map to a standard text or picklist field. Tag preservation is confirmed by the customer during scoping; unused or redundant tags are archived rather than migrated.

Custom fields on any Star CRM object (Contact, Company, Deal, Activity) have no direct Dynamics 365 equivalent and require explicit field-level mapping. During discovery, we infer the custom field name, data type, and sample values from observed Star CRM records, then pre-create matching custom fields in Dynamics 365 before data import begins. Custom field creation is a prerequisite step; we cannot import data into fields that do not exist in the destination schema.

Star CRM user records (name, email, role) map to Microsoft Dynamics 365 Sales User records. We resolve owners by email match against the destination org's User table. Any Star CRM Owner without a matching Dynamics 365 User is held in a reconciliation queue, and the customer's admin provisions the missing User before record import resumes. Active and inactive status is preserved as a custom field if the customer requests archived user history.

Star CRM exports attachments as individual files named by the system, not as a structured archive. We download all files, build a manifest linking each file to its parent record ID, and re-associate them during Dynamics 365 upload. Attachments that were linked to Contacts or Deals attach to the corresponding Note or Document record in Dynamics 365. Large attachment volumes add processing time to the project schedule.

Star CRM pipeline structures with named stages map to Microsoft Dynamics 365 Sales Record Types and Sales Processes. Each Star CRM pipeline becomes a Record Type on Opportunity, with its stage names mapped to StageName values in a corresponding Sales Process. Stage probabilities migrate from Star CRM to the Dynamics 365 Stage Probability field. If Star CRM uses a single pipeline, we create one Record Type and Sales Process; multiple pipelines create multiple Record Types.