Migrate your Daylite data
Apple-native CRM and project management tool for small businesses on Mac, iPhone, and iPad. Deeply integrated with Apple Contacts, Calendar, Mail, and Siri, but the ecosystem lock-in makes migrations unusually difficult.
In its favor
Why people choose Daylite
The signal that keeps Daylite on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Apple ecosystem depth — Daylite integrates directly with Apple Contacts, Calendar, Mail, and Siri, giving Mac-native teams a seamless experience that feels built-in rather than bolted on.
Small-business focus — with a target customer of up to 100 employees, Daylite avoids enterprise complexity and delivers CRM fundamentals without overwhelming configuration overhead.
Project management bundled in — unlike pure CRMs, Daylite includes Projects, Tasks, and Appointments in one application, reducing the need for a separate PM tool.
Structured data ownership — Daylite allows full database export to CSV at any time, ensuring customers can retrieve their data without a formal data portability request process.
Competitive single-tier pricing — at $20–25 per user per month with no add-on tiers, the cost model is transparent and predictable for small teams.
Apple-only platform becomes a constraint — teams that need web access, cross-platform mobile support, or Windows/Linux compatibility hit a hard wall and must migrate away entirely.
Limited third-party integrations — compared to cloud-first CRMs with deep Zapier, API, or native connector ecosystems, Daylite's integration surface is narrow, frustrating teams needing to connect billing, marketing, or analytics tools.
Steep learning curve for non-power users — the rich object model and deep Apple integration come with complexity that new team members find intimidating without dedicated onboarding.
Plugin ecosystem fragility — iOSXpert plugins are third-party and must be maintained alongside Daylite updates; plugin breakage or abandonment leaves data stranded in non-standard tables.
Data export limitations — while CSV export is possible, the 14-day download window and manual column-selection process make large or automated migrations difficult to execute reliably.
Reasons to switch
Why people leave Daylite
The recurring reasons buyers give for replacing Daylite. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Daylite fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Daylite pricing overview
Daylite uses a single-tier pricing model at $20.83 per user per month on annual billing or $25 on monthly billing, with no feature tiers or add-on bundles. The price includes all core CRM and project management features; iOSXpert plugins are separately purchased.
Standard
Tier 1 of 1
$20.83/user/month (annual) or $25/user/month (monthly)
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Daylite's schedule — see our quote-based pricing →
What gets migrated
Daylite object support
Object-by-object support for Daylite migrations. Per-pair details surface during scoping.
People
Fully supportedPrimary contact object. Exported as a distinct CSV table with name, email, phone, address, and custom fields. Relationships to Companies and Opportunities are preserved via foreign key columns in those respective tables.
Companies
Fully supportedOrganization/Account-level records. Exported with full address, industry, and custom properties. Every Person can link to one Company; we map this 1:1 during migration and preserve the linkage.
Opportunities
Fully supportedPipeline deals tied to a Person and Company. Exports include stage, value, probability, and close date. Pipeline stage names are customizable and exported as plain text values that we map explicitly to the destination pipeline.
Projects
Fully supportedProject records with status, dates, and budget fields. When iOSXpert Time&Budget plugin is active, budget and cost threshold data lives in additional tables we also export. We include all linked Tasks under their parent Project.
Appointments
Fully supportedCalendar events with UTC start/end timestamps, timezone, all-day flag, location, and category. Exports include the linked Person and Project IDs. We reconstruct the calendar chronology during import using the UtcStart field.
Tasks
Fully supportedStandalone tasks and sub-tasks exported with status, due date, priority, and assignee. Tasks linked to Projects carry a Project foreign key we follow to maintain parent-child hierarchy in the destination.
Notes
Fully supportedFreeform text notes attached to any object. Exports include the target object type and ID. We write them to the destination as comments or note objects on the corresponding record.
Groups
Fully supportedStatic groupings of People or Companies used for segmentation. Exported as a simple mapping table of group membership. We recreate group membership as tags or segments in the destination CRM.
Custom Fields
Mapping requiredDaylite supports custom fields on People, Companies, Opportunities, Projects, Tasks, and Appointments. Custom field definitions are included in the export. We inspect each custom field type (text, date, number, picklist) and map it to the nearest equivalent in the destination schema, flagging any unsupported field types for review.
Attachments
Mapping requiredFiles attached to any record are bundled into the compressed export as a flat folder alongside the CSVs. Attachment filenames reference the parent object type and ID. We reattach files to the correct record in the destination by parsing the filename mapping. Binary file integrity is preserved during transfer.
Tags
Mapping requiredDaylite uses a tag system across objects. Tags are exported as a separate lookup table. We map tags to labels, categories, or custom multi-select fields depending on the destination platform's capabilities.
Pipeline Stages
Mapping requiredOpportunity stages are user-configurable. We extract the current stage definitions from the export and present them as a mapping table so the customer explicitly maps each stage name and probability to the destination pipeline.
Billings Pro Records
Not in this platformBillings Pro is a separate application (now Cloud-only, self-serve EOL). Its invoices and billing records do not live in Daylite's database. We do not migrate Billings Pro data; the customer must export it separately from Billings Pro if needed.
iOSXpert Plugin Data
Mapping requiredThird-party iOSXpert plugins (Time&Budget, FinanceConnector) store data in additional tables within Daylite's database. Where those tables are present in the export, we migrate them. However, plugin-specific data depends on the plugin being installed during export; we cannot retrieve plugin data that was stored before the plugin was added.
| Object | Support | Notes |
|---|---|---|
| People | Fully supported | Primary contact object. Exported as a distinct CSV table with name, email, phone, address, and custom fields. Relationships to Companies and Opportunities are preserved via foreign key columns in those respective tables. |
| Companies | Fully supported | Organization/Account-level records. Exported with full address, industry, and custom properties. Every Person can link to one Company; we map this 1:1 during migration and preserve the linkage. |
| Opportunities | Fully supported | Pipeline deals tied to a Person and Company. Exports include stage, value, probability, and close date. Pipeline stage names are customizable and exported as plain text values that we map explicitly to the destination pipeline. |
| Projects | Fully supported | Project records with status, dates, and budget fields. When iOSXpert Time&Budget plugin is active, budget and cost threshold data lives in additional tables we also export. We include all linked Tasks under their parent Project. |
| Appointments | Fully supported | Calendar events with UTC start/end timestamps, timezone, all-day flag, location, and category. Exports include the linked Person and Project IDs. We reconstruct the calendar chronology during import using the UtcStart field. |
| Tasks | Fully supported | Standalone tasks and sub-tasks exported with status, due date, priority, and assignee. Tasks linked to Projects carry a Project foreign key we follow to maintain parent-child hierarchy in the destination. |
| Notes | Fully supported | Freeform text notes attached to any object. Exports include the target object type and ID. We write them to the destination as comments or note objects on the corresponding record. |
| Groups | Fully supported | Static groupings of People or Companies used for segmentation. Exported as a simple mapping table of group membership. We recreate group membership as tags or segments in the destination CRM. |
| Custom Fields | Mapping required | Daylite supports custom fields on People, Companies, Opportunities, Projects, Tasks, and Appointments. Custom field definitions are included in the export. We inspect each custom field type (text, date, number, picklist) and map it to the nearest equivalent in the destination schema, flagging any unsupported field types for review. |
| Attachments | Mapping required | Files attached to any record are bundled into the compressed export as a flat folder alongside the CSVs. Attachment filenames reference the parent object type and ID. We reattach files to the correct record in the destination by parsing the filename mapping. Binary file integrity is preserved during transfer. |
| Tags | Mapping required | Daylite uses a tag system across objects. Tags are exported as a separate lookup table. We map tags to labels, categories, or custom multi-select fields depending on the destination platform's capabilities. |
| Pipeline Stages | Mapping required | Opportunity stages are user-configurable. We extract the current stage definitions from the export and present them as a mapping table so the customer explicitly maps each stage name and probability to the destination pipeline. |
| Billings Pro Records | Not in this platform | Billings Pro is a separate application (now Cloud-only, self-serve EOL). Its invoices and billing records do not live in Daylite's database. We do not migrate Billings Pro data; the customer must export it separately from Billings Pro if needed. |
| iOSXpert Plugin Data | Mapping required | Third-party iOSXpert plugins (Time&Budget, FinanceConnector) store data in additional tables within Daylite's database. Where those tables are present in the export, we migrate them. However, plugin-specific data depends on the plugin being installed during export; we cannot retrieve plugin data that was stored before the plugin was added. |
Gotchas
What to watch for in Daylite migrations
Issues we've hit on past Daylite migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Database export download expires after 14 days
Billings Pro self-serve is discontinued, cloud migration required
Plugin-stored data is only exportable if the plugin is installed
Custom field definitions must be manually mapped
Pipeline stage names are plain text, not a managed taxonomy
| Severity | Issue |
|---|---|
| High | Database export download expires after 14 days |
| High | Billings Pro self-serve is discontinued, cloud migration required |
| Medium | Plugin-stored data is only exportable if the plugin is installed |
| Medium | Custom field definitions must be manually mapped |
| Low | Pipeline stage names are plain text, not a managed taxonomy |
Leaving Daylite?
Where Daylite customers move next
12 destinations Daylite can migrate to.
How a Daylite migration works
Four steps, Daylite-specific
Connect
OAuth 2.0 (with personal-token shortcut for single-account use) into Daylite. Scopes limited to read-only on the data we move.
Map
We translate Daylite-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Daylite quirks before production.
Migrate
Full migration with Daylite rate-limit handling. Rollback available throughout.
FAQ
Daylite migration FAQ
Answers to the questions buyers ask most during Daylite migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Daylite migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Daylite.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Daylite setup and destination — written quote back within a business day.