Migrate from Daylite to HubSpot

Daylite People map directly to HubSpot Contacts. First name, last name, email, phone, job title, and address fields migrate as direct field mappings. Multi-company associations (Daylite allows a person linked to several companies) surface as secondary company associations in HubSpot's contact-company relationship model.

Daylite Companies map to HubSpot Companies with company name, domain/website, industry, employee count, and annual revenue as direct fields. Parent-child company hierarchies in Daylite map to HubSpot's Parent Company field. Multi-person associations collapse to the primary contact as defined in Daylite's primary-person flag.

Daylite Opportunities become HubSpot Deals. Deal name, amount, close date, and stage name migrate with stage values mapped via value_mapping per destination pipeline. Probability percentages transfer as custom fields if HubSpot's default stage-based probability doesn't match Daylite's custom probability model.

Daylite pipelines (if multiple exist) map to HubSpot deal pipelines. Each Daylite pipeline becomes one HubSpot pipeline. Stage names within each pipeline map value-by-value to HubSpot's stage pick-list for that pipeline. HubSpot allows up to 15 pipelines on Pro and 50 on Enterprise, so most Daylite configurations transfer without pipeline consolidation.

Daylite Projects have no direct HubSpot equivalent. We map projects to HubSpot Deals with custom properties for project-specific fields (budget, deliverables, deadline), OR to HubSpot Tickets if the project represents service delivery rather than a sales opportunity. Your team chooses the mapping strategy based on whether projects are pre-sale delivery scopes or post-sale work orders.

Daylite Tasks migrate to HubSpot Tasks. Subject, due date, completion status, and assigned owner transfer. Original due dates and times are preserved in HubSpot's hs_timestamp property, and overdue tasks retain their original timestamps. Daylite categories become either HubSpot task types or a custom multi-select property, ensuring segmentation remains intact. Owner assignment is resolved by email match to HubSpot user, with any unmatched owners flagged for review before the full run.

Daylite Appointments map to HubSpot Meetings. Start time, end time, location, body details, and linked contacts or companies transfer with original timestamps preserved, preserving historical context. All-day appointments set HubSpot's all-day flag. Recurring appointments explode into individual HubSpot Meeting records, each carrying the recurrence pattern as a custom property. Attendee participants are logged as HubSpot meeting invitees or linked via the associations API.

Daylite Notes migrate to HubSpot Notes. Rich-text body content transfers as-is for plain notes. Notes linked to specific records (people, companies, opportunities) associate to the corresponding HubSpot Contact, Company, or Deal via the association API. Original creation timestamps preserve the note's historical context.

Daylite categories (on opportunities, projects, tasks) have no HubSpot native equivalent. We map categories to a custom multi-select property in HubSpot (e.g., Opportunity_Category__c) so filtering and reporting remain intact. If Daylite uses many category values, we apply value_mapping to keep the pick-list clean.

Daylite Smart Lists are saved dynamic filter views that auto-update as records change. HubSpot Lists can be static (manual membership) or dynamic (criteria-based). Dynamic lists use enrollment triggers rather than saved filters. We export Smart List criteria as documentation for your HubSpot admin to build equivalent automation-triggered lists or static backup lists.

Daylite Activity Sets define a sequence of tasks and appointments tied to an opportunity or project stage. HubSpot Workflows handle automation but structure differs significantly. We export Activity Set definitions as a rebuild reference (step names, sequence order, timing rules) so your HubSpot admin can replicate the logic in HubSpot's workflow builder.

Daylite file attachments on people, companies, opportunities, and projects re-upload to HubSpot Files and attach to the corresponding record. File size limits apply (HubSpot allows files up to 25MB by default). Inline images in notes download and rehost as HubSpot-hosted assets.

Daylite Groups organize users and permissions, including team hierarchies and sharing rules. HubSpot Teams serve a similar function, grouping users for pipeline and record assignment. We map Daylite Groups to HubSpot Teams, preserving membership as HubSpot user-to-team associations. However, Daylite's granular permission model—particularly record-level sharing—has no direct HubSpot equivalent; achieving equivalent access control requires manual configuration, such as setting team-based visibility or custom property flags for record sharing.