Migrate from CentralStationCRM to Twenty CRM

CentralStationCRM People records map to Twenty Person objects. We export via GET /api/people.json and map firstname, lastname, email, phone, website, and job_title to their Twenty Person field equivalents. The responsible_user_id field resolves to a Twenty User record via email match. Addresses are not embedded in the Person record — we traverse GET /api/people/{id}/addrs.json per contact to capture all address rows and write them to the Person's address fields or as a separate Address relation in Twenty.

CentralStationCRM Company records map directly to Twenty Company. We export via GET /api/companies.json, map name, domain, phone, and industry fields, and create the Company in Twenty before any Person import so that the Person-to-Company relationship is satisfied at the moment of Person insert. If CentralStationCRM stores a billing or shipping address on the Company record, we write it to Twenty's address fields.

CentralStationCRM Deals map to Twenty Opportunity. We export via GET /api/deals.json and map deal name, value (amount), stage, and close date. The assignee maps via responsible_user_id email resolution to the Twenty User. Deal stage labels from CentralStationCRM map to the Twenty pipeline stage values, and we flag any custom stage names requiring configuration in Twenty's pipeline settings before import.

CentralStationCRM Leads are pre-contact prospects distinct from Deals. We export via GET /api/leads.json and map lead name, email, phone, source, status, and assignee. The mapping preserves any CentralStationCRM lead score as a custom field in Twenty. If Twenty does not have a Lead object in the workspace at migration time (it must be enabled in settings), we map Leads to Twenty Person records and flag the object for confirmation during scoping.

CentralStationCRM Activities (calls, meetings, notes) are attached to People or Companies via nested routes (GET /api/people/{id}/activities.json). We traverse all activity routes per parent record and map call activities to Twenty Task records with Task subtype = Call, meeting activities to Event-like Task records, and notes to Twenty Note records. Activity timestamps are preserved as ActivityDate so the chronological timeline is intact in Twenty.

CentralStationCRM Offers are standalone quote-like objects linked to People or Companies with line items and totals. We export via GET /api/offers.json, map offer name, total amount, status, and line items to Opportunity custom fields or a linked Note that captures the offer body. If Twenty has a Quote or Custom Object configured for quote tracking, we map to that object and preserve line item detail in structured fields.

CentralStationCRM Tasks are standalone task records attached to People or Deals. We export task title, due date, status, and assignee (responsible_user_id resolved via email match). Completion state migrates as a status field; we do not hard-delete completed tasks. Tasks are written after the parent Person or Opportunity is created in Twenty to satisfy the relationship reference.

CentralStationCRM tags are flat key-value labels applied to People, Companies, Deals, and Offers. We export all tag assignments per record and apply the same tag set in Twenty, handling the vocabulary as-is. If tag counts exceed Twenty's tag field capacity, we map high-frequency tags to multi-select picklist custom fields and document the strategy during scoping.

Each CentralStationCRM tenant defines their own custom fields with no fixed schema across accounts. We discover all custom fields during scoping (visible via the API response payload for each object) and map them explicitly to Twenty custom fields. Twenty requires custom fields to exist in Settings → Data Model before CSV import or API write. We coordinate with the customer to create matching custom field definitions in Twenty before migration begins.

CentralStationCRM addresses exist as 1-n children of People, accessible only via GET /api/people/{id}/addrs.json. We traverse each nested address route during export so that every address row is captured. In Twenty, address fields live on the Person record. If a Person has multiple addresses (billing, shipping), we write the primary to the Person address fields and store secondary addresses as structured data in a custom field or linked Note.