Migrate from karmaCRM to Microsoft Dynamics 365 Sales

karmaCRM Contacts map to Dynamics 365 Contact records. We preserve first name, last name, email, phone, address, custom field values, and tag associations. The Contact's primary Company (from karmaCRM's company association) resolves to a Dynamics 365 Account record at import time using the company domain or explicit account link. Contact is imported after Account to satisfy the AccountId lookup requirement.

karmaCRM Companies map to Dynamics 365 Account records. We preserve company name, domain, address, industry classification, employee count, and custom field values. The company domain is stored as the Account Website field and used as a deduplication key if the customer already has Account records in Dynamics 365. Account is imported before Contact to satisfy the parent lookup.

karmaCRM Deals map to Dynamics 365 Opportunity records. We preserve deal name, value, stage, owner, created and updated dates, and any associated contacts and companies. The karmaCRM deal stage maps to a Microsoft Dynamics 365 Sales Process stage that we configure before migration, with stage probability percentages migrated from karmaCRM to the corresponding StageProbability field.

karmaCRM's pipeline and stage labels map to Microsoft Dynamics 365 Sales Processes and Record Types on the Opportunity object. Each karmaCRM pipeline becomes a Record Type in Dynamics 365, with stage values mapped to the Sales Process stage picklist. Stage ordering and probability percentages are preserved in the configuration.

karmaCRM Tasks map to Dynamics 365 Task records with Subject, Status, Priority, Due Date, and Owner preserved. Task associations to Contacts and Companies resolve to the migrated Contact and Account records. Completed tasks preserve their completion timestamps. Task assignment migrates by resolving karmaCRM owner email to Dynamics 365 User.

karmaCRM Events map to Dynamics 365 Event records with Start Time, End Time, Location, Subject, and Description preserved. Attendee lists map to EventRelation records pointing to the migrated Contacts and Users. Event duration and time zone information is retained from the source timestamps.

karmaCRM tags applied to Contacts and Companies migrate as a custom multi-select picklist field in Dynamics 365. The customer chooses during scoping whether tags become a native multi-select picklist on the Contact object or a Topics-based classification with TopicAssignment records. Tag names are preserved exactly as they appear in karmaCRM.

karmaCRM custom field definitions and values migrate as freeform name-value pairs in a JSON blob stored in a custom field (customfields__c) on the corresponding Dynamics 365 record. The customer's admin recreates these as typed fields (text, number, picklist, date) in Dynamics 365 post-migration using the blob as a reference. This avoids type-mismatch errors during import while preserving data for manual recreation.

Active karmaCRM users referenced on Deals, Tasks, and Events are mapped to Dynamics 365 Users by email address. The customer's admin provisions the corresponding User records in Dynamics 365 before migration. Any karmaCRM user without a matching Dynamics 365 User is held in a reconciliation queue. Role and permission structures differ between platforms and require manual reassignment post-migration.

karmaCRM email campaign metadata (name, subject line, send date, open rate, click rate, audience list count) migrates as a written inventory record rather than a functional Dynamics 365 Marketing campaign. Email campaign bodies and templates do not migrate because Dynamics 365 real-time marketing uses a different content model. The customer's marketing team rebuilds campaigns in Dynamics 365 Marketing or the preferred email tool.