Migrate from CentralStationCRM to HighLevel

CentralStationCRM People records map to GoHighLevel Contacts via the primary Contact object API. Standard fields (name, email, phone) map directly. We resolve any duplicate contacts using email as the dedupe key, preserving the CentralStationCRM record ID in a custom field for audit. Addresses attached to People via GET /api/people/{id}/addrs.json migrate as nested address records on the Contact.

CentralStationCRM Company records map to GoHighLevel Company. The company_id from CentralStationCRM is preserved in a custom field. Companies are created before Contact import so that any People linked to Companies receive the correct Company association in GoHighLevel. If a Person in CentralStationCRM has no associated Company, it migrates as a Contact without a Company link.

CentralStationCRM Deals map to GoHighLevel Opportunities. The dealstage property maps to the GHL pipeline stage, and the pipeline assignment maps to a GoHighLevel pipeline that we configure before migration. Deal value, assignee (owner), and expected close date transfer to the Opportunity amount, owner, and close date fields. Closed-Lost and Closed-Won states map to GHL stage names that reflect the customer's pipeline configuration.

CentralStationCRM Leads are separate from Deals and represent pre-contact prospects. We map these to GoHighLevel Contacts in the Lead pipeline stage. If the customer uses GoHighLevel's lead routing features, we assign a Lead Status value that routes the record to the appropriate follow-up workflow. The original CentralStationCRM lead source field migrates as a custom field on the Contact.

CentralStationCRM Activity records (calls, meetings, notes) attached to People or Companies migrate as chronological entries on the GoHighLevel Contact's activity timeline. We traverse nested routes during export and write each activity with its original timestamp so that the timeline order is preserved. Activity type (call, meeting, note) maps to the corresponding GHL activity category. Note body content migrates as a text activity entry.

Tags are flat key-value labels in CentralStationCRM applied to People, Companies, Deals, and Offers. We export all tag assignments per record and apply the same tag set to GoHighLevel Contacts, Companies, and Opportunities. Tag vocabulary is preserved as-is; there is no automatic translation or deduplication unless the customer requests it during scoping. Tags used for segmentation in CentralStationCRM become filterable tags in GoHighLevel smart lists.

CentralStationCRM Tasks attached to People or Deals migrate to GoHighLevel tasks on the associated Contact or Opportunity. Task title, due date, and status migrate directly. Completed tasks in CentralStationCRM retain their completed status in GoHighLevel. We flag any tasks without a valid parent record (deleted Contact or Deal) for manual reassignment during reconciliation.

Each CentralStationCRM tenant defines their own custom fields with no fixed schema across accounts. We discover all active custom fields during scoping, map each to an equivalent GoHighLevel Custom Field by type (text, number, date, dropdown, checkbox), create the destination fields in GHL Settings > Custom Fields, and populate them during the import phase. GHL Custom Fields are scoped per object (Contact, Company, Opportunity) using the folder selector, which we configure as part of the schema setup.

CentralStationCRM Offers are standalone objects with line items and totals, linked to People or Companies. We map offer line items to Opportunity line items in GoHighLevel. If GoHighLevel's Opportunity product-line feature is not configured, we migrate the offer as a text summary on the Opportunity record and deliver a configuration note recommending the product catalog setup for the customer's admin. Offer total and status migrate as custom fields if the customer's quoting workflow relies on them.

Address records in CentralStationCRM exist as 1-n children of People, accessible via GET /api/people/{id}/addrs.json. We walk each nested address route during export to capture every address. Each address migrates as a separate address record on the GoHighLevel Contact. If a Contact has multiple addresses (billing, shipping), all are preserved. Addresses without a parent Contact are held in a reconciliation queue.