Migrate from Smart CRM Online to Microsoft Dynamics 365 Sales

Smart CRM Online Company records map directly to Microsoft Dynamics 365 Sales Account. The company name becomes the Account Name field; any website or domain field maps to Account.Website. We import Accounts first in the migration sequence so that the AccountId reference is available when Contacts are loaded. Smart CRM Online does not enforce a parent-company hierarchy, so all companies map as top-level Accounts without a parent account reference unless the customer's data includes an explicit hierarchy field.

Smart CRM Online Contact records map to Microsoft Dynamics 365 Sales Contact. Name, email, phone, job title, and address fields migrate directly. The Contact.AccountId is resolved by matching the Smart CRM Online Company reference (by company name or exported company ID) to the Account record created in the previous phase. Any Contact without a matching Company is flagged in a reconciliation report for the customer's admin to review before the next phase.

Smart CRM Online Deals map to Microsoft Dynamics 365 Sales Opportunity. Deal name becomes Opportunity.Name, deal value maps to Amount, expected close date maps to CloseDate, and owner maps to OwnerId via email match against the Dynamics 365 User table. The Deal.Company or Deal.Contact reference is resolved to Opportunity.AccountId and Opportunity.ContactId respectively. If the Deal export includes a stage label, we map it to a Dynamics 365 StageName under the configured Sales Process.

Smart CRM Online pipeline stages are configurable per deal pipeline. We map each distinct stage label to a Microsoft Dynamics 365 Sales Process stage entry, setting the probability percentage from the source stage configuration. If the customer uses multiple deal pipelines, we create separate Record Types in Dynamics 365, each with its own Sales Process that whitelists only the relevant stage values. Stage sequence order migrates to the stage order in Microsoft Dynamics 365 Sales Process.

Smart CRM Online call logs migrate to Microsoft Dynamics 365 Sales Task records with TaskSubtype set to Call. Call duration, disposition, and any notes attach to custom Task fields. The Task.WhoId links to the migrated Contact by email match; Task.WhatId links to the related Opportunity or Account if the source export includes those references. Activity timestamps preserve the original Smart CRM Online creation date for timeline ordering.

Smart CRM Online email engagement records migrate to Microsoft Dynamics 365 Sales EmailMessage (the message content and headers) linked to a Task record (the activity timeline entry). EmailMessage.ParentId links to the Contact; Task.ActivityDate preserves the original timestamp. Subject, body, sender, and recipient fields transfer directly. If Smart CRM Online tracks email open or click events as separate records, those migrate as Task notes.

Smart CRM Online meeting records migrate to Microsoft Dynamics 365 Sales Event. Start time, end time, location, and meeting title transfer directly. Attendee resolution matches invitee email addresses to migrated Contact records via EventRelation. The Event.WhatId links to the related Opportunity or Account if the source export includes that reference.

Smart CRM Online task records (follow-up items, to-dos) migrate to Microsoft Dynamics 365 Sales Task. Status, priority, due date, and description transfer. Task assignment resolves by matching the Smart CRM Online owner email to the Dynamics 365 User record. If the task has a linked Contact or Deal reference, Task.WhoId and Task.WhatId are resolved accordingly.

Smart CRM Online custom fields are identified during the discovery-phase audit of the CSV export. We compare all exported column headers against the standard Smart CRM Online object schema to identify which fields are custom. Custom fields are then mapped to Dynamics 365 custom fields (Custom_x field names) with type inference from the source data (text becomes Text, numeric values become Number, dates become Date). The customer confirms field mapping during scoping before the import run. Dynamics 365 validates field types at insert time, so type mismatches require transform rules before loading.