Migrate from CentraHub CRM to Freshsales

CentraHub Lead records map directly to Freshsales Lead. We preserve lead source, status, owner assignment, and creation timestamp. CentraHub's Lead module stores the primary phone, email, and qualification status fields that map to Freshsales Lead standard fields. Any CentraHub Lead with a status of 'Converted' is flagged for manual review because Freshsales handles lead conversion differently, and the converted Contact mapping must be reconciled by the customer's admin.

CentraHub Account records map to Freshsales Account with Account Name, Website, Industry, Phone, and Address fields transferred directly. The CentraHub Account ID is preserved as a reference field (centrahub_account_id__c) for audit purposes. Account is created before any Contact import so that the parent Account relationship is satisfied at Contact insert time.

CentraHub Contact records map to Freshsales Contact with Account lookup resolved via email-domain matching against the imported Accounts. We extract the CentraHub Account ID from each Contact record, look up the corresponding Freshsales Account ID from the Account mapping table, and write the Contact with the resolved AccountId. First name, last name, email, phone, title, and address fields migrate directly. Any Contact without a resolvable Account parent is held in a reconciliation queue.

CentraHub Deal records map to Freshsales Deal with stage, amount, close date, probability, and owner preserved. The pipeline-to-stage mapping requires configuration during scoping: CentraHub pipeline names map to Freshsales pipeline names, and CentraHub deal stages map to Freshsales deal stages by name match. Any stages with no Freshsales equivalent are flagged for the customer's admin to configure before migration. Deal owner assignment resolves via email match against Freshsales Users.

CentraHub separates Activities by type (Call, Email, Meeting) into distinct modules. Freshsales uses a unified Activity model with an activity_type picklist field. We extract each activity type from CentraHub, normalize the timestamp and duration fields to UTC, and write each activity as a Freshsales Activity record with the appropriate activity_type value. The parent record reference (Contact ID or Deal ID) resolves via the CentraHub ID lookup table created during the initial extract phase.

CentraHub Task records map to Freshsales Task with due date, priority, status, and owner preserved. Priority and status values require value mapping because the picklist values differ between platforms. We extract the full CentraHub picklist, map each value to the nearest Freshsales equivalent, and flag any values with no direct mapping for admin review.

CentraHub per-module custom fields map to Freshsales custom fields with type-mapped equivalents. We extract the custom field schema (field name, data type, required flag) per module during discovery, pre-create the corresponding Freshsales custom fields before import, and validate data type compliance during the transform phase. CentraHub's loose data type enforcement on CSV import means we expect to find type mismatches (text in number fields, dates in text fields) and flag these before writing to Freshsales, which enforces types strictly at the API level.

CentraHub file attachments are associated with records via Dropbox and Box integrations. We download attachments to temporary storage during the extract phase, then re-attach them post-import using the Freshsales file upload API linked to the corresponding Contact, Account, or Deal record. Attachment references are resolved via the CentraHub record ID mapping table. We flag any attachment exceeding the Freshsales file size limit for manual handling.