Migrate from Bluwave CRM to Pipedrive

Bluwave CRM Contact records map to Pipedrive Person objects. We preserve the name, email, phone, address, and geocoded lat/long as custom properties in Pipedrive. Picklist values for contact type or source require explicit mapping during scoping because Bluwave's picklist schema is not publicly documented. If a Contact has no associated Company in Bluwave, it imports as a standalone Person with no Organisation link.

Bluwave Leads migrate to Pipedrive Leads. Lead source attribution and lifecycle stage status from Bluwave map to Pipedrive's Lead label and Custom fields. We preserve any Bluwave lead scoring value as a custom numeric field in Pipedrive. If Bluwave's lead lifecycle distinguishes between marketing-qualified and sales-qualified stages, we document the mapping during scoping.

Bluwave Company records map to Pipedrive Organisation. The company name, industry, and address fields migrate directly. Organisation is created before Contact import so that the Organisation-Person relationship is satisfied at insert time. Bluwave's geocoded address data on Companies migrates as custom lat/long fields on the corresponding Organisation.

Bluwave Deals map to Pipedrive Deals. Deal value, stage name, expected close date, and owner assignment migrate. We resolve the owner by email match against Pipedrive Users before inserting Deals. The Bluwave pipeline association determines which Pipedrive Pipeline the Deal is assigned to. If a Deal in Bluwave has no associated Contact (orphaned), it imports as a Deal with no Person or Organisation link and is flagged for admin review.

Bluwave Activities (calls, meetings, tasks, face-to-face visits) migrate to Pipedrive Activities. Activity type picklist values require explicit mapping at migration time because Bluwave's picklist schema is not published. The geocoded location on face-to-face Bluwave activities migrates as a custom property on the Pipedrive Activity. We set the Activity timestamp to the original Bluwave date to preserve the activity timeline ordering.

Bluwave Pipeline stages reconstruct as Pipedrive Pipeline stages in the configured order. We extract the stage names and their sequence from Bluwave during scoping and create the matching Pipedrive stages before any Deal import. Probability values from Bluwave (if stored) migrate as stage success probability percentages in Pipedrive. Stage colours are assigned during Pipedrive setup and do not carry over from Bluwave.

Bluwave custom fields migrate to Pipedrive custom fields with type inference during scoping. We sample exported data to determine whether a field is text, numeric, date, or picklist. Any picklist fields in Bluwave require manual value mapping during scoping because the picklist options are not documented. We create Pipedrive custom fields before any record import to avoid import failures from missing field targets.

Bluwave User records map to Pipedrive Users. We resolve by email match. Any Bluwave Owner without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Bluwave role hierarchy does not export and is not migratable; Pipedrive permission sets and role configurations must be rebuilt post-migration.

Bluwave Mail List segments migrate as Pipedrive Lists. We extract the segment definition (criteria that defines membership) and the member Person records. Email campaign history and engagement metrics (open rates, click rates) do not transfer as these are not stored in Bluwave's contact records. The customer's admin rebuilds campaign sequences in Pipedrive's Campaigns feature or a connected email tool.

Binary file attachments on Deals and Contacts in Bluwave do not export via Excel. We access attachments through the web interface where accessible and migrate them as Pipedrive Files linked to the parent Deal or Person record. If a file is stored in a Bluwave document management area with no web-accessible link, we flag it for manual download and re-upload.