Migrate from BSI CRM to Microsoft Dynamics 365 Sales

BSI CRM User records migrate first because every other object references an owner. We match by email against the destination Dynamics 365 User table. Users without a matching Dynamics 365 User are held in a reconciliation queue for the customer's admin to provision before record import proceeds. Role and permission sets are documented for the admin to reapply post-migration.

BSI Contact records map to Dynamics 365 Contact. Standard fields (name, email, phone, title, address) transfer directly. Custom fields on BSI Contact require pre-migration schema discovery to enumerate and must be created as custom fields in Dynamics 365 before the Contact import runs. BSI does not publish a self-service export mechanism for custom fields; we request the full field inventory during discovery.

BSI Company records map to Dynamics 365 Account. Hierarchical parent-child structures in BSI map to the Account.ParentAccountId relationship. Industry classification fields from BSI map to the Industry picklist or custom fields in Dynamics 365. The Account record must be created before any Contact import to satisfy the AccountId lookup on Contact.

BSI Deal records map to Dynamics 365 Opportunity. The Deal's pipeline stage name maps to a Dynamics 365 StageName, but because BSI's pipeline stages vary by industry module configuration, we map each distinct BSI pipeline to a Dynamics 365 Record Type with a corresponding Sales Process that defines the allowed stage values. Deal value maps to Amount; expected close date maps to CloseDate; owner maps to OwnerId via the User lookup.

Each BSI deal pipeline maps to a Dynamics 365 Record Type on Opportunity, with a Sales Process that whitelists the relevant stage values and probabilities. Stage probability percentages transfer from BSI to the Sales Process stage probabilities with rounding to the nearest integer allowed by Dynamics 365.

BSI Activities (logged calls, emails, meetings, and tasks linked to Contacts or Deals) map to Dynamics 365 Task, Event, and EmailMessage records. Call activities map to Task with TaskSubtype = Call; email activities map to EmailMessage linked to a Task; meeting activities map to Event. We preserve the parent record linkage by resolving the Contact or Deal reference to Dynamics 365 WhoId and WhatId at migration time. Activities are loaded via Dynamics 365 Bulk API due to volume. Historical timestamps are preserved as ActivityDate or ScheduledStart on the destination records.

BSI CRM supports custom objects and fields within its modular architecture, but the schema is not published in a self-service format accessible to migration tooling. We perform a manual discovery phase to enumerate all custom object names, field definitions, data types, and record counts before designing the migration schema. Destination custom entities are provisioned in Dynamics 365 Dataverse before any data import. Custom object relationships that reference standard objects (Contact, Account, Opportunity) require the lookup target to be loaded first. This discovery step is migration-critical and must complete before scope is confirmed.

File attachments associated with Contacts, Deals, or Activities are exported from BSI individually and reattached to their parent record in Dynamics 365. If the destination Dynamics 365 org uses SharePoint document management (a common configuration for organizations with Microsoft 365), attachments migrate to SharePoint libraries linked via Dynamics 365 document locations. The migration path is determined during discovery based on the customer's SharePoint configuration.

BSI CRM tagging and custom classification fields may not have a direct Dynamics 365 equivalent. We capture these as Dynamics 365 custom multi-select or single-select picklist fields on the appropriate entity. Any tag values that exceed the Dynamics 365 picklist value length or format constraints are flagged and mapped to a text field as a fallback. The customer chooses the tag strategy during scoping.