Daylite to HubSpot
Small-business CRM for Mac, iPhone and iPad that manages contacts, companies, deals, projects and appointments.
Daylite data can move into HubSpot, landing mainly in Sales Hub. 2 of 7 mapped objects move directly (Contacts (people) and Companies (organizations)); 4 items need manual work and 2 do not move. Plan roughly 2-4 weeks for a small move and 8-14 weeks for a large one.
Migration checklist for Daylite
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 5 doneDuring
0 of 5 doneAfter
0 of 5 doneWhat will it take?
No price list: cost follows volume, custom objects and how much logic must be rebuilt. Answer four quick questions for a planning range.
The three scenarios
Small migration
<10k records
CSV import.
Mid migration
10k-100k records
Needs ID mapping and an association audit.
Large migration
>100k records plus many attachments
Scripted ETL plus a custom object for projects.
What moves the number
Timeline ranges are planning estimates, not a quote. A partner confirms scope after discovery.
Access, mapping and limits
Start with how data leaves Daylite: what you need to get in, what lands in HubSpot, and what will not.
REST API (api.marketcircle.net/v1) with webhooks, according to a third-party page
A Daylite Cloud account with an API token or OAuth app. Superuser or admin rights are needed for a full export.
Superuser/admin is needed to start a full data export.
Choose your route
How will you move the data?
No native connector was found.
- You need: A Daylite Cloud account with an API token or OAuth app. Superuser or admin rights are needed for a full export.
- Permission: Superuser/admin is needed to start a full data export.
Native imports often bring over only some data, so check coverage per object in the mapping below.
Export each object, clean it, then import it into HubSpot.
- Full Daylite Cloud data export (Superuser only): .tgz/.tar archive with all tables as CSV plus attached files
- List-view export of visible columns and selected rows to CSV or tab-delimited from the Mac app
- REST API extraction
- vCard export of contacts
Limits: To confirm
Migration and sync tools can move more than a plain import. Confirm which objects each one supports before you choose.
Best when volume is high, custom objects are many or automation is heavy. That is the Large scenario: 8-14 weeks, usually phased.
Talk to a partnerWhere each object lands
In Daylite
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Contacts (people) | Contacts | yes | The full export includes all tables as CSV; the API also exposes contacts. |
| Companies (organizations) | Companies | yes | Company records link to contacts, appointments and a category; contact-to-company links need preserved IDs. |
| Opportunities | Deals | partial | Opportunities and pipelines are listed as importable and exportable; stages and pipelines must be recreated in HubSpot first. |
| Appointments, tasks and notes | Meetings, Tasks, Notes | partial | The data is available in the export; association coverage must be audited and the records re-associated via IDs. |
| Projects | Custom objects | manual | HubSpot has no native equivalent; use a custom object or a deal pipeline. |
| Users | Contact owner (HubSpot users) | manual | Map Daylite users to HubSpot owners by email. |
| Attached files | Files | partial | Attachments are included in the full export archive. |
What to expect
These are configuration rather than exported data; they must be rebuilt in HubSpot.
The sources do not show whether email content is exported; coverage is unverified.
Daylite's schema differs from HubSpot's.
Not part of the data export.
Exports are flat CSV tables.
Daylite uses generic extra fields.
Keep the Daylite primary keys in HubSpot properties and import associations separately.
Validate fields against the actual export.
Prefer the bulk CSV export and throttle any API pulls.
Arrange Superuser access early.
Data governance and compliance
Decide what is allowed to move before anything is exported. Tick each gate once it is agreed.
How we researched this page
How much to trust each section, and where it comes from.
Export paths (full Cloud data export, CSV list export) and the API are sourced, but mostly from partner and third-party pages. No HubSpot doc covers Daylite, and the object-to-HubSpot mapping is analyst inference.
Sources
Related migrations
Frequently asked questions
How do I migrate Daylite to HubSpot?
1. Confirm a Superuser can run Preferences > Account > Export All Data. 2. Inventory the Daylite categories, pipelines, custom fields and users. 3. Create matching HubSpot properties, pipelines and owners. 4. Decide how to handle projects (custom object or deal pipeline).
What data can move from Daylite to HubSpot?
These objects move directly: Contacts (people) and Companies (organizations). Check the mapping table for partial and manual items.
What does not move from Daylite to HubSpot?
Automations, permissions and saved reports/smart lists and Sent emails and letters stored in Daylite. Plan to rebuild or retire these.
How long does a Daylite to HubSpot migration take?
Small (<10k records): 2-4 weeks. Mid (10k-100k records): 4-8 weeks. Large (>100k records plus many attachments): 8-14 weeks. These are planning estimates, not a quote.
What access do I need to export from Daylite?
A Daylite Cloud account with an API token or OAuth app. Superuser or admin rights are needed for a full export. Superuser/admin is needed to start a full data export.
What compliance issues apply when moving Daylite data?
Check: Possible health or financial client notes in a cross-industry CRM. Agree consent, retention and access rules before exporting.
Moving Daylite into HubSpot?
A network of 153+ tiered HubSpot partners and 1,800+ accounts of experience. Tell us what you are moving and which hub matters most.
Talk to a partner