Migrate from Data Team DDS to Freshsales

Direct object-to-object map between Data Team DDS Contact and Freshsales Contact. Freshsales requires an AccountId lookup on all contacts — contacts without a primary company association in the source require a resolution strategy before migration. You can either attach them to a pre-created default account record or define a fallback account rule in the migration configuration to ensure every contact lands with a valid company association.

Direct field-level mapping from Data Team DDS Company to Freshsales Account object. Freshsales Account supports parent-child hierarchies through the Parent Account lookup field — source company parent relationships map to Freshsales ParentId references. Multi-company contacts in the source system that belong to multiple companies collapse to a single primary AccountId in Freshsales, with secondary associations preserved through Account Contact Relationships.

Direct object-to-object mapping when the source system maintains a separate Lead object distinct from Contact. Freshsales Lead records include standard Status, Source, Rating, and Owner fields that map directly from the source. Any unqualified leads in the source that have not yet converted to contacts map as-is into Freshsales Lead records for continued nurturing and follow-up within the Freshsales sales workflow.

Direct map. Freshsales Deal corresponds to an Opportunity object — it stores pipeline stage, amount, close date, probability, owner, and associated contacts. Stage names are mapped value-by-value per pipeline using a defined value-mapping table. Freshsales enforces Deal Value on every deal — any blank amount values in the source must default to 0 or records will be rejected during the API import process.

Source pipeline becomes a Freshsales Pipeline record. If the source has a single pipeline, it maps directly to one Freshsales Pipeline. Multiple pipelines with different stage sets each become separate Freshsales Pipelines, and deal records route by matching pipeline names. Stage probability values are re-applied according to Freshsales pipeline stage configuration settings.

Freshsales has no native lifecycle stage equivalent at the contact level beyond its own Lifecycle Stage object. We create a custom pick-list field (Lifecycle_Stage__c) on the Contact and Lead objects in Freshsales and map the source stage values into it. Stage-change timestamps are preserved as Lifecycle_Stage_Updated__c datetime fields.

Source call log records map directly to Freshsales Sales Activities of type Call. Original call duration in seconds, direction (inbound or outbound), outcome disposition, and owner assignment are all preserved during migration. If the source platform stores call recordings as linked files, those recordings are downloaded and re-uploaded as attachments to the corresponding Sales Activity record in Freshsales.

Source email activity logs map to Freshsales Sales Activities of type Email. The subject line, full email body content, direction (sent or received), and sent or received timestamps are all preserved in the migrated records. Associated contact and account records are linked by email address or name match during the activity migration step to maintain relationship continuity.

Source meeting records map to Freshsales Sales Activities of type Meeting. The start time, end time, physical or virtual location, meeting title, list of attendees, and organizer details are preserved during migration. Migrated meetings are linked to their associated contact and account records in Freshsales using attendee email address matching to maintain the full relationship context.

Source notes map directly to Freshsales Note records. Note title, body content, created date, and owner are preserved. Notes are linked to the parent Contact, Account, or Deal by record ID match. Rich-text formatting is preserved where the source supports it.

Source task records map directly to Freshsales Task objects. Task subject, due date, status (open, completed, deferred), priority level, and owner are all preserved during migration. Tasks that are linked to specific contacts or deal records in the source are re-linked in Freshsales using email address or name matching on the associated records to maintain workflow continuity.

Source custom objects map to Freshsales Custom Modules (available on Pro and Enterprise plans). Each custom object requires a corresponding Custom Module to be created in Freshsales before migration. Custom object associations that use many-to-many relationships need junction objects in Freshsales — we surface this in the pre-migration schema plan.

Owners in the source are matched to Freshsales users by email address. Unmatched owners are flagged before migration — your team either invites them to Freshsales first or assigns their records to a fallback owner. No record lands in Freshsales without a resolved OwnerId.

Source file attachments linked to contacts, accounts, and deals are downloaded from the source system and re-uploaded to Freshsales. Each file is attached to the corresponding Freshsales record (Contact, Account, or Deal) using record ID matching. File size limits apply per the Freshsales storage tier assigned to your account — large files may require additional storage provisioning before migration.