Migrate from Daffodil CRM to Microsoft Dynamics 365 Sales

Daffodil CRM Contact records map to Microsoft Microsoft Dynamics 365 Sales Contact or Lead depending on qualification status. We define the split rule during scoping based on the customer's lifecycle stage values in Daffodil CRM, compute the split at migration time, and preserve the original Daffodil CRM contact status in a custom field for audit. AccountId is resolved after Accounts are imported so that Contact-to-Account lookups are satisfied at insert time. If Daffodil CRM used a flat contact model without lifecycle stages, all records map to Contact with Account lookup resolved via company name match.

Daffodil CRM Company records map directly to Microsoft Microsoft Dynamics 365 Sales Account. Company name becomes Account Name; domain or website fields map to the Account Website field. Account is created before any Contact import so that the AccountId Lookup relationship is satisfied at the moment of Contact insert. We deduplicate by company name during import to avoid duplicate Account records.

Daffodil CRM Deals map to Microsoft Microsoft Dynamics 365 Sales Opportunity. Deal name maps to Opportunity Name; deal amount maps to Amount; deal stage maps to a configured Sales Process stage in Dynamics 365. Expected close date migrates to CloseDate; owner assignment maps to OwnerId via User lookup. If Daffodil CRM used multiple deal pipelines, we create multiple Opportunity Record Types and Sales Processes in Dynamics 365 before migration.

Daffodil CRM Activity records export as flat rows with an activity type field. We split by type: calls map to Task with TaskSubtype=Call and call duration preserved in a custom field; emails map to EmailMessage linked to a Task for timeline display; meetings map to Event with StartDateTime and EndDateTime preserved; standalone tasks map to Task. Parent record resolution (WhoId, WhatId) uses email-based matching against imported Contacts and Leads since Daffodil CRM does not expose record IDs for direct lookup.

Daffodil CRM custom fields vary per customer implementation. We request a complete field inventory from the customer before mapping begins, then configure equivalent custom fields in Dynamics 365 using the same display name and matching data type. Multi-select picklist values from Daffodil CRM map to Dynamics 365 Option Sets with the same value labels. Date fields and currency fields migrate directly with type preservation. Custom fields are deployed to Dynamics 365 Sandbox for validation before production migration.

Daffodil CRM tags applied to contacts, companies, or deals export as comma-separated values or individual rows. We flatten multi-value tag fields during extraction and reassemble them in Dynamics 365 as multi-select picklist fields on the relevant entity. The customer confirms during scoping whether tags represent classification categories, status flags, or segmentation values to ensure correct field type selection in the destination.

Daffodil CRM user records (sales reps, managers, admins) migrate as owner assignments on records. We map user name, email, role, and team membership. Active status is preserved; inactive users are archived. We match by email against the Dynamics 365 destination org's User table. Any Daffodil CRM Owner without a matching Dynamics 365 User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

File attachments stored within Daffodil CRM are not reliably exportable via standard CSV. We do not migrate attachment files directly. Instead, we export attachment metadata (filename, file type, associated record reference, upload date) into a CSV inventory that the customer's admin uses to manually relocate files to SharePoint or re-attach them post-migration. This is documented in the handoff package.