Migrate from Apollo ERP to Nutshell

Apollo contacts map directly to Nutshell people records. The person name, email, phone, and job title carry over as standard fields. The company link requires a pre-existing Nutshell company record — we create companies first so foreign-key resolution is clean.

Apollo organizations map 1:1 to Nutshell companies. Company name, domain, industry, employee count, and annual revenue map to their Nutshell equivalents. Apollo's industry pick-list values are mapped to Nutshell's industry pick-list per the value map created during discovery. Where Apollo stores numeric revenue as a formatted string, we parse it to a numeric value for Nutshell's revenue field. All organization records migrate in the organizations-first step to ensure they exist before any dependent person records link to them via the company lookup.

Apollo deals map to Nutshell deals with pipeline stage mapping. Apollo stage names map to Nutshell stage names per the stage-value map created during discovery. Deal amount, close date, and owner are carried forward; owner is resolved by email match to Nutshell users.

Apollo's company-level enrichment signals (employee count ranges, revenue tiers, technology stack) have no native Nutshell equivalent. We create a set of company custom fields in Nutshell and populate them with the last-known enrichment values from Apollo — treated as static reference data since Nutshell does not refresh enrichment.

Apollo contact-level enrichment data (seniority, department, intent signals) has no direct Nutshell equivalent. We create person-level custom fields in Nutshell and populate them with Apollo's enrichment output, preserving the data for reference even though it will not be updated by Nutshell's native tools.

Apollo custom fields defined in Settings > Objects, fields, stages map to identically typed custom fields in Nutshell. We create the destination custom field in Nutshell first, then map values during the migration run. Pick-list custom fields require value-by-value mapping if the Nutshell pick-list options differ from Apollo's.

Apollo call logs, email records, and meeting logs become Nutshell tasks attached to the parent person record. Task type is set to Call, Email, or Meeting, subject carries the activity description, and the original creation timestamp is preserved in a custom datetime field on the task since Nutshell's CreatedDate reflects the import time.

Apollo's computed last_contacted_date field has no native Nutshell equivalent. We create a Last_Contacted__c custom datetime field on the person object and populate it with Apollo's value so the last-contacted signal is visible in Nutshell without requiring activity reconstruction. This preserves the last-contacted intelligence your team relies on for follow-up prioritization, carrying forward the computed date as a static field rather than deriving it from activity records.

Apollo contacts with no linked organization_id are valid and exported with null company. We migrate these as Nutshell people records with no company link, flagging them during mapping review so your team can decide whether to attach to an existing company or leave them unlinked.

Apollo owner_id values are resolved by email match against Nutshell users. Unmatched owners are flagged before migration — your team either creates Nutshell user accounts or assigns records to a fallback owner. No record lands in Nutshell without a valid owner.

Apollo sequences and workflow rules have no equivalent in Nutshell's automation model. We export the sequence definitions (step order, delay days, email templates) as a structured reference document your team can use to rebuild sequences in Nutshell's personal email sequence tool.

Apollo does not provide a comprehensive all-objects export in a single file. We extract data via the REST API in paginated batches, preserving the export scope and original field values. The API extraction log serves as the source-of-truth reference for reconciliation after the Nutshell import completes.