Migrate from CentralStationCRM to Salesforce Sales Cloud

CentralStationCRM People records map to either Salesforce Lead or Contact depending on whether the record represents an unqualified prospect or a qualified contact with an active relationship. We evaluate any lead_status field and the presence of Deals or Activities during scoping to determine the split. Records with no Deals and no active communication history map to Salesforce Lead. Records attached to Deals or with a closed-won status map to Salesforce Contact. The original CentralStationCRM record ID preserves in a custom field cscrm_id__c on both Lead and Contact for reconciliation.

CentralStationCRM Company records map directly to Salesforce Account. The company name maps to Account Name, domain information maps to Website, and industry maps to Industry if populated. Account is created before any People import so that the AccountId lookup is resolved at Contact insert time. We use Company name as the dedupe key to prevent duplicate Account creation during import.

CentralStationCRM Deals map to Salesforce Opportunity. The deal title becomes Opportunity Name, deal value maps to Amount, and stage maps to StageName via a stage-mapping configuration we build during scoping. The assigned person maps to OwnerId via the Owner-to-User email resolution. Deals linked to a Company get the AccountId resolved at migration time.

CentralStationCRM deal stages map to Salesforce Opportunity StageName values. We configure a Salesforce Sales Process that whitelists the relevant stage values before migration. Stage probability percentages migrate from CentralStationCRM to StageProbability, rounded to the nearest Salesforce-allowed integer. If CentralStationCRM has a custom stage field, it maps to a custom Opportunity field.

CentralStationCRM Leads that are distinct from Deals (separate API endpoint /api/leads.json) map directly to Salesforce Lead. Lead status maps to Salesforce Lead Status, and any scoring or source information maps to custom fields. Leads that have been converted to Deals in CentralStationCRM are not re-imported as Leads in Salesforce to avoid duplication with the Deal-to-Opportunity migration.

CentralStationCRM Activities attached to People or Companies traverse via nested routes (e.g., GET /api/people/{id}/activities.json) and map to Salesforce Task and Event records. Call and task activities map to Task with TaskSubtype = Call for phone calls. Meeting activities map to Salesforce Event with StartDateTime, EndDateTime, and Location preserved. Activity timestamps preserve to maintain the chronological timeline.

CentralStationCRM tags are flat key-value labels applied across People, Companies, Deals, and Offers. We export all tag assignments per record and apply them at the destination. For tag counts under 100 unique values, we use Salesforce multi-select picklist fields on the relevant object. For higher tag volumes, we use Salesforce Topics with TopicAssignment records. The customer chooses the strategy during scoping.

CentralStationCRM custom fields have no fixed schema across accounts. We discover all custom fields during scoping via the API, inspect their data types (text, number, date, boolean, select), and create matching custom fields in Salesforce before migration. We map CentralStationCRM text fields to Salesforce Text fields, number fields to Number or Currency, date fields to Date, and select fields to Picklist with the corresponding values.

CentralStationCRM Tasks attached to People or Deals map to Salesforce Task. Title, due date, and completion status migrate. Completion state in CentralStationCRM maps to a custom Salesforce Task field rather than a hard delete so that the task history is auditable. Task assignments resolve the hubspot_owner_id to Salesforce OwnerId via the Owner mapping.

CentralStationCRM Offers (standalone objects similar to Quotes) map to Salesforce Quote, which is available from Salesforce Sales Cloud Professional tier. Offer line items map to QuoteLineItem with product, quantity, unit price, and total preserved. Quote status migrates from CentralStationCRM offer status. Note that Quote requires the Pricebook2 to be set on Opportunity before Quote creation; we configure this sequence during the migration run.

CentralStationCRM addresses are nested children of People, fetched via GET /api/people/{id}/addrs.json. We traverse each nested address route during export. For single-address contacts, we map to Salesforce standard address fields on Contact. For multi-address contacts, we create a custom Address object with a lookup to Contact and preserve address type (billing, shipping, other) as a custom picklist field.

CentralStationCRM Owner records map to Salesforce User. We resolve owners by email match against the destination Salesforce org's User table. Any CentralStationCRM Owner without a matching Salesforce User enters a reconciliation queue for the customer's admin to provision before record import resumes. Inactive CentralStationCRM owners map to inactive Salesforce Users if historical assignment needs to be preserved.

CentralStationCRM Deals optionally link to a Company. We capture this link during Deal export and resolve it to AccountId on the Salesforce Opportunity at migration time. If the linked Company does not exist in the destination (e.g., it was archived in CentralStationCRM), we flag the Opportunity with a custom field missing_company__c for the customer's admin to manually associate post-migration.