Migrate from CentraHub CRM to Salesforce Sales Cloud

CentraHub Lead records map directly to Salesforce Lead. We preserve lead source, status, owner assignment, and all standard lead fields. Any CentraHub custom lead fields migrate as Salesforce custom Lead fields. The migration user performs all Lead inserts into the target Salesforce org before any Contact conversion begins, ensuring the conversion path is available when Leads qualify.

CentraHub Account records (company-level entities) map 1:1 to Salesforce Account. The Account record is the parent anchor for all Contact and Opportunity relationships in Salesforce, so we write Accounts first and resolve the Account ID for every dependent Contact and Deal record before those insert phases begin. Account Name becomes the Account Name field; industry and website map from the corresponding CentraHub fields.

CentraHub Contact records (person-level entities) map to Salesforce Contact, linked to the parent Account via the AccountId lookup. We reconstruct the Account-Contact relationship from the exported ID columns in the CentraHub CSV export. All Contact standard fields (name, email, phone, title, department) map directly; custom Contact fields map to Salesforce custom Contact fields with type-matched field definitions.

CentraHub Deal records map to Salesforce Opportunity. The deal stage maps to the Salesforce Opportunity StageName via a stage name translation table we build during scoping. Each distinct CentraHub pipeline definition becomes a Salesforce Record Type on Opportunity with its own Sales Process and stage whitelist. We flag stages with no Salesforce equivalent for admin configuration before the migration insert phase.

CentraHub pipeline definitions map to Salesforce Opportunity Record Types and corresponding Sales Processes. The pipeline name becomes the Record Type label and API name; stage names within each pipeline become Stage values in the associated Sales Process. Probability percentages per stage migrate to the Salesforce stage probability map. Page Layout assignments per pipeline are configured by the customer's admin after migration.

CentraHub Task records map to Salesforce Task with Status, Priority, ActivityDate, and Subject preserved. Custom task types (call, meeting, follow-up) require value mapping against the CentraHub picklist since task subtype taxonomy differs. Owner assignment migrates by email lookup against Salesforce User records. Any CentraHub task without a matching Salesforce User is held in the owner reconciliation queue.

CentraHub calendar Appointment records map to Salesforce Event with StartDateTime, EndDateTime, Subject, and Location preserved. Timezone handling is normalized to UTC before insert. We flag appointments that fall outside the standard business hours configured in Salesforce or that reference attendees not present in the migrated Contact or Lead set.

CentraHub Activity records encompass call logs, email logs, and notes attached to Leads, Accounts, Contacts, or Deals. We split these by activity type: call logs become Task with TaskSubtype=Call; email logs become Salesforce EmailMessage records linked to a Task for timeline display; notes become Salesforce Note records linked via ContentDocumentLink to the parent record. WhoId and WhatId are resolved at migration time using the Lead and Account IDs reconstructed from the export.

CentraHub custom fields per module (text, number, picklist, date, phone, email, website, geolocation) map to Salesforce custom fields of the corresponding type. We extract the complete custom field schema per module during discovery and create the destination Salesforce custom field definitions before any data load. Type mismatches (values CentraHub silently accepted on CSV import that violate the declared data type) are flagged and corrected before the Salesforce insert to prevent validation rule failures.

CentraHub Email Campaign records (open/click data and send history) migrate to Salesforce Campaign as read-only records preserving campaign name, start date, status, and budget cost. Historical send metrics migrate to CampaignMember records linked to the corresponding Leads and Contacts. Active campaign state and scheduled sends do not migrate; these require re-initiation in Salesforce Campaign or Marketing Cloud Account Engagement post-migration.

CentraHub tags applied across objects for segmentation migrate to Salesforce as a customer-chosen strategy: either multi-select picklist fields on the relevant object or Salesforce Topics with TopicAssignment records. We document the full tag vocabulary during discovery and the customer selects the destination model. Tags with no direct equivalent are flagged for manual reassignment after migration.

CentraHub file attachments stored via Dropbox or Box integrations are downloaded to temporary storage during the export phase. We re-attach files post-import using the Salesforce ContentDocument and ContentVersion APIs, linking each document to the parent record via ContentDocumentLink. Files without a downloadable URL in the export (stored only in the CentraHub UI) are flagged for manual re-upload by the customer's team.