Migrate from Bluwave CRM to HighLevel

Bluwave CRM Contact records map to GoHighLevel Contact. Standard fields (name, email, phone, address) migrate directly. The geocoded latitude and longitude appended by Bluwave at address entry transfer as GoHighLevel Custom Fields (text type storing the numeric values). We validate coordinate format during the batch audit phase. Any Bluwave Contact picklist values (source, status) map to GoHighLevel Contact tags or custom dropdown fields. Records without an email address are flagged in the reconciliation report because GoHighLevel's import validation requires a contact identifier.

Bluwave CRM separates Leads from Contacts, with Leads capturing unqualified prospects and Contacts representing engaged buyers. At migration time we assess the Lead's last activity date and lifecycle stage in Bluwave to decide whether it should land as a GoHighLevel Contact with a Lead tag or remain as a separate pipeline entry. The customer chooses the split rule during scoping. We preserve the original Bluwave lead source attribution as a custom field on the GoHighLevel Contact.

Bluwave CRM Company records store business name, industry, address, and phone. In GoHighLevel, the primary company context is the Contact's company name field. If the customer has multiple Bluwave Companies with shared contacts, we map each to a separate GoHighLevel Contact entry with the company name field populated and the address stored on the Contact. GoHighLevel's Location concept is not a separate record type but a field grouping on Contact.

Bluwave CRM Deals map to GoHighLevel Opportunities. We preserve deal value, stage name, expected close date, owner assignment, and any custom deal fields. Bluwave pipeline stages map to GoHighLevel pipeline stage names, with stage ordering reconstructed from Bluwave's stage reorder settings. Orphaned deals (parent contact deleted in Bluwave) are flagged for the customer's review before import; GoHighLevel requires a Contact association on Opportunities.

Bluwave CRM's single configurable pipeline with named stages reconstructs as a GoHighLevel Pipeline with the same stage names and order. We capture the stage probability and win/loss flag from Bluwave's stage configuration and apply them to the GoHighLevel Pipeline settings. If the customer uses multiple named pipeline views in Bluwave, we create corresponding GoHighLevel Pipelines.

Bluwave CRM Activities (face-to-face visits, calls, notes) map to GoHighLevel Tasks. Activity type picklist values (call, meeting, note) are inferred from the exported data and mapped to the closest GoHighLevel Task category. Geocoded location stored on face-to-face activities transfers as a custom text field. Activity timestamps and owner assignments migrate directly. Note body content migrates as a GoHighLevel Task note or as a separate Contact note.

Bluwave CRM supports custom fields but publishes no field name or data type schema. We audit exported records during scoping, infer field types from content (text, number, date, picklist), and create matching GoHighLevel Custom Fields under Settings > Custom Fields for the relevant object before migration. Type mismatches detected during the batch audit trigger a mapping correction. Picklist values are created as GoHighLevel dropdown options matching the Bluwave source values.

Bluwave CRM Excel exports do not include binary attachments. We extract files accessible via the web interface separately and associate them with the corresponding GoHighLevel Contact or Opportunity record. Files without a retrievable URL in Bluwave are listed in the gaps inventory for the customer to handle manually post-migration.