Migrate from Bluwave CRM to Freshsales

Bluwave CRM Contact records map to Freshsales Contact. Standard fields (first_name, last_name, email, phone, address) map directly. The geocoded latitude and longitude appended at address entry migrate as custom properties (latitude_c, longitude_c) on the Contact record. We validate email format, normalise phone number formats, and deduplicate on email address before insert.

Bluwave CRM Lead records map to Freshsales Lead. Source attribution and lifecycle stage from Bluwave CRM migrate as custom properties on the Freshsales Lead (lead_source_c, bluwave_lifecycle_stage_c). Freshsales Lead fields map to Contact and Account during conversion, so we configure the field mapping in Freshsales Admin settings before migration to prevent data loss on conversion.

Bluwave CRM Company records map to Freshsales Account. Company name, industry, and address fields migrate directly. Multiple Contacts can associate to one Account in Freshsales, preserving the one-to-many relationship that Bluwave CRM supports. We create Accounts before Contact import to satisfy the lookup dependency.

Bluwave CRM Deals map to Freshsales Deals. Deal value, stage name, expected close date, and owner assignment migrate directly. We map Bluwave CRM pipeline stages to Freshsales deal stages, and configure stage probability values in Freshsales Admin settings before import. Orphaned deals (deal with no associated Contact) are flagged for the customer to resolve before final import.

Bluwave CRM face-to-face activities with geocoded location and travel claim associations map to Freshsales Task records with custom fields for location data (location_latitude_c, location_longitude_c, travel_claim_reference_c). Activity type picklist values are inferred from sampled data during scoping and mapped to Freshsales activity types (Meeting, Call, Task) before import. We preserve the original activity timestamp as ActivityDate.

Bluwave CRM pipeline stages (configurable per organisation) map to Freshsales deal stages. We extract the current stage names and probability percentages from the Bluwave CRM export, then configure Freshsales deal stages in Admin settings to match before migration. Stage ordering and probability percentages are preserved in the Freshsales stage configuration.

Bluwave CRM custom fields have no published schema reference. We export a sample of records during scoping, infer field names and data types from content, and build a mapping guide before the full load. Picklist values require explicit mapping because the platform's picklist schema is not documented. We validate with a batch of 50 records before committing the full import to catch misidentified field types.

Bluwave CRM User records (name, email, role) map to Freshsales User records. Owner assignment on Deals and Activities resolves by email match against Freshsales Users. Bluwave CRM role hierarchies are not exportable and must be rebuilt in Freshsales Admin settings post-migration. Any Bluwave CRM Owner without a matching Freshsales User goes to a reconciliation queue for the customer's admin to provision.

File attachments on deals and contacts do not export via Bluwave CRM's Excel export. We extract binary attachments separately via the web interface where accessible and upload them to Freshsales as Attachments linked to the parent Contact, Account, or Deal record. Attachment migration is performed last after parent records are confirmed in Freshsales.