Migrate from Levitate to Microsoft Dynamics 365 Sales

Levitate Contacts with no associated deal or pipeline belong in Microsoft Dynamics 365 Sales as Leads by default. Contacts that have a clear organizational parent (company name, agency name, firm name) map to Account first, then Contact linked to that Account. We split the migration at discovery: contacts with a non-empty company field go to Account-Contact; contacts without go to Lead. The split rule is confirmed with the customer before import, and any Levitate Key Date fields migrate as custom Date fields on the target record.

Levitate Tags are a flat or hierarchical segmentation taxonomy stored as a multi-select property per contact. Microsoft Dynamics 365 Sales has no native tag field. We create a custom Multi-Select Picklist field (tag_names__c) on the Contact or Lead object to hold the full tag assignment per record, or a related custom Tag Assignment entity if the tag taxonomy exceeds 50 unique values. The customer selects the approach during scoping. We preserve the full tag taxonomy in the migration inventory so downstream segmentation can be rebuilt in Dynamics 365 views or Power Automate.

Levitate Key Dates (birthday, policy_renewal_date, custom age milestones) are a Levitate-native field type that drives date-triggered automations. Dynamics 365 has no equivalent trigger type. We create matching custom Date fields in Dynamics 365 (birthday__c, policy_renewal_date__c, and any customer-specific variants) before contact import, and migrate all Key Date values as typed Date data. Date-triggered automations from Levitate do not fire in Dynamics 365 without a rebuild as Power Automate flows or scheduled Flows, which we document in the automation handoff inventory.

Levitate Company records (agency, firm, or organizational name) map to Dynamics 365 Account. The Company name becomes Account Name, and the Levitate contact's company field is used as the dedupe key during import. Account is created before any Contact import so that the AccountId Lookup is satisfied at insert time. If Levitate has no Company records, the Contact-Account split is resolved using the company name on the Contact record itself.

Levitate Campaigns (email group sends with engagement tracking) map to Dynamics 365 Campaign records with CampaignMember linking contacts to the campaign. Campaign name, send date, and aggregate engagement stats (total sent, opens, clicks) migrate as Campaign properties. Individual email engagement events per contact (open timestamp, click URL) are not bulk-exportable from Levitate and are noted as a gap; we migrate the last_engagement_date as a contact property where available.

Levitate engagement history (calls logged, meetings scheduled, tasks created, notes attached) migrates to Microsoft Dynamics 365 Sales as Activity records. Emails and calls migrate as Task with TaskSubtype (Call or Email). Meetings migrate as Event with StartDateTime and EndDateTime preserved. Notes migrate as Note records linked via ContentDocumentLink. Levitate does not expose a bulk export of individual engagement events — we migrate available records from the contact export supplemented by Levitate Support data requests, and flag the gap in the engagement completeness disclosure.

Levitate SMS message threads stored per contact are migratable as Note records or custom activity entries in Dynamics 365. Levitate's export capability for SMS logs is limited to the contact's recent message thread view, and deep thread history may not be available for bulk export. We migrate available SMS content and flag any gaps during the engagement completeness disclosure.

Levitate user accounts (Owner, Admin, Member roles) are mapped to Dynamics 365 User records by email address. Role definitions and permission scopes are not exportable from Levitate. We flag that Dynamics 365 User roles, security roles, and sharing rules must be configured by the customer's admin after migration. Any Levitate Owner without a matching Dynamics 365 User is held in a reconciliation queue.