Migrate from CentralStationCRM to Nutshell

CentralStationCRM People map directly to Nutshell Person records. We export all standard fields (name, email, phone) plus inline fields (title, notes) during the People phase. The Nutshell Person is created first so that any subsequent Deal associations can resolve the Person lookup. Tags from CentralStationCRM apply as Nutshell tags against the Person record. Custom fields on People are discovered during scoping and mapped to Nutshell's custom field definitions for the Person object.

CentralStationCRM Company records map to Nutshell Company. The Company object in Nutshell stores an address inline rather than as a child record, so we flatten the first Company address from CentralStationCRM's GET /api/companies/{id}/addrs.json route into the destination's address fields. Additional addresses are noted in a custom field or in the Company notes field if the customer requests it during scoping. Tags migrate as Nutshell tags against the Company record.

CentralStationCRM Lead records map to Nutshell Lead with no split logic required since both platforms use a separate Lead object for pre-contact prospects. HubSpot's Lead-versus-Contact split pattern does not apply here. We export Lead source, status, and any custom fields, then create Nutshell Lead records before associating them with the relevant Person or Company where a relationship exists.

CentralStationCRM Deals map to Nutshell Deals with stage name, value, and assignee preserved. Deal stage names from CentralStationCRM are mapped to Nutshell's default pipeline stages during scoping; if the customer uses custom stage names, we create matching Nutshell pipeline stages before migration. Closed-won and closed-lost outcomes are preserved as status values. Deals are associated with their primary Person or Company using Nutshell's deal-party lookup during import.

CentralStationCRM Activities attached to People or Companies export via nested routes and map to Nutshell's activity timeline on the corresponding Person or Company record. Call logs, meeting records, and notes each become a distinct activity entry in Nutshell's timeline with the original timestamp preserved. We set the activity type field per record so that the timeline renders with the correct icon (phone, calendar, or notepad) in Nutshell's UI.

CentralStationCRM Tasks attached to People or Deals migrate as Nutshell Tasks. Title, due date, and completion status transfer directly. Incomplete tasks import as open Nutshell Tasks; completed tasks import with a completed status and a completed_date matching the original timestamp. Task assignment maps by resolving the CentralStationCRM owner email against the Nutshell user table.

CentralStationCRM tags are flat key-value labels applied across People, Companies, Deals, and Offers. We export the full tag vocabulary and apply each tag to the corresponding Nutshell record by type. Tags that do not yet exist in Nutshell are created at migration time. The customer chooses during scoping whether tags are the primary taxonomy or whether a subset of tags should be mapped to custom fields instead.

CentralStationCRM per-tenant custom fields have no fixed schema across accounts. We discover every custom field on People, Companies, Deals, and Leads during scoping, identify the field type (text, number, date, checkbox, dropdown), and create matching Nutshell custom fields on the equivalent object before migration. Custom field values are then written during the main import phase for each object.

CentralStationCRM Offers (standalone quote-like objects with line items and totals linked to People or Companies) map to Nutshell Quotes. We export offer line items, quantities, prices, and the total, then create Nutshell Quote records with line items attached to the corresponding Person or Company. Nutshell Quotes are available on Pro and above; if the customer is on the Foundation plan, we flag this during scoping so the customer can upgrade before migration or accept that quote records are written as Deal-line-item notes.

CentralStationCRM stores addresses as 1-n children of People via GET /api/people/{id}/addrs.json and of Companies via GET /api/companies/{id}/addrs.json. We traverse every address route during export, then flatten each address into Nutshell's inline address fields (street, city, state/province, postal code, country) on the corresponding Person or Company record. If a Person or Company has multiple addresses, the primary (first) address becomes the inline fields; additional addresses are written to a custom text field or the notes field as a pipe-delimited list, per the customer's scoping preference.