Daylite to Salesforce migration
We migrate People, Companies, Opportunities, and Appointments from Daylite into Salesforce with the People-to-Lead-or-Contact split resolved during scoping, project history preserved as custom fields, and every iOSXpert plugin table audited from the export before a single record is imported through the Bulk API.
FlitStack AI migrates lead or contacts, accounts, opportunities, opportunity stages and custom objects from Daylite to Salesforce, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 4-6 weeks.

What moves from Daylite to Salesforce?
Daylite and Salesforce have structurally different data models that require deliberate mapping decisions before migration begins.
Read the full summary
Daylite's unified People object does not map directly to either Salesforce Lead or Contact; the split rule must be defined during discovery based on whether each Person has an associated Opportunity. Companies map 1:1 to Salesforce Account, and Opportunities map to Opportunity with stage names normalized from Daylite's plain-text values to Salesforce's picklist. Daylite Projects have no direct Salesforce equivalent; we preserve them as a custom object with custom fields. Appointments and Tasks migrate as Event and Task respectively, with UTC timestamps and attendee relations reconstructed. Groups, Tags, and plugin-stored data require configuration-level decisions during scoping. We do not migrate Billings Pro records, Daylite Workflows, or automations as code; we deliver written inventories for the customer's admin to rebuild post-migration.
People → Lead or Contact (split required)
Daylite People with at least one linked Opportunity map to Salesforce Contact attached to the corresponding Account.
How it maps
Daylite People with no linked Opportunity map to Salesforce Lead. The split is evaluated at migration time by querying the Opportunity foreign key in the People table. We preserve the original Daylite Person ID in a custom field daylite_person_id__c on both Lead and Contact for audit and cross-referencing. Any Person marked as a Company contact (is_company_primary_contact flag) is treated as a Contact regardless of Opportunity status.
Company → Account
Daylite Company records map directly to Salesforce Account.
How it maps
The Company name becomes Account Name; the address fields map to BillingAddress. The Daylite Company ID is preserved in a custom field daylite_company_id__c. Accounts are imported before any People migration so that AccountId lookup references are satisfied at Contact insert time. Multiple Daylite People linked to the same Company all resolve to the same AccountId.
Opportunity → Opportunity
Daylite Opportunities map to Salesforce Opportunity with the linked Person resolved to Contact (via the AccountId chain) and the linked Company resolved to AccountId.
How it maps
The Opportunity monetary value maps to Amount, probability maps to a probability percentage we derive from the Daylite stage mapping table, and close date maps to CloseDate. Stage names are normalized from Daylite plain-text strings to the Salesforce Sales Process stage picklist via the stage mapping table produced during scoping.
Pipeline Stage → Opportunity Stage
Daylite Opportunity stages are freeform text strings with no managed taxonomy.
How it maps
We extract every distinct stage value from the export, deduplicate variants (handling typos and case differences), and present a stage mapping table during scoping. Each unique Daylite stage maps to a Salesforce stage name and probability percentage that the customer approves before migration. The mapping becomes a Salesforce Sales Process deployed to the Sandbox before production import.
Project → Custom Object (Project__c)
Daylite Projects have no native Salesforce equivalent.
How it maps
We pre-create a Project__c custom object in the destination org during schema design, with custom fields for project status, start and end dates, budget amount, linked Company (Account lookup), and linked Person (Contact lookup). Project tasks migrate as Task records linked to the Project__c parent via WhatId. If the iOSXpert Time&Budget plugin tables are present in the export, budget and cost data migrate to custom numeric fields on Project__c.
Task → Task
Daylite Tasks map to Salesforce Task with Status, Priority, ActivityDate, and Description preserved.
How it maps
Standalone Tasks carry no WhatId reference. Tasks linked to a Project carry the Project__c custom object ID as WhatId. Task assignment maps by resolving the Daylite owner ID to Salesforce UserId via the owner mapping produced during scoping. Sub-tasks inherit the parent Task ID as a custom parent_task__c field.
- PeopleLead or Contactsplit
- CompanyAccount1:1
- OpportunityOpportunity1:1
- Pipeline StageOpportunity Stagetransformed
- ProjectCustom Objecttransformed
- TaskTask1:1
+ 7 more in the mapping below
How Daylite and Salesforce differ
The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.
| Dimension | Daylite | Salesforce |
|---|---|---|
| Platform availability | Apple macOS, iOS, and iPadOS only | Browser, Windows, macOS, iOS, Android, and Linux web access |
| Contact model | Single People object for all contacts regardless of qualification status | Separate Lead (unqualified prospect) and Contact (qualified, tied to Account) objects |
| Pipeline stages | Freeform plain-text stage names stored per Opportunity | Managed stage picklist with probability percentages tied to a Sales Process |
| Project management | Built-in native Projects, Tasks, and Appointments with budget tracking | No native project object; requires custom object configuration or an AppExchange PM app |
| Pricing model | Single-tier $20.83/user/month with all features included | Edition tiers from $25/user/month (Essentials) to $330/user/month (Unlimited) with feature gating |
| Custom objects | Custom fields on standard objects; no standalone custom object type | Full custom object (__c) support from Professional tier ($80/user/month) |
| Group/segment model | Static Groups of People or Companies as a native object | No native static Groups; recreated as tags, segments, or campaign membership |
What to watch for in a Daylite to Salesforce migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Daylite export download link expires after 14 days
When Daylite generates a full database export from Account Settings > My Info > Create Data Export, it produces a compressed archive of CSVs and an attachments folder.
How we handle it
The download link for that archive is valid for only 14 days. If the link expires before scoping is complete, a new export must be triggered. We confirm link validity at the start of every engagement and request a fresh export if needed before any import work begins.
Daylite People must split into Lead and Contact
Daylite has a single People object for all contacts regardless of whether they are unqualified prospects or active customers.
How we handle it
Salesforce separates unqualified leads from qualified contacts attached to accounts. We resolve this by splitting on the Opportunity relationship: Daylite People with at least one linked Opportunity become Salesforce Contacts under the corresponding Account; Daylite People with no Opportunity become Salesforce Leads. The split rule is defined during discovery and applied as a transform step before any Salesforce insert. We preserve the original Daylite Person ID in a custom field for audit.
Opportunity stage names require explicit normalization
Daylite Opportunity stages are freeform plain-text strings stored per record, not a managed picklist.
How we handle it
Typo variants and inconsistent capitalization in historical records are preserved verbatim in the export. We deduplicate all unique stage values and present them as a mapping table during scoping so the customer explicitly maps each Daylite stage to a Salesforce stage name and probability percentage. This mapping becomes a Salesforce Sales Process deployed before production import. Without this step, imported Opportunities may have invalid stage values that fail Salesforce validation rules.
Plugin tables are absent if the plugin was not installed at export time
iOSXpert extensions write to additional tables within Daylite's database.
How we handle it
If a customer exported their database before installing Time&Budget or FinanceConnector, those plugin tables will not appear in the export and the data cannot be recovered from Daylite alone. We audit the exported table list for plugin signatures during scoping and flag any absent plugin tables for the customer to confirm whether that data should be included and whether it exists elsewhere. We do not infer plugin data from historical records if the plugin tables are missing.
Billings Pro records live in a separate application and do not export
Billings Pro is a separate Marketcircle application (now Cloud-only, self-serve discontinued).
How we handle it
Its invoices and billing records do not appear in Daylite's database export. Customers with billing records to preserve must export them from Billings Pro independently before their Marketcircle account transitions. We do not migrate Billings Pro data as it requires a separate Billings Pro export process that is outside Daylite's data export scope.
How the migration runs
Export validation and scoping
We begin by confirming that the Daylite database export download link is still active.
What this step covers
If it has expired, we request a fresh export before proceeding. We ingest the CSV tables and audit the schema: we identify all present tables, check for iOSXpert plugin table signatures (Time&Budget, FinanceConnector), flag absent plugin tables for customer confirmation, and extract the custom field definition table alongside the value tables. We produce a scoping document listing all migratable objects, record counts per table, and a preliminary object mapping summary before any schema design begins.
Schema design in Salesforce Sandbox
We design the destination schema in a Salesforce Full Copy or Partial Copy Sandbox.
What this step covers
This includes provisioning the Project__c custom object with custom fields, creating any custom fields from Daylite's custom field metadata table on People, Company, Opportunity, Task, and Event, defining Salesforce Sales Process and stage picklist values from the deduplicated stage mapping table, configuring the Group recreation strategy (campaigns, multi-select picklist, or topics), and creating any required record types. Schema is deployed via Salesforce metadata API into the Sandbox for validation before production.
Sandbox migration and record reconciliation
We run a full migration into the Sandbox using production-like data volume.
What this step covers
The customer's admin reviews record counts across all objects, spot-checks 25-50 records per object against the Daylite source, validates the Lead-Contact split logic, confirms stage name normalization, and reviews the Project__c custom object structure. We resolve any mapping corrections in the Sandbox before proceeding to production. This step prevents mapping errors from reaching production data.
Owner reconciliation and User provisioning
We extract every distinct Daylite owner referenced on People, Company, Opportunity, Task, Appointment, and Note records and match by email address against the Salesforce destination org's User table.
What this step covers
Any Daylite owner without a matching Salesforce User is placed in a reconciliation queue. The customer's Salesforce admin provisions the missing Users (active for current team members, inactive for departed users whose records must be reassigned) before record import proceeds. OwnerId references must be valid at insert time for most standard Salesforce objects.
Production migration in dependency order
We execute production migration in strict dependency order: Accounts (from Companies) first, then Leads and Contacts with the split rule applied and AccountId lookups resolved, then Opportunities with AccountId, OwnerId, and stage values resolved, then Project__c records with custom field data, then Tasks and Events with parent WhatId references, then Notes as ContentDocumentLink records, then attachments as ContentVersion.
What this step covers
Each phase emits a row-count reconciliation report before the next phase begins. Activity history volumes exceeding CSV loader capacity are migrated via the Salesforce Bulk API 2.0 with batch chunking and exponential backoff on rate limit responses.
Cutover, validation, and rebuild handoff
We freeze Daylite writes during the cutover window, run a final delta migration of any records modified during the migration window, then enable Salesforce as the system of record.
What this step covers
We validate record counts, spot-check a second sample against Daylite source data, and deliver a migration summary report to the customer's admin. We deliver a written inventory of every Daylite automation or workflow with a recommended Salesforce Flow equivalent for the admin or a Salesforce partner to rebuild. We support a one-week post-cutover window for reconciliation issues. We do not rebuild Daylite automations as Salesforce Flow inside the migration scope.
Daylite - Connect
- Map
- Sample
- Migrate
- Verify
- Contacts48,210 / 48,210 Done
- Companies9,134 / 9,134 Done
- Deals6,377 / 11,920 In progress
- Before sample runRestore point 01Restore
- Before full migrationRestore point 02Restore
- After verificationRestore point 03Current
How long it takes, and what drives the quote
A quote scales with record volume, project history scope, and whether iOSXpert plugin tables are present in the export. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Daylite to Salesforce →Why teams move from Daylite to Salesforce
- Apple-only deployment becomes a hard constraint when teams grow beyond macOS users. Daylite has no web interface, no Windows or Linux desktop access, and no Android mobile app, which forces cross-platform teams to choose between staying in the Apple ecosystem or moving their CRM. Salesforce runs in any browser and has native apps for every major mobile platform, making it the default destination for teams that have expanded beyond Apple-only environments.
- Daylite's integration surface is narrow compared to Salesforce's AppExchange ecosystem. Teams that need native ERP connectors, CPQ, contract lifecycle management, revenue intelligence, or advanced BI tools move to Salesforce because those integrations are AppExchange-certified or first-party rather than requiring Zapier routing or unsupported API workarounds.
- Daylite has no native custom object capability. As teams add non-standard data types (properties, subscriptions, assets, contracts) that do not fit People, Companies, or Opportunities, they hit the ceiling of Daylite's flat object model. Salesforce supports full custom objects with lookup relationships, validation rules, and page layouts from the Professional tier, removing the data model constraint that drives mid-market migrations.
- Daylite's project management capability is self-contained and Apple-native, which limits visibility for cross-functional teams. Organizations that have grown beyond a single-department CRM need Salesforce's platform to give sales, service, marketing, and operations a shared record model with cross-departmental reporting and shared pipeline visibility.
- Daylite's 14-day export download window and sparse API documentation create data portability risk. Teams that have committed to Daylite for years face a non-trivial export process that must be executed within a narrow window and produces CSVs requiring manual column mapping before any migration tooling can ingest them. Salesforce's Bulk API 2.0 and REST API are publicly documented, rate-limited, and support batch ingestion, removing the ad-hoc export risk that characterizes Daylite exits.
Questions, answered
Daylite to Salesforce migration questions
How long does a Daylite to Salesforce migration take?
Most Daylite migrations land between four and six weeks for accounts with under 10,000 People, 2,000 Companies, and no iOSXpert plugin tables to audit. Migrations with project history requiring a Project__c custom object, large appointment and task histories (over 100,000 records), multiple Daylite Groups, or plugin data move to ten to fourteen weeks because of custom field schema design, sandbox validation cycles, and the owner reconciliation phase before production import begins.
Do Daylite Workflows and automations migrate to Salesforce Flow?
No. Daylite's automation rules and Salesforce Flow are structurally different automation systems that do not share a common interchange format. We do not migrate automations as code. We deliver a written inventory of every active Daylite workflow, rule, or automation with its trigger, conditions, and actions and a recommended Salesforce Flow equivalent that the customer's admin or a Salesforce partner rebuilds post-migration. This inventory is included in the handoff documentation at cutover.
Can we migrate Daylite Projects to Salesforce?
Daylite Projects have no direct Salesforce equivalent, but we handle them as a custom object migration. We pre-create a Project__c custom object in the destination org during schema design with custom fields for status, dates, budget, and linked Account and Contact lookups. Linked Tasks migrate as Salesforce Task records with WhatId pointing to the Project__c parent. If the Daylite export includes iOSXpert Time&Budget plugin tables, budget and cost data migrate to custom numeric fields on Project__c. The custom object is validated in a Sandbox before production deployment.
Do Daylite Groups and Tags migrate to Salesforce?
Daylite Groups and Tags require a configuration decision during scoping. Groups (static People or Company groupings) can be recreated as Salesforce Campaigns with CampaignMember membership, as a custom multi-select picklist on Contact, or as Salesforce Topics. Tags (cross-object string labels) can map to a custom Label__c multi-select picklist or to Salesforce Labels. The customer chooses the strategy during scoping, and we implement it consistently across all migrated records. Neither Groups nor Tags migrate as native Salesforce objects because no equivalent exists.
Can we keep Daylite running for project management while moving CRM to Salesforce?
Yes. A hybrid stack is feasible but requires the customer to maintain two separate subscriptions. Daylite would continue handling Projects, Tasks, and Appointments while Salesforce manages Accounts, Contacts, Opportunities, and the sales pipeline. There is no native Daylite-to-Salesforce sync connector, so cross-system data consistency must be maintained manually or through a custom integration the customer builds. We do not build or maintain that integration as part of the migration scope.
What happens to our Daylite Notes and Appointments during migration?
Daylite Notes migrate as Salesforce Note records linked via ContentDocumentLink to the parent Contact, Account, Opportunity, or Project__c. Appointment data migrates as Salesforce Event records with StartDateTime, EndDateTime, Location, and IsAllDayEvent preserved. Attendee links become EventRelation records pointing to the resolved Contact or Lead. All timestamps are converted to UTC from Daylite's local time before insert. The Daylite note and appointment creation timestamps are preserved in custom fields on the migrated records for audit.
What data do you not migrate from Daylite?
We do not migrate Billings Pro records (invoices, billing data), Daylite automations or workflows (these require a separate rebuild inventory), or iOSXpert plugin data if the plugin was not installed at the time of the Daylite export (plugin tables will be absent from the CSV archive). We do not migrate Daylite reports, dashboards, or form configurations. We deliver a written inventory of these items at cutover so the customer's admin knows exactly what requires manual recreation in Salesforce.
Related migrations
Salesforce implementation
Set up Salesforce and migrate into it as one engagement.
See the service → Convertkit to SalesforceMapping · history · rollbackCopper to SalesforceMapping · history · rollbackSuperOffice CRM to SalesforceMapping · history · rollbackHousecall Pro to SalesforceMapping · history · rollbackFotoNotes to SalesforceMapping · history · rollbackHoneyBook to SalesforceMapping · history · rollback Daylite to PipedriveMapping · history · rollbackDaylite to Zoho CRMMapping · history · rollbackSources: official documentation
- Custom Field Attributes — Salesforce Help (External ID)
- Increase Limit of Salesforce Big Object Storage Allocation — Salesforce Help
- Uploading Activity data to Salesforce — Salesforce Stack Exchange
- Sandboxes — Staging Environments for Customizing and Testing
- Case Comment STRING_TOO_LONG — Salesforce Stack Exchange
- Salesforce Data Migration: 7 Challenges and How to Solve Them — DEV
- Salesforce Duplicate Management — Salesforce Stack Exchange
Get a quote
Moving from Daylite to Salesforce?
Tell us roughly how many records and objects you have. We scope the mapping and the Salesforce setup with you, then send a quote.
Get a quote