Migrate from Bluwave CRM to Twenty CRM

Bluwave Contact records map to Twenty People. We extract name, email, phone, address, and the geocoded latitude/longitude values as custom number fields in Twenty. Picklist values for contact status or type are inferred from sampled content and mapped to Twenty's select field options, which we create in Settings → Data Model before import. Owner assignment maps to Twenty's workspace Member by email match.

Bluwave Lead records (distinct from Contacts in Bluwave) map to Twenty People with a lead_source select field capturing the original lead attribution. If the customer uses a qualification lifecycle, we create a select field for lead_stage in Twenty and preserve the original Bluwave lifecycle value. The decision to merge Leads into existing People records vs. creating separate People records is made during scoping based on the customer's deduplication policy.

Bluwave Company records map directly to Twenty Company. The company name, industry, and address fields migrate to Twenty's equivalent Company fields. Twenty Company records are created before People import so that the company-people relationship is resolved at the point of People insert. Company is the deduplication anchor for incoming People records that have a matching company association.

Bluwave Deals map to Twenty Opportunity. Deal value, stage name, expected close date, and owner assignment transfer to Twenty's equivalent Opportunity fields. The pipeline stage name maps to a stage picklist in Twenty that we configure before migration. Orphaned Deals (where the associated Contact or Company has been deleted in Bluwave) are flagged for the customer to resolve before import because Twenty Opportunity requires a linked Company or Person.

Bluwave pipeline stages are exported from the pipeline configuration module. We reconstruct the stage names and probability percentages as Opportunity stage picklist values in Twenty's Settings → Data Model before importing Deals. Stage order is preserved as the picklist option sequence. If Bluwave uses multiple pipelines, we document the pipeline-to-Record-Type mapping for Twenty configuration during setup.

Bluwave face-to-face activities map to Twenty Task. Activity type picklist values (call type, meeting type, etc.) are inferred from sampled export data and created as select options in Twenty's Task object. The geocoded latitude and longitude stored against Bluwave activities migrate to custom number fields on Twenty Task. We set Task status to the original Bluwave activity status and preserve the original activity date for timeline ordering. Meetings with start and end timestamps map to Twenty Task with a time field if the customer's workflow requires them.

Bluwave custom fields have no public schema reference, so we audit field names and data types during scoping by exporting sample records and inferring types from content patterns. We create matching custom fields in Twenty's Settings → Data Model before any data import, using the inferred type (text, number, date, select, multi-select, etc.). Validation errors from misidentified field types are caught during batch testing before the full load commits.

Bluwave User records (name, email, role) map to Twenty Members. Owner assignment on Deals and Activities resolves by email match against the Twenty Member table. Any Bluwave Owner without a matching Twenty Member is held in a reconciliation queue; the customer's admin provisions missing Members before record import resumes. Role hierarchies do not transfer and must be rebuilt in Twenty's workspace permissions.

Binary file attachments on Bluwave Deals and Contacts do not export via the Excel export method. We extract accessible file attachments separately via the Bluwave web interface where possible and either upload them directly to Twenty post-migration (as linked files on the record) or store them in the customer's chosen document store with a URL field added to the Twenty record. File attachment history is inventoried in the migration scope but cannot be loaded programmatically without a Bluwave API.

Bluwave mail list segments and their member associations migrate as a custom select field on Twenty People, with each member receiving the list name as a field value. We do not migrate email campaign history or delivery receipts. If the customer uses multiple mail lists, we create a multi-select field in Twenty that captures all applicable list memberships per Person record.