Migrate from Daylite to HighLevel

Daylite People records map directly to GoHighLevel Contacts. The export CSV contains first_name, last_name, email, phone, address, and custom field columns. We use the email address as the dedupe key during GoHighLevel import and preserve the Daylite People ID in a custom field dl_people_id__c for audit. Groups that a Person belongs to migrate as tags on the Contact record.

Daylite Company records map to GoHighLevel Accounts. Every Person in Daylite can link to one Company via a foreign key; we resolve the Company lookup at migration time and set AccountId on each Contact during import to preserve the relationship. Company address, industry, and custom fields map to the corresponding Account custom fields.

Daylite Opportunities map to GoHighLevel Opportunities with pipeline stage mapping. Daylite stores stage names as plain text per Opportunity rather than a managed taxonomy; we deduplicate all unique stage strings from the export and present them as a stage mapping table so you explicitly map each Daylite stage name to a GoHighLevel pipeline stage. Opportunity value, probability, and close date migrate directly. The linked Person and Company foreign keys resolve to the Contact and Account records created in the prior migration phases.

Daylite Opportunity stages are freeform text strings stored per record, not a central stage definition. We extract every distinct stage value across all Opportunities and deduplicate the list. During scoping, we present this stage inventory and you map each to a GoHighLevel pipeline stage with a corresponding probability percentage. GoHighLevel pipelines are created in Settings before migration begins, and the stage mapping table drives the stage assignment during import.

Daylite Projects do not have a direct GoHighLevel equivalent. GoHighLevel has no native project management object. We offer two approaches: (1) create a GoHighLevel Custom Object named Project with custom fields for project name, status, start date, end date, and budget; or (2) map Projects to Opportunities with a dl_project_id__c custom field and store project metadata as Opportunity custom fields. The approach is chosen during scoping based on whether you need to track project-specific tasks and appointments separately from sales Opportunities.

Daylite Appointments carry UTC start/end timestamps, timezone, location, category, and a linked Person and Project ID. GoHighLevel's appointment system uses a separate Calendars and Locations model. We import Appointments as Task records with ActivityDate set to the original Daylite timestamp, preserving subject, start time, and location in custom task fields. If you intend to use GoHighLevel's appointment scheduler post-migration, we document which Daylite Appointments should be recreated as GoHighLevel Calendar events.

Daylite Tasks (standalone and sub-tasks) map to GoHighLevel Tasks. Status, priority, due date, and assignee migrate. Tasks linked to Projects carry a Project foreign key that we resolve against the Project mapping choice made in scoping (Custom Object or Opportunity). Sub-tasks become GoHighLevel Tasks with a custom parent_task_id__c field linking to the parent.

Daylite Notes attached to People, Companies, Opportunities, or Projects export with the target object type and ID. We write them to GoHighLevel as notes on the corresponding Contact or Opportunity record using the target ID to resolve the destination. Notes with no valid target record are flagged for manual assignment.

Daylite Groups are static groupings of People or Companies used for segmentation. They export as a membership mapping table. We recreate group membership in GoHighLevel as tags on Contact and Account records. The mapping worksheet lets you confirm whether each Daylite Group becomes a GoHighLevel tag, a GoHighLevel Contact list, or a Smart List segment.

Daylite custom field definitions live in a separate metadata table alongside the record data. We extract both the definition table (field name, type, options) and the value table and present them as a mapping worksheet. In GoHighLevel, custom fields are either Contact-scoped or Opportunity-scoped with no switching after creation, so each Daylite custom field must be assigned a GoHighLevel scope during scoping. Field types (text, date, number, picklist) map to GoHighLevel equivalents; multi-select picklists in Daylite map to GoHighLevel multi-select fields.

iOSXpert plugins (Time&Budget, FinanceConnector) write data into additional tables within Daylite's database. We audit the exported table list for plugin signatures during scoping. Where those tables are present, we migrate them to GoHighLevel as custom fields on the relevant object (Project or Opportunity) or as a dedicated Custom Object depending on the plugin's data structure. If the plugin was not installed when the export was generated, those tables will be absent from the export and the data cannot be recovered without a fresh export with the plugin active.