Migrate from Centrium CRM to Freshsales

Centrium stores person contacts and organization contacts in the same object, distinguished by an organization flag. We identify person contacts during preprocessing and route them to Freshsales Contacts. Contacts without an assigned organization map to Freshsales Leads if the customer prefers to qualify them before account assignment. The email address serves as the dedupe key. Phone numbers, addresses, custom fields, and contact owner (team member) transfer directly. Owner assignment defaults to the importing admin and requires manual redistribution post-migration if Centrium team members map to Freshsales users.

Centrium organizations are contacts marked with an organization flag. We extract these flagged records during preprocessing, create corresponding Freshsales Account records, and re-link the individual Contact records to the new Account via the Account lookup. This split-and-link step adds preprocessing time proportional to the number of distinct organizations. Any organization name, website, address, or custom field data on the flagged contact maps to the equivalent Freshsales Account field.

Centrium Deals map to Freshsales Deals. The Centrium status field (won/open/lost) maps to the nearest Freshsales pipeline stage; we default won to Closed Won, open to the first stage of the target pipeline, and lost to Closed Lost. Deal name, amount, expected close date, contact association, and custom fields migrate directly. If the destination Freshsales account uses multiple pipelines, we map the Centrium deal to the default pipeline and flag any pipeline-routing requirement for the customer's admin to configure post-migration.

Centrium uses a fixed three-state pipeline (won/open/lost) with no intermediate stages or timestamps. We map each state to the corresponding Freshsales pipeline stage during configuration. Because Centrium does not track stage-entry timestamps or progression history, we cannot reconstruct a stage history timeline in Freshsales. We note this gap in the validation report as a data completeness disclosure.

Centrium Tasks map to Freshsales Tasks with title, description, due date, priority, and status preserved. Task assignment resolves by matching Centrium team member email to Freshsales User email. Open and completed tasks both migrate. If the Centrium task is linked to a contact or deal, we preserve the association by resolving the Freshsales record ID at migration time. Completed task status maps directly to Freshsales completed status.

Centrium Projects map to Freshsales Projects if the destination account has the Projects module enabled (Growth plan and above). Project name, description, start date, due date, and linked tasks migrate. If the Projects module is not enabled on the destination Freshsales plan, we migrate projects as Tasks with a custom field project_flag__c set to true and flag the limitation in the scoping document.

Centrium Notes attach to contacts, deals, or projects. We migrate note body text and the parent-object association (contact, deal, or project reference). If the note contains file attachments, we flag those separately for storage scoping. Notes are flat in Centrium with no threading model; they map directly to Freshsales Notes attached to the resolved parent record.

Centrium custom fields store as property maps on each record. We extract the field definition (name and type) during preprocessing and create corresponding custom fields in Freshsales before import. Field types map to Freshsales field types (text, number, date, picklist, checkbox). If a Centrium custom field type has no Freshsales equivalent, we flag it during scoping and propose a closest-match type with a note in the mapping document.

Centrium users include name, email, and team membership. We match by email to Freshsales User records. If a Centrium user has no matching Freshsales User, we hold the assignment in a reconciliation queue and flag the gap for the customer's admin to provision the user before record import resumes. Centrium role permissions do not transfer because the platform has no granular RBAC.

Files attached to contacts, deals, or projects in Centrium are retrieved via the UI export. We scope total attachment volume against the destination Freshsales plan's storage allocation. If the total attachment size exceeds the destination storage (10Gb on Growth), we flag the gap before migration and recommend either purchasing additional storage or archiving attachments externally. File content and file name migrate as Freshsales File records linked to the parent record via ContentDocumentLink.