Migrate from Bluwave CRM to Salesforce Sales Cloud

Bluwave CRM does not distinguish between Leads and Contacts; all prospect records are Contact objects. We apply a split rule during migration: Bluwave CRM Contacts with no associated Deals and no opportunity attachment map to Salesforce Lead; Contacts with an active Deal or a closed-won record map to Salesforce Contact attached to an Account. We preserve the original Bluwave CRM record ID in a custom field bluwave_record_id__c on both Lead and Contact for cross-system audit. Any Bluwave CRM custom picklist values on contact status fields are mapped to Salesforce Lead Status or Contact source fields before import.

Bluwave CRM Company records map directly to Salesforce Account. The Company name maps to Account Name and serves as the dedupe key during import. Industry, website, and address fields map to their Salesforce Account equivalents. Account is created before Contact import so that the AccountId Lookup relationship is satisfied at the moment of Contact insert. Companies with multiple associated Contacts in Bluwave CRM result in one Account per Company with multiple Contact records linked via the Account Lookup.

Bluwave CRM Deals map to Salesforce Opportunity. Deal value maps to Amount, expected close date maps to CloseDate, owner maps to OwnerId via the User reconciliation step, and the Bluwave CRM pipeline stage maps to the Salesforce StageName under the Sales Process we configure before migration. Closed-won and closed-lost Deals carry their original stage to preserve historical pipeline reporting in Salesforce.

Each Bluwave CRM pipeline's stage names are extracted during scoping and mapped to Salesforce StageName values under a new Sales Process. Stage probability percentages from Bluwave CRM migrate to StageProbability in Salesforce with rounding to the nearest integer. We configure the Sales Process in a Salesforce Sandbox first and validate the stage sequence with the customer's sales ops lead before production migration.

Bluwave CRM supports one pipeline per organisation with configurable stages. If the customer has used pipeline stages to represent different lines of business, we map each distinct stage set to a Salesforce Record Type on Opportunity, paired with a dedicated Sales Process that scopes StageName values per line. Page Layout assignments per Record Type are configured in the destination org before migration.

Bluwave CRM activities (calls, emails, meetings, tasks) map to Salesforce Task (TaskSubtype = Call for phone calls) and Event objects. Activity type picklist values require explicit mapping as Bluwave CRM's picklist schema is not published publicly; we infer the mapping from exported data during scoping. Geocoded latitude/longitude from face-to-face activities migrate as custom fields latitude__c and longitude__c on Task, flagged as forward-geocoded approximations rather than GPS captures. Parent record linking (WhoId and WhatId) is resolved by matching the associated Contact or Deal record ID to the migrated Salesforce ID.

Bluwave CRM pipeline stage names and reorder logic are extracted during scoping and reconstructed as Salesforce Sales Processes. Stage probability weights migrate to StageProbability on each stage entry. The Sales Process is associated with the relevant Opportunity Record Type before Deals are imported.

Bluwave CRM User records (name, email, role) are extracted and matched to Salesforce Users by email address during the Owner reconciliation step. Any Bluwave CRM Owner without a matching Salesforce User is held in a reconciliation queue for the customer's admin to provision before Deal and Activity import resumes, because OwnerId references are required on most standard Salesforce objects.

Bluwave CRM Mail List segments migrate to Salesforce Campaign records, with the segment member contacts mapped to CampaignMember records linked to the corresponding Campaign. The customer chooses whether to create one Campaign per list or consolidate into a single Campaign with list-name tagged in a custom field. Email campaign send history, open rates, and click data do not transfer as these are transient engagement metrics not stored in Bluwave CRM record fields.

Bluwave CRM custom field names and data types are inferred during scoping by sampling exported data and validating content patterns against expected formats. We pre-create all destination custom fields in Salesforce (with appropriate field types: Text, Number, Picklist, Date, Checkbox) before any data import. Misidentified field types discovered during batch validation trigger a schema correction cycle before the full load commits.

Binary file attachments on Deals and Contacts do not export via Bluwave CRM's Excel export. We extract these separately through the web interface where accessible and load them into Salesforce as ContentVersion records, then link them via ContentDocumentLink to the parent Contact, Account, or Opportunity. Attachment count and a list of accessible files are documented in the scoping report; inaccessible files (due to permission restrictions or deleted records) are flagged for manual handoff.

Bluwave CRM Lead records (distinct from Contacts, sourced from website real-time capture) map directly to Salesforce Lead. Lead source attribution and lifecycle stage from Bluwave CRM migrate to LeadSource and a custom field bluwave_lifecycle_stage__c on the Salesforce Lead for audit continuity.