Migrate from Camp Automation to Nutshell

Camp Automation Contacts map to Nutshell Person records. Standard fields (name, email, phone, address) migrate directly. The company name stored in Camp's company property becomes a lookup to the Nutshell Account record we create from distinct company names extracted during the discovery pass. We split the full name into Nutshell's first_name and last_name fields; any records without a name are imported with a placeholder and flagged for customer review.

Camp Automation Company records map to Nutshell Account records. We extract company name, domain, industry, and size fields and map them to Account.name, Account.website, Account.industry, and Account.employees respectively. Account records are created first during migration so that the AccountId lookup on Person is satisfied at import time. Where Camp stores multiple contacts under a single company with no explicit Company record, we create Account records from the company name property during the Contacts extraction pass.

Camp Automation Deals map to Nutshell Opportunities with pipeline and stage mapped via a named stage-to-stage configuration. We extract pipeline name, stage, value, close date, and owner. Nutshell's pipeline structure uses Stages configured within the CRM rather than as a separate API object, so we pre-configure the pipeline in Nutshell before import and map the Camp pipeline and stage values to the corresponding Nutshell Stage during the transform step. Deal owner maps by email lookup to Nutshell User.

Camp pipeline stages map to Nutshell Stages pre-created in the destination CRM. Stage probabilities are not stored in Camp's export, so we either use customer-specified probabilities or default to Nutshell's standard stage probability percentages. Closed-Lost and Closed-Won stages are preserved with their original close dates from Camp.

Camp Automation pipelines (one per campaign or sales process) map to Nutshell Pipelines. We create a Nutshell Pipeline for each Camp pipeline during the configuration phase. The mapping is 1:1 unless the customer requests pipeline consolidation, in which case we document the intended mapping and apply it during the Deal import transform.

Camp Automation multi-channel Campaigns (grouping email, SMS, social, and push assets) do not have a direct Nutshell equivalent because Nutshell Campaigns are email-centric activity groupings. We import the campaign name and description as a Nutshell Campaign record for reference, and document the channel-specific assets (email templates, SMS content, social posts) in a written handoff inventory for the customer's admin to manually re-create in Nutshell's campaign editor.

Camp Automation Email Templates (subject, HTML body, variable placeholders) export as HTML files with inline CSS and preserved variable syntax. We deliver these as a zip archive of HTML documents organized by campaign, rather than importing them into Nutshell's template library, because Nutshell's template structure differs from Camp's. The customer's admin uploads templates manually into Nutshell's email editor, using the exported HTML as source material.

Camp Automation tags migrate to a Nutshell Tag field of type multi-select picklist. We preserve the full tag taxonomy exactly and reapply all tags at import time. Tags that do not exist in the destination are created during import. The tag taxonomy is preserved end-to-end so that segmentation logic built on tags in Camp continues to function in Nutshell after migration.

Camp Automation custom fields on Contacts, Companies, and Deals require schema discovery before migration (customer exports the field list from Camp UI). Field types (text, date, dropdown, number) map to the equivalent Nutshell column types. We pre-create all custom columns in Nutshell before data import so that field types are correct and reporting filters remain functional. Without schema discovery, we risk creating fields with incorrect types which can corrupt filter logic.

Camp Automation Owners map to Nutshell Users by email address match. We extract every distinct owner referenced on Contact, Company, Deal, and Engagement record and match by email against the Nutshell destination. Owners without a matching Nutshell User go to a reconciliation queue for the customer's admin to provision before record import resumes.