Migrate from Unanet CRM by Cosential to Freshsales

Unanet contacts map 1:1 to Freshsales contacts. The contact's associated company resolves to a Freshsales Account via domain match or name match. Unmapped contacts land with no account association and are flagged for manual resolution before the migration commits. During the migration, each contact's original Unanet ID is stored in a custom field (source_system_id__c) for traceability and future delta runs.

Unanet companies map to Freshsales accounts. Company hierarchies (parent/child) collapse to a single primary parent-account reference since Freshsales accounts support only one ParentId. Multi-subsidiary structures require post-migration account hierarchy setup in Freshsales. We also preserve the original Unanet company ID in a custom field (source_system_id__c) on the Freshsales Account record to enable cross-reference during delta imports.

Unanet opportunities map to Freshsales deals. Pipeline stages map value-by-value to Freshsales deal stages per pipeline. Deal amount, close date, owner, and probability all transfer directly. Unanet opportunity IDs are stored in a custom field for traceability. The mapping also ensures that any custom fields on the opportunity, such as regional segmentation or product lines, are transferred to Freshsales custom fields on the deal record.

Unanet call logs become Freshsales tasks with Type=Call. Emails become tasks with Type=Email. Meetings become Freshsales events with original start/end times and location preserved. Notes migrate as Freshsales notes. Original activity timestamps and owner IDs transfer with each record. Each migrated activity retains a reference to its source Unanet ID in a custom field (source_system_id__c) for reconciliation during delta runs.

Unanet lifecycle stage values have no direct Freshsales equivalent. We create a custom pick-list field (lifecycle_stage__c) on Freshsales contacts and map Unanet's stage values one-by-one. Unmapped stage values default to a catch-all value and are flagged for review. The mapping table is exported as a CSV so your team can validate the stage assignments before the final data load.

Unanet custom objects map to Freshsales custom objects created via the developer platform. N:N relationships in Unanet require junction objects or custom multi-select fields in Freshsales. We deliver a relationship mapping plan showing which custom objects need junction setup before migration.

Unanet proposal documents have no Freshsales equivalent. We download all proposal files and re-upload them as file attachments linked to the corresponding migrated deal record. Teams needing proposal automation should evaluate Freshsales CPQ add-on post-migration. The original proposal filenames and IDs are stored in a custom text field on the deal for future reference.

Unanet project records tracking pursuit-to-project transitions have no Freshsales deal counterpart. Project names and identifiers migrate as custom text fields on deal records for reference. Active project tracking requires a separate project management tool post-migration. Each migrated project identifier is stored in a custom field (source_project_id__c) on the deal to maintain a link to the original Unanet record.

Unanet's personnel module (staff experience, certifications, areas of expertise) maps to Freshsales contacts with custom fields. Professional credentials and certification data migrate as custom text fields. Original timestamps and department associations are preserved in corresponding custom fields. The staff ID from Unanet is recorded in a custom field (source_personnel_id__c) on the Freshsales contact for future reference.

Unanet file attachments on any record re-upload to Freshsales Files attached to the corresponding record. File size limits of Freshsales apply (typically 25MB per file). Inline images in notes are downloaded and re-hosted as file attachments. Each re-uploaded file retains its original filename and a reference to the source Unanet attachment ID in a custom field for auditability.

Unanet owners and users resolve to Freshsales users by email address match. Unmatched owners are flagged before migration — teams either invite them to Freshsales first or assign records to a fallback owner. No record lands without a valid Freshsales owner.