Migrate from Bolten CRM to Microsoft Dynamics 365 Sales

Bolten Contacts with a lifecycle status of unqualified or prospect map to Salesforce Lead; contacts with qualified status map to Microsoft Dynamics 365 Contact attached to an Account. We compute the split using Bolten's lifecycle status property at migration time and preserve the original status value in a custom field on both the Lead and Contact records. The Account must be created before Contact import so that the AccountId lookup relationship is satisfied at insert time.

Bolten Leads map directly to Dynamics 365 Lead records. Lead status, owner assignment, and source campaign attribution migrate as standard Lead fields. Any Bolten lead-scoring value stored in a custom field is preserved in a custom field on the Dynamics Lead for the customer's admin to map into Dynamics lead scoring if needed.

Bolten Deals map to Dynamics 365 Opportunity. The Bolten Kanban stage name maps to a Dynamics Opportunity stage value that we configure as part of the pre-migration stage-sequencing design. Probability percentages are written from Bolten to Dynamics StageProbability. Deal value, close date, owner, and linked contact association migrate with the Opportunity. Closed-Won and Closed-Lost reason custom fields from Bolten become Dynamics Loss Reason and Win Reason fields.

Bolten Kanban stage names carry no ordinal property in the API. During pre-migration scoping, we request explicit stage ordering from the customer and write an ordinal position value to each stage in Dynamics. Each Bolten pipeline maps to a Dynamics Opportunity Record Type with its own Sales Process containing stage values in the confirmed sequence with probability percentages preserved from Bolten.

Bolten Tasks map directly to Dynamics 365 Task records. Assignee, due date, status, priority, and linked contact or deal association migrate intact. Recurring task rules do not transfer; we flag them in the deliverable for the customer's admin to rebuild in Dynamics.

Bolten Activities log every record change (edits, assignments, stage moves) with timestamps and operator attribution. Dynamics 365 has no equivalent audit-activity object, so each Bolten activity entry is transformed into a separate Task record with Subject, Description, ActivityDate, and CreatedBy populated from the original Bolten log. The Task's WhoId and WhatId are resolved to the migrated Contact and Opportunity respectively. We count total activity entries during scoping and flag this to the customer if it exceeds 50 entries per record, since it significantly affects migration duration.

Bolten custom fields on each object map to custom fields on the corresponding Dynamics entity. We convert field types where possible: Bolten dropdown becomes OptionSet, multi-select becomes MultiSelectOptionSet, date stays DateTime. Custom fields with no matching Dynamics target are flagged during scoping for the customer's admin to either create in the destination schema or archive. This mapping is dependent on a pre-migration schema review of both systems.

Bolten tags are flat-label strings applied to Contacts and Deals. We migrate tag sets as a semicolon-delimited custom text field on the corresponding Dynamics entity, or as a multi-select option set field if the destination schema supports it. The tag relationship per record is preserved so that reporting by tag can be rebuilt in Dynamics after migration.

WhatsApp message history lives on Meta's infrastructure, not Bolten's database. The full conversation content cannot be migrated through our pipeline. We preserve contact phone numbers and conversation metadata as Activity records so that the existence and timing of WhatsApp conversations is not fully lost, but live WhatsApp message threads require a separate Meta data-portability request outside our scope.

Bolten users identified by email and name map to Dynamics 365 User records. During pre-migration, the customer admin provisions all active Bolten users in Dynamics 365 so that migration can resolve OwnerId on Contact, Opportunity, and Task records. Owners without a matching Dynamics User are held in a reconciliation queue for the admin to provision before record import resumes. Suspended or inactive Bolten users are flagged for remapping to an active Dynamics user.

Bolten tracks lead origin and real-time conversion events (Google, Meta Ads, direct) as Conversion records. We migrate conversion records and attribution data to Dynamics 365, mapping UTM values to a custom field for the customer's admin to rebuild in Dynamics reporting. If the destination org includes Dynamics 365 Customer Insights - Journey, attribution data maps there instead as a parallel scope.