Migrate from solve 360 to Microsoft Dynamics 365 Sales

solve 360 Contacts map directly to Microsoft Dynamics 365 Sales Contacts. Standard fields (full name, email, phone, address) transfer via the resolve-owner lookup workflow. User-defined custom fields on Contacts migrate to equivalent Dataverse columns with matching data types (text to string, number to integer or decimal, date to datetime). We create the destination field schema before import using the Microsoft Dynamics 365 Sales or Power Platform admin center.

solve 360 Companies map to Microsoft Dynamics 365 Sales Accounts. Company name maps to Account Name; domain maps to Website. Parent-child company relationships in solve 360 become Parent Account lookup relationships in Microsoft Dynamics 365 Sales . Account is created before Contact import so that the AccountId lookup on Contact is satisfied at insert time, preventing orphaned Contact records.

solve 360 Tasks map to Microsoft Dynamics 365 Sales Tasks. Status, Priority, Due Date, Description, and time tracking fields transfer. HubSpot owner assignment in solve 360 resolves to Microsoft Dynamics 365 Sales User by email match; any task with an unresolved owner is placed in a reconciliation queue for the customer's admin to provision the missing User record before migration continues.

solve 360 Follow-ups are time-stamped activity records tied to Contacts or Companies. We map them to Microsoft Dynamics 365 Sales Task with the Activity Type set to Follow-up (via a custom field or Task Category) and the original solve 360 timestamp preserved as Activity Date. Follow-up text migrates as the Task Description.

solve 360 Support Requests map to Microsoft Dynamics 365 Sales Case (or Dynamics 365 Customer Service Case if the Sales Professional license does not bundle Service). Request status, priority, description, and full conversation thread transfer as Case Description and EmailMessages linked to the Case. If the destination org does not include the Customer Service module, we map to a custom Case entity in Dataverse and flag the licensing gap during scoping.

solve 360 Users are both system actors and assignment targets on Tasks, Follow-ups, and Support Requests. We export the solve 360 user list and match by email address against the destination Microsoft Dynamics 365 Sales User table. Any solve 360 user without a matching Dynamics 365 User is flagged in a reconciliation report; the customer's admin provisions the missing User before record import resumes.

solve 360 pipelines and their stages (with probability percentages and ordering) are exported and reconstructed in Microsoft Dynamics 365 Sales as Sales Processes with corresponding stage values on the Opportunity object. If solve 360 has multiple pipelines, we create multiple Sales Processes and map each to an Opportunity Record Type. Probability values migrate as Stage Probability rounded to the nearest integer.

solve 360 Tags are exported as a comma-separated list and mapped to a custom text field on Contact and Account in Microsoft Dynamics 365 Sales . If the customer has a small, fixed tag vocabulary, we can alternatively create a multi-select picklist. Tag associations per record transfer as field values; no separate tag taxonomy object is created unless the customer requests it during scoping.

Attachments stored on solve 360 Contacts, Companies, Tasks, and Support Requests are downloaded as files and re-uploaded to the destination. If the Microsoft Dynamics 365 Sales org uses SharePoint integration (common for Microsoft 365 environments), we upload files to the relevant SharePoint document library and create DocumentLocation records in Microsoft Dynamics 365 Sales linked to the parent Contact, Account, or Case. Without SharePoint, attachments migrate as Note attachments.