Migrate from Simply CRM to Microsoft Dynamics 365 Sales

Simply CRM companies map directly to Dynamics 365 Sales Accounts. Parent-child company hierarchies in Simply CRM map to the Parent Account lookup in Dynamics 365 Sales. Simply CRM N:N contact-company associations require Account Contact Relationships in Dataverse. During migration, each company's industry classification is validated against the Dynamics 365 Sales IndustryCode pick-list to ensure consistent categorization.

Contacts map 1:1 to Dynamics 365 Sales Contacts. Each Contact requires a valid AccountId — Simply CRM contacts without a primary company are linked to a default placeholder Account or flagged for owner resolution before migration. If a contact lacks an email address, the system generates a temporary identifier to preserve the record's uniqueness during the load.

Simply CRM leads map directly to Dynamics 365 Sales Leads. Lead status pick-list values require value-by-value mapping since Dynamics 365 Sales uses a predefined Lead Status pick-list with specific state codes. During the mapping process, any custom lead status values in Simply CRM are translated to the nearest Dynamics 365 Sales state code to maintain data integrity.

Simply CRM deals map to Dynamics 365 Sales Opportunities. The pipeline field maps to a custom Business Process Flow field, and deal stage values require value mapping to Dynamics 365 Sales Opportunity Stage pick-list values. Additionally, the estimated close date and probability fields are migrated as-is, preserving historical forecasting data for reporting.

Simply CRM cases map to Dynamics 365 Sales Cases (Incident table in Dataverse). Case status, priority, and origin pick-list values require value-by-value mapping to match Dynamics 365 Sales enumerations. During mapping, any custom case origin values are aligned to the nearest Dynamics 365 Sales case origin option to ensure consistent case routing and reporting.

Simply CRM activity records split by type into Dynamics 365 Sales Task (general tasks), PhoneCall (calls), and Appointment (meetings). Original timestamps, owners, and regarding object links are preserved. Dynamics 365 Sales requires explicit Activity Party participation types. Each activity party is assigned a ParticipationTypeMask indicating whether the party is a sender, recipient, or other role.

Simply CRM notes migrate to Dynamics 365 Sales Annotations. File attachments are uploaded to SharePoint document locations linked to the relevant Dataverse record. Original file names and MIME types are preserved during re-upload. The migration also ensures that SharePoint folder structures mirror the original Simply CRM file organization for straightforward retrieval.

Simply CRM custom fields (with _c suffix) require pre-creation as __c columns in the appropriate Dataverse table before migration data can load. Field data type matching — text, number, pick-list, date — is validated against Dynamics 365 Sales schema rules.

Simply CRM custom objects require corresponding Dataverse table creation before migration. N:N relationships between custom objects in Simply CRM need junction tables in Dynamics 365 Sales — the migration plan surfaces these and your admin pre-creates them. Each new Dataverse table includes a primary key and audit fields to align with Dynamics 365 Sales data governance standards.

Simply CRM owners resolve to Dynamics 365 Sales SystemUsers by email match against Azure Active Directory. Unmatched owners are flagged before migration so your admin either invites them to the tenant or assigns records to a fallback owner. The resolution process also updates the ownerid field on related records to ensure consistent assignment after migration.

Simply CRM workflows do not migrate to Dynamics 365 Sales. They must be rebuilt in Power Automate. We export your Simply CRM workflow definitions as a reference document so your Dynamics 365 admin can reconstruct the logic step-by-step. The exported file includes screenshots of each workflow canvas for easier reconstruction.

Report definitions and dashboards are not transferred between platforms. Underlying opportunity, contact, and case data migrates so reporting is possible in Dynamics 365 Sales, but report layouts must be rebuilt using Dynamics 365 Sales built-in reporting or Power BI. This rebuild ensures that new reports leverage Dynamics 365 Sales visualizations and real-time data connectors for accurate insights.