Migrate from Unim to Freshsales

Unim's Contact entity maps to Freshsales Contact if the record represents a qualified buyer with an associated Company. If the Unim instance tracks qualification state via a lifecycle or status custom field, we apply a split rule during migration: qualified prospects become Freshsales Leads (which can later be converted to Contacts tied to Accounts), and fully engaged records with an associated Company become Freshsales Contacts linked to an Account. We preserve the original Unim Contact ID and any qualification state in a custom field unim_original_contact_id__c for audit traceability.

Unim Company records map directly to Freshsales Account. The company name maps to Account Name; domain or website maps to Website. We deduplicate by company name during import to prevent duplicate Accounts from forming if the same company appears under multiple names in Unim. The Account must exist before any Contact import so that the Account lookup is satisfied at the moment of Contact insert.

Unim Deal records, whether using a standard Deal model or a bespoke opportunity-type custom object, map to Freshsales Deal. The Unim deal stage property maps to Freshsales Deal Stage; pipeline assignment maps to Freshsales Sales Pipeline. We preserve deal amount, close date, and any custom amount fields as typed Freshsales numeric fields. Closed-Won and Closed-Lost reasons from Unim custom fields map to Freshsales custom deal fields.

Unim Activity records (calls, emails, meetings, notes) with a contact or company linkage migrate to Freshsales as Tasks (for calls, emails, and generic tasks) or Events (for meetings). Note-type activities migrate to Freshsales Notes linked to the parent Contact or Account via ContentDocumentLink. Each record's original timestamp is preserved in Freshsales ActivityDate so that the timeline ordering is intact when sales reps open a record in Freshsales.

Unim owner IDs are scoped to the specific Unim deployment and cannot be used directly in Freshsales. We extract every distinct owner referenced on Contact, Company, Deal, and Activity record, then match by email address against Freshsales User records. Any Unim owner without a matching Freshsales User goes into a reconciliation queue for the customer's admin to provision before the record migration phase resumes. Owner assignment on Deals maps to Freshsales Deal Owner field.

Every custom field active in the Unim instance is discovered via the custom-fields API before migration begins. We inspect the DataType and ModelID for each custom field and create the corresponding Freshsales custom field under the appropriate entity (Lead, Contact, Account, or Deal) via Admin Settings. Multi-select, date, numeric, and text custom field types map directly. Unim enum or picklist fields map to Freshsales picklist fields with the same options enumerated.

Unim applications may include bespoke object types beyond Contacts, Companies, and Activities. We discover these during schema introspection, identify their relationships to standard entities (lookups, foreign keys), and create equivalent custom objects in Freshsales using the Freshsales custom objects feature (available from Growth tier). Lookup relationships from custom objects to standard entities are preserved as Freshsales lookup fields. The customer's admin configures any custom object page layouts in Freshsales post-migration.

Unim attachments are served via the Files dimension and require a separate API call per file. We paginate file extraction to stay within Unim API rate limits, apply retry logic on 429 responses, and upload each file to Freshsales linked to the target Contact, Account, or Deal record. Original filenames and MIME types are preserved. For large attachment volumes, we extract files in batches and track progress via a migration manifest so that no file is silently dropped.

Unim tag associations are stored as separate linked records or array fields depending on the specific deployment. We preserve tag-to-record linkages as a migration join table and apply them to Freshsales either as a multi-select picklist field on the target entity (if tags apply to a single entity type) or as text label fields. The customer chooses the tag application strategy during scoping. Tags that represent contact segments are mapped to Freshsales Contact Segments if available on the plan.