Migrate from Salescamp CRM to Nutshell

Discovery and collection inventory

We audit the source Salescamp CRM account, identifying every active Collection, the record counts within each, and the admin responsible for exports. We review the standard Lead CSV export columns to determine whether activity history fields are included. We also inventory custom fields on Leads, Companies, and Deals, and confirm the deal pipeline stages in use. The discovery output is a written scope listing all Collections, expected record counts per Collection, and any supplemental export requirements.

CSV export coordination and validation

We request CSV exports from each Collection via the customer's Salescamp workspace admin. On receipt, we validate row counts against the Collection record counts shown in Salescamp's UI and flag any discrepancies. We identify duplicate Lead records (same email address across Collections) and define the deduplication rule (keep most recently updated, merge Collection tags). We request supplemental activity exports if engagement history columns are absent from the standard Lead export.

Nutshell schema setup and custom field creation

We configure the Nutshell destination: create custom fields matching the Salescamp custom field names and types, configure Opportunity stages mapping to Salescamp pipeline stages, set up Tags for Collection membership migration, and define any required picklists. Nutshell requires custom fields to be defined before import, so this step completes before any data moves. We work in the customer's Nutshell trial or sandbox environment first for validation.

Sandbox migration and reconciliation

We run a full migration into the Nutshell sandbox environment using production-like data volume from the collected CSV exports. The customer's admin reconciles record counts (People in, Companies in, Opportunities in, Activities in), spot-checks 15-25 random records against the Salescamp source, and signs off the schema and mapping before production migration begins. Mapping corrections and duplicate resolution refinements happen here, not in production.

Production migration in dependency order

We run production migration in record-dependency order: Companies first (as standalone records), then People (with Company attachment via domain match), then Opportunities (with OwnerId resolved and stage mapped), then Activities (where exported). Collection membership migrates as Tags after the parent records are in place. Each phase emits a row-count reconciliation report before the next phase begins.

Cutover, validation, and automation handoff

We freeze Salescamp writes during cutover, run a final delta migration of any records modified during the migration window, then enable Nutshell as the system of record. We deliver a written inventory of any Salescamp automation or workflow logic for the customer's admin to rebuild in Nutshell's workflow builder. We support a three-day hypercare window where we resolve any reconciliation issues. We do not rebuild Salescamp automations inside the migration scope; that is a separate task for the customer's admin.