Migrate your CentralStationCRM data

The primary contact object in CentralStationCRM. Exposed via GET /api/people.json with standard fields (name, email, phone). We export all fields and create matching contact records at the destination, preserving the email address as the primary identifier.

Company records are distinct from People and link to contacts via a has-many relationship. Exported via GET /api/companies.json. We create company records at the destination first, then associate People records to them using the stored relationship.

Deals track sales opportunities attached to People or Companies. The API exposes them via GET /api/deals.json with stage, value, and assignee fields. We map Deal stages to the destination pipeline stages and preserve monetary values and close dates.

Leads are separate from Deals and represent pre-contact prospects. Exported via GET /api/leads.json. Where the destination CRM does not have a separate Lead object, we merge into the contact type and preserve the Lead source as a custom property.

Activity records (calls, meetings, notes) attached to People or Companies. We export activity history via nested routes and write it to the destination as chronological engagement records on the linked contact.

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 at the destination, handling the tag vocabulary as-is since most targets support free-form tagging.

Each CentralStationCRM tenant defines their own custom fields, which have no fixed schema across accounts. We discover custom fields at the source during scoping and map them explicitly to destination fields, flagging any with data-type mismatches for manual review before import.

Tasks are attached to People or Deals and store title, due date, and completion status. We export task titles and due dates; completion state is migrated as a status field rather than a hard delete, since not all target CRMs treat completed tasks identically.

Offers are standalone objects similar to Quotes, linked to People or Companies with line items and totals. The API exposes them via GET /api/offers.json. We map offer line items to quote line items at the destination, noting that product catalog references may require manual mapping.

Address records exist as a 1-n child of People, accessible via GET /api/people/{id}/addrs.json. We walk each nested address route during export to ensure every address is captured and written to the destination contact's address fields.