Migrate from Daylite to Freshsales

Daylite's single People object maps to Freshsales Lead for unqualified or new-source contacts and to Contact for qualified buyers. We split based on criteria defined during scoping: contacts with an active Opportunity in Daylite become Contacts in Freshsales; contacts without any Opportunity become Leads. Each Person's email, phone, address, and custom fields map to Freshsales equivalent fields. The original Person record type is preserved in a custom field daylite_person_type__c for audit.

Daylite Company records map directly to Freshsales Account. Every Daylite Person can link to one Company via the Company foreign key in the People CSV; we resolve this relationship at migration time so each Contact in Freshsales lands with the correct AccountId lookup. The Daylite Company industry, address, and custom fields map to Freshsales Account fields. Account is imported before Contact to satisfy the lookup dependency.

Daylite Opportunities map to Freshsales Deals. The Opportunity's Person and Company foreign keys resolve to ContactId and AccountId in Freshsales. Stage, value, probability, and close date transfer directly. Daylite's freeform stage text (plain strings with possible typos and variants) is deduplicated and presented as a stage normalization table during scoping before we create Freshsales stage definitions.

Daylite Opportunity stage names are not a centrally managed taxonomy; they are stored per record. We extract all unique stage strings from the Opportunities CSV, deduplicate them, and present a mapping worksheet so the customer maps each Daylite stage name to a Freshsales Sales Process stage. Stage probabilities migrate from Daylite where present or are assigned defaults during mapping. Typos and variant spellings in historical records are normalized per the agreed mapping.

Daylite Projects have no native equivalent in Freshsales. We map each Project to a Freshsales Deal with the Project name and status, and attach the Project's Tasks and Appointments as Notes to that Deal for reference. If the Time&Budget plugin was active, we include budget fields and cost thresholds as custom fields on the Deal. Customers who need full project management in Freshsales should pair this with a dedicated project tool post-migration.

Daylite Appointments export with start/end UTC timestamps, timezone, all-day flag, location, and linked Person and Project IDs. We create Freshsales Tasks of type Appointment (or Event if the customer enables Freshsales calendar features) with the original timestamps, location, and description preserved. The linked Person resolves to ContactId or LeadId; linked Project resolves to the Deal record we created from the Project mapping.

Daylite Tasks (standalone and sub-tasks) export with status, due date, priority, and assignee. Tasks linked to Projects carry a Project foreign key that resolves to the Deal we created during the Project mapping. Sub-tasks become child Tasks with a parent TaskId reference. Task assignment resolves by matching Daylite assignee email to Freshsales User email.

Daylite Notes attached to any object export with the target object type and ID. We create Freshsales Notes linked via the appropriate lookup (Contact, Account, Deal, or Lead) and preserve the note body text and original timestamp. Notes on Projects land on the corresponding Deal record.

Daylite Groups are static groupings of People or Companies. We export the group membership mapping table and recreate each Group as a Freshsales Tag applied to the corresponding Contacts, Leads, or Accounts. The customer chooses during scoping whether Groups map to Tags (flat) or Segments (filter-based). If Daylite Groups are used for segment-based campaigns, we document the segment criteria for recreation in Freshsales.

Daylite custom fields on People, Companies, Opportunities, Projects, Tasks, and Appointments are defined in a separate metadata table and values stored in record tables. We extract both, then present a mapping worksheet to match each Daylite custom field to a Freshsales custom field of equivalent type (text, number, date, picklist, checkbox). Custom field definitions are created in Freshsales before data import so values load into typed fields rather than falling into a catch-all.