Migrate from Daylite to Twenty CRM

Daylite Company records map directly to Twenty CRM Company records. Address, industry, and custom properties migrate as text or field-type-matched columns. Company is the 'one' side of the Person-Company relationship and must be imported first per Twenty CRM's documented import order. We use the Daylite company ID as an external identifier to resolve Person-Company linkages during the People import phase.

Daylite People records map to Twenty CRM Person records. Name, email, phone, and address fields migrate directly. Each Person carries a Company foreign key; we resolve this by first importing Companies and then inserting Person records with the matched Twenty Company ID. Daylite allows one Company per Person, matching Twenty's Person-Company relationship model.

Daylite Opportunities map to Twenty CRM Opportunity records with stage, value, probability, and close date preserved. Daylite stores pipeline stages as freeform text per Opportunity; we deduplicate all unique stage strings from the export and present them as a mapping table for your admin to define as valid stage values in Twenty CRM's workspace settings before import. This is a required pre-import step; stage normalization happens before Opportunity records are inserted.

Daylite's freeform stage text is normalized into Twenty CRM's stage configuration. We extract every unique stage string from the Opportunities CSV, deduplicate it, and present the list as a mapping worksheet. Your admin defines the stage names and probability percentages in Twenty CRM's workspace settings. Historical opportunities with stage typos or variant names will be remapped to the corrected stage value during import.

Daylite Project records map to a custom Project object in Twenty CRM. Status, dates, and budget fields migrate as text fields unless your admin specifies typed equivalents. If the iOSXpert Time&Budget plugin is active and its tables are present in the export, budget and cost threshold data migrates to additional custom fields on the Project object. Projects are imported after Opportunities and before Tasks, following Twenty's dependency order.

Daylite Tasks (both standalone and sub-tasks) map to Twenty CRM Task records. Status, due date, priority, and assignee migrate directly. Tasks linked to Projects carry a Project foreign key that we resolve after the Project import phase. Sub-tasks maintain parent-child hierarchy through a custom parent_task_id__c field that we populate during import.

Daylite Appointments map to Twenty CRM Task records with an event-like structure. UTC start and end timestamps, timezone, all-day flag, location, and category migrate as custom fields or as part of the Task's description and due date fields. The linked Person and Project IDs resolve against the already-imported Person and Project records. Calendar chronology is preserved by ordering Task records by the original appointment timestamp.

Daylite Notes (freeform text attached to any object) map to Twenty CRM Comment records linked via the target object type and ID. We write the note body as the Comment text and link it to the corresponding Person, Company, Opportunity, or Project record using Twenty's object-comment relationship model.

Daylite static Groups (People or Company groupings) map to Twenty CRM Workspace Tags. The group membership table (Group-Record-ID pairs) becomes a set of TagAssignment records linked to the migrated Person or Company. Your admin decides during scoping whether to create a flat tag list or a hierarchical tag structure in Twenty.

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, present each custom field with its type and options, and your admin confirms the target field name and type in Twenty CRM. Text fields map directly; picklist-type custom fields map to Twenty's select fields with the same option values.

Daylite attachments are bundled into the compressed export as a flat folder with filenames referencing parent object type and ID. We reattach files to the corresponding Person, Company, Opportunity, or Project record in Twenty CRM by parsing the filename, resolving the parent ID, and uploading through Twenty's attachment API. Attachment volume affects migration timeline significantly for large file libraries.

Daylite's tag system (used across objects) is exported as a separate lookup table. We map each Daylite tag to a Twenty CRM Workspace Tag, then write the tag associations as TagAssignment records linked to the relevant Person, Company, Opportunity, or Project. Tag names are preserved verbatim unless your admin requests normalization.