Migrate from Bluwave CRM to Microsoft Dynamics 365 Sales

Bluwave CRM Contact records map directly to Microsoft Dynamics 365 Contact. Standard fields (full name, email, phone, postal address) migrate without transformation. The geocoded latitude/longitude values appended at address entry in Bluwave are preserved as custom decimal fields on the Dynamics Contact record for post-migration review; we flag these to the customer because they are forward-geocoded approximations, not GPS captures. We validate email format and uniqueness before insert to catch duplicates that Excel export does not surface.

Bluwave CRM Lead records (distinct from Contacts in the Bluwave data model) map directly to Dynamics 365 Lead. Lead source attribution, lifecycle stage values, and any scoring custom fields migrate as custom fields on the Dynamics Lead. We infer the picklist values from exported content during the scoping phase because Bluwave does not publish a field schema reference.

Bluwave CRM Company records map to Microsoft Dynamics 365 Account. Company name, industry classification, annual revenue, number of employees, and address fields transfer directly. Account is inserted before Contact records to satisfy the parent AccountId lookup requirement on the Contact object during import.

Bluwave CRM Deals map to Dynamics 365 Opportunity. Deal value maps to EstimatedRevenue, expected close date maps to EstimatedCloseDate, and owner assignment maps to OwnerId via email-matched User resolution. The pipeline stage name maps to the StageName field against the Sales Process we configure before migration. Deals without an associated Contact or Company are flagged as orphaned and held in a reconciliation queue.

Bluwave CRM's configurable pipeline stages are extracted by exporting the pipeline settings module. Each stage name becomes a Dynamics 365 Opportunity Stage value within a Sales Process that we provision during the destination schema phase. Probability percentages from Bluwave transfer as probability values on each stage. We validate that stage names do not exceed Dynamics' 30-character limit before creation.

Bluwave CRM Activities (including geocoded face-to-face visits linked to travel claims) map to Dynamics 365 Task for tasks and calls, and Event for scheduled meetings. Activity type picklist values require explicit mapping during scoping because Bluwave's picklist schema is not publicly documented. We sample exported activities to build the type mapping before the production migration run. Geocoded location values on face-to-face activities migrate as custom fields on the Dynamics Task record.

Bluwave CRM User records (name, email, role) map to Microsoft Dynamics 365 User records by email match. We extract all distinct owner references from Deals, Contacts, and Activities and cross-reference against the destination Dynamics org's User table. Any Bluwave owner without a matching Dynamics User is placed in a reconciliation queue; the customer's admin provisions the missing User before record import resumes.

Bluwave CRM Mail List segments are migrated as Dynamics 365 Marketing List records with member Contact and Lead associations preserved. We do not migrate email campaign history or engagement metrics; these have no equivalent in Microsoft Dynamics 365 Sales and would require rebuilding in Dynamics 365 Marketing or an email marketing platform post-migration. The segment definition and current member list transfer as a static list.

Bluwave CRM custom fields are supported but have no published schema reference. We audit custom field names and infer data types by sampling exported records during the scoping phase. Custom fields that do not map to a standard Dynamics field type are created as Text fields in Dynamics 365 with a note in the migration guide for the customer's admin to re-type as needed. This prevents validation failures on import that would result from mis-identified field types.