Migrate from CentraHub CRM to Nutshell

CentraHub Account records map directly to Nutshell Company. The Account Name becomes the Company name field, and the Account Website maps to the Company website field. Nutshell Companies do not have a mandatory Person association, so we write all Companies first during migration to establish IDs before any Person records are created. If CentraHub Accounts contain industry, annual revenue, or address data, we map these to Nutshell Company custom fields that the customer configures before migration begins.

CentraHub Contact records map to Nutshell Person. Each Person's company_name field is set by resolving the Contact's parent Account ID to the Nutshell Company ID created during the Accounts phase. Contact phone, email, title, address, and owner fields map directly. If a Contact in CentraHub has no parent Account, the Person is created without a Company association. Person records are written after all Companies to satisfy the Company lookup requirement on every Contact-to-Account relationship.

CentraHub Lead records map to Nutshell Person with a Lead source field preserved as a custom Person field. Lead status and rating are mapped to Nutshell custom picklist fields that the customer configures before migration. Since Nutshell does not have a separate Lead object, unqualified prospects and qualified contacts coexist in the same Person table, and the customer's admin manages segmentation using custom fields populated during migration.

CentraHub Deal records map to Nutshell Opportunity. The Deal's Amount, Close Date, and Probability map directly to Nutshell Opportunity fields. Deal Stage names are translated using a customer-defined mapping table against Nutshell's standard stages (New Lead, Presentation Scheduled, Decision Maker Bought-In, Contract Sent, Closed Won, Closed Lost). The Deal's primary Contact or Account owner maps to the Nutshell Opportunity owner and the associated Person. Nutshell Opportunity stages are configurable in Settings > Pipelines before migration, and we match stage names to the configured values during the transform phase.

CentraHub Activities of type Call, Email, Meeting, and Note all map to Nutshell Note records. The activity type, timestamp, body content, duration, and outcome are preserved in Note custom fields or the Note body itself. Nutshell does not have separate native objects for calls, emails, and meetings, so we consolidate all four activity types into Note records with a custom type field to preserve the original taxonomy. Activity history cannot be imported via CSV; we use Nutshell's REST API with per-record POST calls, batched and rate-limited to avoid throttling.

CentraHub Task records map to Nutshell Note records. Task Due Date, Status, Priority, and Description are preserved in Note custom fields that the customer configures before migration. Task assignment maps to Nutshell Person or Company owner where the resolved User lookup exists. Tasks with a completed date are flagged with a custom completed flag field to preserve the original task lifecycle state.

CentraHub custom fields per module (Leads, Accounts, Contacts, Deals) are mapped to Nutshell custom fields on the corresponding Person, Company, or Opportunity object. We extract the full CentraHub custom field schema during discovery, validate data types against Nutshell's supported types (text, number, picklist, date), and flag any field type that requires a multi-select or relational structure not available in Nutshell's custom field system. The customer configures the target Nutshell custom fields before the migration data load begins.

CentraHub attachments stored via Dropbox or Box integration are downloaded to temporary storage during migration. After Person, Company, and Opportunity records are written to Nutshell, we re-attach files using Nutshell's attachment API, linking each file to the corresponding Nutshell record by ID. We do not migrate attachment metadata as a bulk load; each file requires a separate API call and file upload, which makes large attachment sets a significant time and cost driver in the migration scope.