Migrate from Bluwave CRM to Zoho CRM

Bluwave Contact records map to Zoho CRM Contacts with standard field correspondence: Full Name, Email, Phone, Mobile, Physical Address. The geocoded latitude/longitude appended at address entry in Bluwave migrates as two Zoho CRM multi-line custom fields (Latitude and Longitude) stored against the Contact record. We validate picklist values for Contact Type, Source, and any custom picklists by inferring types from sampled Bluwave export data before finalising the mapping.

Bluwave Lead records (distinct from Contacts in Bluwave's data model) map to Zoho CRM Leads. Source attribution fields, lifecycle stage values, and lead score equivalents migrate as Zoho custom fields. Lead Owner maps to Zoho CRM User by email match. We flag any Bluwave Leads that reference a Company record without a matching Account in the destination so the customer can resolve the linkage before cutover.

Bluwave Company records map to Zoho CRM Accounts. Company Name, Industry, Website, Physical Address, and Billing Address fields migrate directly. Account is created before any Contact import so that the Account-Contact lookup is satisfied at the moment of Contact insert. Bluwave's Company-Contact association (one Company to many Contacts) maps to Zoho's standard Account-to-Contact lookup relationship.

Bluwave Deals map to Zoho CRM Deals. Deal Name, Value (Amount), Expected Close Date, Stage, Owner, and associated Contact and Company references migrate directly. The Bluwave pipeline stage name maps to Zoho's Stage field, which we configure during the pipeline setup phase. We preserve the original Bluwave stage order and probability percentages in Zoho custom fields for reporting continuity.

Bluwave's configurable pipelines map to Zoho CRM Pipelines and Stages. We extract the current stage names and reorder logic from the Bluwave export and reconstruct the pipeline structure in Zoho CRM before Deal import. Each Zoho Stage is assigned a probability percentage matching the Bluwave original, and stages are ordered to reflect the sales process flow. If Bluwave has multiple pipelines, we create corresponding Zoho CRM Pipelines and assign them to Zoho CRM users during migration.

Bluwave face-to-face activities carry geocoded location data and optionally link to travel claim reports. We migrate them as Zoho CRM Events (for scheduled meetings) or Tasks (for completed activity logs) with the Bluwave geocoded coordinates stored in custom Event/Task fields. Activity type picklist values from Bluwave are mapped to Zoho Task Status and Event Type picklists. The parent Contact or Company lookup is resolved before insert.

Bluwave call logs and note entries migrate as Zoho CRM Tasks. Call duration and disposition are stored as custom Task fields. Note content migrates as Task Description. Owner assignment resolves via email match to Zoho User. We preserve the original Bluwave activity timestamp in Zoho's Activity Date field for timeline ordering.

Bluwave User records (name, email, role) map to Zoho CRM Users. We resolve by email match. Any Bluwave Owner referenced on a Deal, Contact, or Activity without a matching Zoho User is held in a reconciliation queue for the customer's admin to provision before that phase of migration begins. Bluwave role hierarchies are not exportable and must be rebuilt in Zoho CRM Roles and Profiles.

Bluwave CRM supports custom fields but publishes no field names, data types, or picklist values in any public reference. During scoping we export sample records and infer field types from content patterns (date formats, numeric vs text, picklist delimiters). We create equivalent custom fields in Zoho CRM (Custom Fields module and per-module custom fields) before migration, using the inferred types as the target schema. We validate with a 50-record test batch before committing the full load because any misidentified field type causes validation failures in Zoho's API.

Bluwave file attachments on Deals and Contacts do not export via the Excel export method. We extract these separately where accessible via the web interface. Each attachment is linked to its parent Contact, Company, or Deal record in Zoho CRM using Zoho's attachment API. Binary attachments that cannot be accessed through the web interface are flagged in the scoping report for manual handoff.

Bluwave mail list segments and their member Contact associations migrate as Zoho CRM Campaigns (with Campaign Type = Email List) and Campaign Member records linked to the corresponding Contact records. We note that email campaign send history, open rates, and click data do not transfer; only the segment definition and membership list migrate. The customer's admin rebuilds the email send history in Zoho Campaigns or Zoho Marketing Automation post-migration.