Migrate from SalesPro CRM to Nutshell

SalesPro Contact records map directly to Nutshell Person. We extract name fields, email address, phone number, company association (via the Company foreign key), and any permission-based sharing flags. The Contact-to-Company lookup resolves to a Nutshell Company record that must be created first in the import sequence. Null spouse fields (a known SalesPro bug where the spouse field displays even when empty) are stripped during transformation to avoid spurious data in Nutshell Person records.

SalesPro Company records map to Nutshell Company. The HubSpot-sourced salespro_crm Company name becomes the Nutshell Company name, and the domain or website field maps to Company website. Nutshell Company records are imported before Person records so that the Company lookup on Person is satisfied at the moment of insert. Any SalesPro Company without a domain or name becomes a placeholder Company record that the customer reconciles post-migration.

SalesPro Event records map to Nutshell Activity. We preserve start and end timestamps, location, group details, and event description. The Contact association (via the SalesPro event-to-contact linkage) migrates as an Activity linked to the resolved Nutshell Person. If SalesPro Events reference BEO records, we preserve the BEO identifier in a custom Activity field for reconstruction against the BEO custom object mapping.

SalesPro BEO records are derived outputs generated from Event data, containing cost calculations, timeline specifications, and event signing data. Nutshell has no native BEO object, so we reconstruct BEO data as custom fields on the corresponding Nutshell Activity. Cost line items map to custom currency fields; timeline specs map to custom date and text fields; signing data (signer name, timestamp, spouse field if valid) maps to custom fields on the Activity. This reconstruction requires the Event-to-BEO linkage to be intact at export time.

SalesPro Task records map to Nutshell Task with assignee (via email-to-User resolution), due date, description, and completion status preserved. Email reminder flags migrate as Nutshell Task notification settings. Task assignment resolves HubSpot owner IDs to Nutshell User records by email match, with unresolved owners placed in a reconciliation queue for the customer's admin to provision before record import.

SalesPro custom milestone definitions tied to sales cycles or goal-based scenarios map to Nutshell custom fields on the relevant Deal. We ask the customer during scoping which milestones are pipeline-level (mapped as Deal custom fields) versus task-level (mapped as Task custom fields). Milestone ordering and relative stage position are preserved as picklist or integer values in the custom field.

SalesPro pipeline and stage configurations (tier-dependent on SalesPro) map to Nutshell Pipeline stages. We extract stage names and relative ordering from SalesPro, then configure the corresponding Nutshell Pipeline with matching stage labels. If SalesPro stages use custom colors or probabilities, we document these for manual configuration in Nutshell's visual pipeline builder post-migration.

SalesPro Users mapped to Contacts, Tasks, and Events by email address resolve to Nutshell User records. We extract the full user list from SalesPro, match by email against Nutshell's provisioned users, and hold any unmatched owners in a reconciliation queue. Owner reassignment during migration requires the customer to provision missing Nutshell users before the Person and Activity imports run, since OwnerId references are required for Activity assignment.