Migrate from Daffodil CRM to Freshsales

Daffodil CRM Contact records migrate to Freshsales Contact. The primary mapping covers first_name, last_name, email, phone, mobile, and company name. Because Daffodil CRM stores company as a text field rather than a relational ID, we use company name as a fuzzy-match key against Freshsales Account records imported in the prior phase. Custom fields on Daffodil CRM contacts export as separate columns and map to Freshsales custom fields of matching type (text, number, date, picklist). Multi-select picklist values from Daffodil CRM require flattening before Freshsales import.

Daffodil CRM Company records map to Freshsales Account. We import Accounts first so that the Account ID is available when Contacts are loaded, satisfying Freshsales Contact.relationships.account_id. Daffodil CRM company name becomes Account Name; domain fields map to Website. Industry, size, and address fields migrate to standard Freshsales Account fields or custom fields based on the customer's field inventory. If Daffodil CRM exports company records as a separate file, we process it before Contact imports to establish the parent relationship.

Daffodil CRM Deal records map to Freshsales Deal. The mapping covers deal_name, amount, stage, expected_close_date, owner_email, and contact association. We use Freshsales Deal pipeline and stage configuration to match Daffodil CRM pipeline stages, creating the pipeline in Freshsales first if it does not already exist. Deal amount migrates as a numeric field; currency assumptions follow what is stored in Daffodil CRM. Owner assignment uses email-based lookup against the User mapping.

Daffodil CRM deal pipeline stages become Freshsales Deal pipeline stages. If Daffodil CRM has a single pipeline with linear stages, we create a matching Freshsales pipeline with equivalent stage names and probabilities. Multi-stage Daffodil CRM pipelines map to separate Freshsales pipelines, each with its own stage sequence and probability weighting. Stage order and probability percentages come from the customer's Daffodil CRM configuration.

Daffodil CRM Activity records of type task migrate to Freshsales Task. The mapping covers task_title, due_date, status, priority, and description. We resolve the related contact or deal by matching on name or email against the records imported in prior phases. Task owner maps via email to Freshsales User. Daffodil CRM does not have a documented activity type taxonomy, so we infer task type from field names and values provided in the export.

Daffodil CRM call activity records migrate to Freshsales Task with subtype set to Call. Duration, disposition, and call outcome from Daffodil CRM map to Freshsales custom Task fields. Activity timestamp preserves the original call date for timeline ordering. Call notes migrate to the Task description field. If Daffodil CRM stores call recordings, we flag these as attachment references requiring manual handoff since file URLs may not be accessible post-migration.

Daffodil CRM meeting records map to Freshsales Event. Start datetime, end datetime, location, and meeting title migrate. Attendee information migrates to Freshsales Event contacts via the contact relationship resolved during import. Meeting notes migrate to the Event description or as an associated Note. If Daffodil CRM stores meeting type or outcome, these map to custom fields on the Event.

Daffodil CRM user and owner records map to Freshsales User accounts. We resolve by email address: each unique owner email in Daffodil CRM records is matched to a Freshsales User with the same email, which we provision before record import begins. Users without a match go to a reconciliation queue for the customer's admin to provision in Freshsales. Active and inactive status from Daffodil CRM carries forward as User status in Freshsales.

Daffodil CRM custom fields on Contacts, Companies, and Deals are exported as additional columns in the respective object CSV. We create matching custom fields in Freshsales (Admin Settings > Customize Fields) before data import, using Freshsales field types that best correspond to the Daffodil CRM data (text, number, date, picklist, multi-select picklist, checkbox). Multi-select picklist values require transformation: comma-separated Daffodil CRM values become individual Freshsales picklist option selections.

Daffodil CRM tags applied to contacts, companies, or deals export as comma-separated values or repeated rows. We parse the tag values and create Freshsales Tags during import, then apply them to the corresponding Contact, Account, or Deal records via the Freshsales Tags API. If Daffodil CRM uses a label system with hierarchical groupings, we flatten it to a single tag namespace in Freshsales to match the platform's flat tag model.