Migrate from Bluwave CRM to Nutshell

Bluwave Contact records map directly to Nutshell Person. Standard fields (name, email, phone, address) map to Nutshell's standard Person fields. The geocoded latitude and longitude stored against the contact's address migrate as a custom Lat/Lng property pair in Nutshell. Bluwave's contact type picklist (if used) maps to a Nutshell custom picklist field. We validate email uniqueness in Nutshell before insert to avoid duplicate Person records for contacts sharing an email address.

Bluwave Lead records map directly to Nutshell Lead, preserving the source attribution, lifecycle stage (if present), and owner assignment. The Bluwave lead source field maps to Nutshell's standard Lead Source picklist. Owner resolution runs by email match against Nutshell User records. Any Lead without a matching User goes to a reconciliation queue for manual provisioning before the import phase begins.

Bluwave Company records map to Nutshell Company. Company name, industry, website, and address fields migrate to their Nutshell equivalents. Company is imported before Person records so that the Company lookup relationship on Person resolves correctly at insert time. Dedupe is performed on Company name during import to avoid creating duplicate Company records.

Bluwave Deals map to Nutshell Opportunities. The deal value maps to Amount, stage name maps to Status, expected close date maps to Close Date, and owner maps by email resolution to the Nutshell User. The parent Contact and Company associations migrate as Person and Company lookups on the Opportunity record. Closed-Lost and Closed-Won statuses from Bluwave map to Nutshell's Won and Lost status values.

Bluwave pipeline stages are configurable per organisation. We extract the current stage names and order from the exported data, then pre-create matching stages in Nutshell's pipeline configuration before Deal import begins. Probability percentages associated with each stage in Bluwave are not natively stored but can be mapped to Nutshell stage probabilities if the customer provides the mapping during scoping.

Bluwave face-to-face activities (calls, meetings, site visits) map to Nutshell Activity records. Activity type picklist values require explicit mapping at migration time because the Bluwave picklist schema is not publicly documented. We infer the type from the exported activity records and create matching Activity type values in Nutshell before import. Geocoded location attached to the activity is preserved as a custom property. Activity assignment migrates by resolving the owner email to the Nutshell User.

Bluwave CRM supports custom fields but publishes no field name or data type reference. During scoping we export sample records from each module, infer data types from content patterns (date, number, text, picklist), then pre-create matching custom fields in Nutshell before the full import. Any misidentified field type causes validation failures in Nutshell's CSV import, so we validate with a 10-20 record batch before committing the full load. This inference step adds one to two days to the discovery phase.

File attachments on Deals, Contacts, and Companies do not export via Bluwave's Excel export method. We extract attachments separately through the web interface where accessible and re-associate them manually after the data migration using Nutshell's file attachment feature. The customer receives a manifest of extracted files indexed by source record so that manual re-upload can proceed in batches. Attachments not accessible via web interface cannot be migrated and are listed in the exceptions report.

Bluwave User records (name, email, role) map to Nutshell User accounts. We resolve by email match. Role hierarchies and permission sets in Bluwave are not exportable and do not map to Nutshell; the customer configures Nutshell User roles post-migration. Any Bluwave User without a matching Nutshell User is held in the reconciliation queue and provisioned by the customer before the production import phase runs.