Migrate from Function 365 to Freshsales

Direct 1:1 mapping. Each Dynamics 365 Contact field—full name, email address, phone number, physical address, and job title—is transferred directly to the corresponding Freshsales Contact record. The migration also writes the Dynamics 365 contact GUID into a custom field (source_system_id) for traceability. Owner resolution occurs by matching the Dynamics 365 owner’s email address to an existing Freshsales user; unmatched owners are logged for manual assignment before the migration run.

Direct 1:1 mapping. Active Dynamics 365 Leads (status New or Open) become Freshsales Leads, with the source Dynamics 365 GUID preserved in a custom field. Converted Dynamics 365 Leads trigger the creation of Freshsales Contact and Account records, copying the original lead creation date and any custom lead fields onto the new Contact. This conversion logic is defined in the migration plan and verified during the sample run.

Direct 1:1 mapping. Each Dynamics 365 Account’s attributes—company name, website domain, industry code, employee count, and annual revenue—are written to the corresponding Freshsales Account record. The original Dynamics 365 Account GUID is saved as a custom field for cross‑reference, and the parent‑account hierarchy is either mapped to Freshsales Territory structures or flattened, depending on your configuration. Any missing parent references are flagged for manual review after the migration run.

Direct 1:1 mapping. Each Dynamics 365 Opportunity becomes a Freshsales Deal, copying the deal name, amount, close date, and stage. The Dynamics 365 opportunity GUID is stored as a custom field for traceability, and the owner is resolved by email match to a Freshsales user. Pipeline assignment maps the source stage name to a Freshsales pipeline stage; any unmapped stages are flagged for configuration before the migration run.

Direct 1:1 mapping. Dynamics 365 Product entries—product name, product ID, unit of measure, and associated price list—are transferred to Freshsales as Products, with the Dynamics 365 product GUID saved in a field for reference. The price‑list relationships are not automatically replicated; after migration, the Freshsales Product Catalog must be configured to re‑establish those pricing tiers. Any missing product categories are noted for manual assignment before the data set goes live.

Dynamics 365 Email activities are migrated as Freshsales Sales Activities of type Email, preserving the original send timestamp, subject line, body, sender and recipient addresses. The email appears on the timeline of the matching Freshsales record (Lead, Contact, Account, or Deal) based on the Dynamics 365 Regarding reference, and any file attachments are attached to the same timeline entry.

Dynamics 365 Phone Call activities become Freshsales Call activities, preserving call duration, direction (inbound/outbound), subject, and outcome notes. The Dynamics 365 phone call GUID is stored in a custom field, and the activity is attached to the matching Freshsales record (Lead, Contact, Account, or Deal) using the source Regarding lookup. The original owner’s email is matched to a Freshsales user, and the original timestamp is retained.

Dynamics 365 Tasks are transferred as Freshsales Tasks, mapping the subject, description, due date, priority, and status fields directly. The Dynamics 365 task GUID is saved in a custom field, and the owner is resolved by matching the source user email to a Freshsales user. Completed tasks carry over the completion timestamp to Freshsales’s task completion tracking, and any custom task fields are reproduced as Freshsales fields during the migration.

Dynamics 365 Appointment records become Freshsales Meeting activities, copying the start and end timestamps, location, organizer email, attendee list, and meeting notes into the corresponding Freshsales Meeting fields. The Dynamics 365 appointment GUID is stored in a custom field, and each meeting is attached to the timeline of the related Freshsales record (Contact, Account, or Lead) based on the source Regarding reference.

Dynamics 365 Note and Annotation records, including any file attachments stored as annotations, are transferred as Freshsales Notes on the timeline of the matching record (Lead, Contact, Account, or Deal). The note’s creation timestamp, author, and rich‑text body are preserved, and the Dynamics 365 annotation GUID is saved in a field for auditability. File attachments are imported as linked files to the Freshsales Note, preserving the file name and content.

Dynamics 365 custom entities transfer as Freshsales custom objects, with each entity’s attributes mapped to matching custom fields. For N:N relationship tables linking custom entities, the migration plan creates a Freshsales junction custom object (or custom relationship fields) to preserve the associations. Custom field data types, pick‑list values, and relationship cardinalities are documented in the pre‑migration schema report and validated before the data load.

Dynamics 365 User records cannot be imported directly into Freshsales; each platform has its own user identity store. The migration engine matches each Dynamics 365 User’s email address to an existing Freshsales user account, preserving the original owner on migrated records. Unmatched owners are flagged in a pre‑flight report and assigned to a designated fallback user, ensuring every record has a valid owner before migration commits.

Dynamics 365 Lead Status pick‑list values—New, Open, Qualified, and Converted—are mapped directly to the corresponding Freshsales Lead Status labels. Any custom Lead Status values defined in Dynamics 365 are identified during the schema assessment and require a one‑to‑one value mapping in the migration plan before execution. The mapping ensures that the status displayed in Freshsales matches the original status from Dynamics 365, preserving reporting continuity for sales cycles.