Migrate from Bluwave CRM to HubSpot

Bluwave contacts map 1:1 to HubSpot contacts. Email serves as the primary identifier for deduplication — if a contact with the same email already exists in HubSpot, FlitStack flags it for manual merge decision before the full run. This ensures no duplicate records are created unintentionally.

Bluwave company records map to HubSpot companies. Domain matching is used to associate contacts with companies automatically after migration — contacts without a matching company link to an 'Unassigned' company record for manual review and proper linking.

Bluwave deals map to HubSpot deals. Since HubSpot supports multiple pipelines, FlitStack maps Bluwave's single pipeline to one HubSpot pipeline by default; if your Bluwave setup uses deal categories to simulate multiple pipelines, we discuss pipeline-splitting during the discovery phase.

Bluwave deal stages map to HubSpot deal stages on a value-by-value basis. Each Bluwave stage name is matched to the closest HubSpot stage; if HubSpot stages do not exist yet, we create them during the migration setup phase. Stage probability values are preserved as HubSpot stage probability settings.

Bluwave owner records are resolved to HubSpot owners by email address matching. If a Bluwave owner email matches a HubSpot user email, the OwnerId links correctly. Unmatched owners are flagged before migration — your team either creates HubSpot users for them or assigns their records to a fallback owner.

Bluwave call logs map to HubSpot engagement calls. Original call timestamps, duration, outcome, and associated contact/company links are preserved. Call metadata (if Bluwave exports it) maps to HubSpot call properties such as disposition, recording link if available, and any custom call-related fields.

Bluwave email records map to HubSpot engagement emails. Subject, body (plain text or HTML), timestamp, sender, and recipient are preserved. Associated contact/company records link automatically via email address matching after the migration completes.

Bluwave meeting records map to HubSpot engagement meetings. Start time, end time, title, location, and associated contacts and companies are preserved. Meeting outcome notes and attendee details map to the corresponding HubSpot meeting properties.

Bluwave notes map to HubSpot engagement notes. Note body text, timestamp, and owner are preserved. Notes linked to specific records in Bluwave attach to the corresponding HubSpot contact, company, or deal record after migration.

Bluwave contact custom fields that do not map to native HubSpot contact properties become HubSpot custom properties. We create these before migration runs so field-level diff can validate the mapping. Enterprise-tier accounts can use HubSpot custom objects for complex multi-property data.

Bluwave deal custom fields map to HubSpot deal custom properties. Each custom field is assessed for type compatibility — pick-list values become HubSpot option sets, numeric fields map to number properties, and dates map to date properties for proper data formatting.

Bluwave file attachments are downloaded and re-uploaded to HubSpot Files. Files linked to contacts, companies, or deals attach to the corresponding HubSpot records. HubSpot's 115MB file size limit applies to all uploads; files exceeding this threshold are flagged for manual handling.

If Bluwave stores product or service items linked to deals, these map to HubSpot line items. Line items require a corresponding HubSpot product record — we create a placeholder product record for each unique item so line item associations on deals are preserved.

Bluwave's internal record ID is stored on each HubSpot record as a custom property for traceability. This ID enables delta-run deduplication (if a record is modified in Bluwave after initial migration, the ID allows FlitStack to match and update the correct HubSpot record).