Daylite to Pipedrive migration
We migrate People, Companies, Opportunities, and Engagements from Daylite into Pipedrive using Daylite's CSV database export as the source, resolving the freeform Opportunity stage names and 1:1 Company-to-Organization relationships before any data lands in Pipedrive's cloud-native sales pipeline.
FlitStack AI migrates persons, organizations, deals, pipeline stages and deal or projects from Daylite to Pipedrive, 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: 2-4 weeks.

What moves from Daylite to Pipedrive?
Moving from Daylite to Pipedrive is a cross-platform migration that exits the Apple ecosystem entirely.
Read the full summary
Daylite exports its full object graph as a compressed archive of CSVs covering People, Companies, Opportunities, Projects, Appointments, Tasks, Notes, and Groups, but the download link expires after 14 days — a hard deadline we confirm at the start of every engagement. Pipedrive uses a cloud-native API with per-token rate limits and a tiered pricing model ($14-$99 per user per month), so migration cost scales with record volume and the number of Pipedrive seats the customer deploys. We resolve Daylite's freeform Opportunity stage names into Pipedrive's structured Pipeline stages during the mapping phase, preserve Company-to-Person linkage as Organization-to-Person lookups, and handle Projects either as Deals with custom fields or as Pipedrive's native Projects feature depending on scope. Workflows, automations, and Billings Pro billing records do not migrate.
People → Person
Daylite People records map directly to Pipedrive Persons.
How it maps
The mapping preserves name fields (first_name, last_name), email addresses (as a separate emails table with type and value columns), phone numbers, and address fields. Custom fields on People migrate to Pipedrive custom fields on Person, which we pre-create in the destination account during schema setup. The Person-Company linkage (a Daylite Person can be linked to one Company via a foreign key) maps to the Pipedrive Person's organization_id field, resolved at migration time after Organizations are created.
Companies → Organization
Daylite Company records map to Pipedrive Organizations with a 1:1 correspondence.
How it maps
Name, address, industry, website, and custom properties transfer directly. Organization is created before any Person import so that the organization_id lookup is satisfied when Persons are inserted. Daylite supports multiple addresses per Company; we import the primary address and flag the existence of additional addresses in a custom field for the customer's admin to reconcile.
Opportunities → Deal
Daylite Opportunities map to Pipedrive Deals.
How it maps
The key migration decision is the Pipeline and Stage assignment. Daylite Opportunity stage names are freeform text strings stored per record, not a managed list. We extract all unique stage name values from the Opportunities export, deduplicate them, and present a stage mapping worksheet where the customer explicitly maps each Daylite stage to a Pipedrive Pipeline Stage. Probability, value (formatted as decimal in Daylite), and close date transfer directly. The Person and Company foreign keys resolve to Pipedrive person_id and org_id via the Person and Organization imports.
Pipeline Stages → Pipeline Stage
Daylite's freeform stage names require explicit normalization.
How it maps
We extract the full set of unique stage strings from the Opportunities export, present them to the customer in a deduplicated table, and the customer assigns each to a Pipedrive Pipeline Stage (with a name and probability). Stages that are typos or variants of the same stage get consolidated at this point. Pipedrive Pipelines are pre-created in the destination account before Deals are imported, and the Stage ID from Pipedrive is stored as the mapping target for all Deal inserts.
Projects → Deal (with custom fields) or Project
Daylite Projects require a scope decision during discovery.
How it maps
Pipedrive's Projects feature (available on Advanced tier and above) supports tasks, milestones, and linked Deals, but is less structured than Daylite's Projects with budget tracking and Time&Budget plugin data. For migrations where Projects represent sales deliverables tied to Deals, we map Projects to Deals with a custom field project_id__c carrying the original Daylite Project reference. For migrations where Projects represent a distinct work-tracking domain, we use Pipedrive's native Projects object and link them to Deals via the project reference field. The customer chooses the strategy during scoping. Time&Budget plugin tables are mapped to custom fields on the Project or Deal depending on strategy.
Appointments → Activity (type = calendar)
Daylite Appointments map to Pipedrive Activities with type set to calendar.
How it maps
Each Appointment carries a UTC start and end timestamp, timezone, all-day flag, location, and category. The linked Person and Project IDs resolve to Pipedrive deal_id and person_id at migration time. Attendees from Daylite import as ActivityParticipants in Pipedrive. We preserve the chronological ordering of the appointment history by setting the Activity's due date to the original Daylite timestamp.
- PeoplePerson1:1
- CompaniesOrganization1:1
- OpportunitiesDeal1:1
- Pipeline StagesPipeline Stagetransformed
- ProjectsDeal or Project1:1
- AppointmentsActivity1:1
+ 5 more in the mapping below
How Daylite and Pipedrive 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 | Pipedrive |
|---|---|---|
| Platform ecosystem | Apple-only (macOS, iOS, iPadOS) with deep Contacts, Calendar, Mail, and Siri integration | Cloud-first web app with native mobile on iOS and Android; no platform lock-in |
| Custom field support | Custom fields on People, Companies, Opportunities, Projects, Tasks, and Appointments with definition in a separate metadata table | Custom fields available on Persons, Organizations, Deals, Activities, and Products at all paid tiers |
| Pipeline and stages | Opportunity stage names are freeform text stored per record, not a managed taxonomy; no central pipeline definition | Deals organized into Pipelines with defined Stages, each with a probability percentage and a whitelisted set of stage names |
| Project management | Full Projects object with Tasks, Appointments, budget tracking, and milestone support native to the CRM | Optional Projects feature on Advanced and above; simpler task-only model by default; full PM typically handled outside Pipedrive |
| Pricing model | Single-tier $20.83/user/month (annual) with no feature gating between plans | Five-tier model ($14-$99/user/month); Advanced ($29+) required for Projects, Custom Fields, and multiple Pipelines |
| Data export | Full database export to compressed CSV archive available from Account Settings; download link expires after 14 days | REST API and CSV import via Settings; Import2 third-party tool available for supported CRM sources |
| Third-party integrations | Limited plugin ecosystem via iOSXpert; no webhooks or native REST API for external integrations | Marketplace with 400+ apps, native Zapier and Make (Integromat) integrations, and a documented REST API with token-based rate limits |
What to watch for in a Daylite to Pipedrive migration
The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.
Daylite database export link expires after 14 days
When you trigger a full database export from Account Settings > My Info > Create Data Export, Daylite generates a compressed archive of CSVs and attachment files.
How we handle it
That download link is valid for 14 days from the moment it is generated. If the link has expired by the time we begin migration work, the export must be regenerated and a new download completed before any import activity starts. We confirm link validity at the start of every scoping call and request a fresh export if needed. This is the single most common Daylite-specific blocker we encounter in Apple-to-cloud migrations.
Daylite Opportunity stages are freeform text, not managed taxonomy
Opportunity stage names in Daylite are freeform strings entered per Opportunity record, not a centrally defined stage list with a probability table.
How we handle it
This means a Daylite database may contain 30 Opportunity records with 22 distinct stage string values (typos, abbreviations, and renamed stages all preserved in historical records). We deduplicate all unique stage strings and present them to the customer in a stage mapping worksheet. The customer explicitly assigns each unique Daylite stage name to a Pipedrive Pipeline Stage and its probability percentage. Migrations that skip this step import Deals with no stage assignment, leaving them in Pipedrive's default stage and breaking pipeline reporting.
Daylite Projects require an explicit scope decision in Pipedrive
Daylite's Projects object is richer than Pipedrive's native Projects feature: it includes budget tracking, milestone management, and integration with the Time&Budget iOSXpert plugin.
How we handle it
Pipedrive's Projects (Advanced tier and above) support tasks and milestones but lack budget fields and cost tracking. We present two strategies during scoping. Strategy one: map Daylite Projects to Pipedrive Deals with a project reference custom field, keeping all project data visible within the sales pipeline. Strategy two: use Pipedrive's native Projects object and link them to Deals, which is closer to Daylite's structure but requires Advanced tier and may not capture budget data. The customer chooses before we build the Pipedrive schema.
Billings Pro records do not exist in Daylite's export and cannot be migrated
Marketcircle discontinued self-serve Billings Pro and migrated customers to Billings Pro Cloud.
How we handle it
Billings Pro stores invoices and billing records in a separate application database that is not included in Daylite's database export. Customers with historical billing records to preserve must export them from Billings Pro independently before their Marketcircle account is transitioned. We flag the existence of Billings Pro during scoping and explicitly exclude it from the migration scope in our written engagement letter. Any billing history needed in Pipedrive must be sourced from Billings Pro export and handled as a separate data pass.
Pipedrive API rate limits require batched import with backoff
Pipedrive's API enforces token-based rate limits per account.
How we handle it
Heavy record imports (Deals, Activities, or large custom field updates) can exhaust the token budget or trigger 429 Too Many Requests responses, particularly when the migration runs alongside active user sessions and API-driven integrations. We pace imports with exponential backoff and schedule the heaviest passes (Activity history, bulk custom field updates) outside business hours to avoid competing for tokens with the customer's live integrations.
How the migration runs
Export validation and discovery
We begin every Daylite engagement by confirming the database export download link is still active.
What this step covers
If it has expired, we request a fresh export before proceeding. We then audit the exported table list for plugin signatures (iOSXpert Time&Budget, FinanceConnector) and flag any missing plugin tables for the customer to confirm whether that data should be included. We count records per object, identify custom field definitions, extract the full set of unique Opportunity stage strings, and document the Groups and Tags in use. We also ask whether Billings Pro is in use and confirm the customer has sourced any required billing export independently.
Schema mapping and stage normalization worksheet
We build a mapping worksheet that covers every Daylite object and its Pipedrive equivalent, including custom fields and stage name normalization.
What this step covers
The customer reviews and approves the stage mapping table (where each unique Daylite stage string is assigned to a Pipedrive Pipeline Stage and probability), the custom field mapping (Daylite field name to Pipedrive field name and type), and the project strategy (Deal-with-custom-fields or native Pipedrive Projects). This worksheet is the binding source of truth for the migration; we do not begin schema creation or data extraction until it is signed off.
Pipedrive account preparation
We create the Pipedrive custom fields, Pipelines, Stages, and any required Tags or Organization categories in the destination account before data import begins.
What this step covers
Pipedrive's API allows field creation via POST to the /fields endpoint, and pipeline creation via POST to /pipelines. We configure Pipelines with the customer's chosen stage names and probabilities. If the customer has selected the native Projects strategy, we provision the Projects feature on the Advanced tier. We do not modify existing Pipedrive account settings (user provisioning, email config, global defaults) unless explicitly scoped.
Data extraction and transformation
We extract data from Daylite's exported CSVs in dependency order: Organizations (from Companies), Persons (from People with org_id resolved), then Deals (with stage string normalized to the mapped Pipedrive Stage ID), then Activities (Appointments, Tasks, Notes), then Tags.
What this step covers
Custom field values are extracted from the per-record CSVs and written to the mapped Pipedrive custom field columns. Attachment filenames are cross-referenced against the attachment folder to confirm all files are present before upload. Billings Pro records are excluded and documented as out of scope.
Sandbox migration and reconciliation
We run a full migration into a Pipedrive Sandbox account (if available on the customer's plan) or a designated test workspace using production-like data volume.
What this step covers
The customer reconciles record counts for each object, spot-checks 20-30 records against the Daylite source (checking name accuracy, custom field values, relationship linkage, and date fields), and signs off the mapping and schema. Any corrections to field names, stage mappings, or custom field types happen at this stage. We do not proceed to production migration without explicit sign-off.
Production migration and cutover
We freeze Daylite writes during cutover (typically a 48-72 hour window), run a final delta extraction of any records modified since the initial export, and execute production migration in dependency order: Organizations, Persons (with org_id resolved), Deals, Activities, Tags, Custom Fields, Attachments.
What this step covers
Each phase emits a row-count reconciliation report. After all records are imported, we run a final validation pass checking for orphaned records (Persons with no Organization, Deals with no Person link) and resolve them in coordination with the customer. We deliver the automation and workflow inventory document for the customer's admin to rebuild in Pipedrive, and we provide a one-week hypercare window for reconciliation issues.
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 and scope complexity. Every quote is scoped with you; there is no self-serve pricing.
Get a quote for Daylite to Pipedrive →Why teams move from Daylite to Pipedrive
- Teams that expand beyond Apple devices hit a hard operational wall. Daylite has no web application, no Windows or Linux client, and no browser-based mobile option. Remote teams using Chromebooks, Android devices, or shared workstations cannot access Daylite at all. Pipedrive's cloud-native web app and native iOS and Android apps eliminate platform dependency entirely, which is the primary migration trigger cited by Daylite users on Reddit and G2 reviews when describing why they began evaluating alternatives.
- Daylite's integration ecosystem is narrow compared to Pipedrive's 400-plus Marketplace apps and native Zapier, Make (Integromat), and REST API connectivity. Teams that need to connect billing, marketing automation, accounting, or analytics tools find Daylite's third-party plugin surface insufficient. Pipedrive's documented API with per-token rate limits and OAuth 2.0 authentication enables reliable integrations that Daylite cannot match without custom development.
- Pipedrive's sales pipeline visualization, deal tracking, and activity management are purpose-built for sales teams. TrustRadius scores show Pipedrive at 8.6 for customer data management and 8.3 for opportunity management versus Daylite's 7.0 and 8.0 respectively, with Pipedrive's reporting (8.1) significantly outscoring Daylite (9.0 on CRM Reporting is a single-review outlier). Pipedrive's Lead Inbox, visual deal board, and activity feed are cited as more immediately actionable for sales workflows than Daylite's project-centric interface.
- Pipedrive's multi-tier pricing model allows teams to start at Essential ($14/user/month) and scale to Advanced ($29), Professional ($49), or Enterprise ($99) as the team grows. Daylite's single-tier model at $20.83/user is competitive at the low end but offers no clear upgrade path within the platform for teams that need advanced automation, custom objects, or enterprise security features. Teams evaluating Pipedrive as a destination often cite predictable per-seat pricing with visible feature gates as a preference over Daylite's all-in-one model.
- Daylite's native project management features (Projects, Tasks, Appointments, budget tracking) are tightly coupled to the Apple platform and cannot be accessed via web. Teams whose project work spans Apple and non-Apple contributors, or who need client-facing project portals accessible via browser, migrate to Pipedrive for its cloud availability while choosing a dedicated project management tool for complex work. Pipedrive's Advanced tier includes Projects as a lighter-weight alternative to Daylite's full PM suite.
Questions, answered
Daylite to Pipedrive migration questions
How long does a Daylite to Pipedrive migration take?
Straightforward migrations under 3,000 People and 1,500 Opportunities with no custom objects or plugin data land in two to four weeks. Migrations with Projects requiring a scope decision, large appointment histories (over 2,000 calendar events), multiple pipeline structures, or iOSXpert plugin tables extend to six to ten weeks. The Daylite export validation and mapping worksheet approval typically takes one to two weeks before any data moves, which is included in the timeline estimate.
Do Daylite Workflows, automations, and Project templates migrate to Pipedrive?
No. Daylite workflows and automations are stored in a different internal format that does not export as part of the database archive, and Pipedrive's automation model (Workflows and Automations in the Advanced and Professional tiers) is structurally different. We do not migrate automations as code. We deliver a written inventory of every Daylite workflow, automation, and Project template the customer documents during discovery, with a recommended Pipedrive Automation equivalent and trigger configuration for the customer's admin to rebuild. Forms, landing pages, and email templates in Daylite also do not migrate.
What happens to our Billings Pro billing records during migration?
Billings Pro stores invoices and billing records in a separate application database that is not included in Daylite's database export. We do not migrate Billings Pro data as part of the standard Daylite-to-Pipedrive migration scope. If the customer needs billing history preserved, they must export it from Billings Pro independently before their Marketcircle account is transitioned. We can import a Billings Pro CSV export into Pipedrive as a separate data pass with custom fields on the relevant Deal or Organization records, but this is scoped separately and requires the customer to produce the export file.
Do Daylite Notes and Appointments migrate to Pipedrive with their original dates?
Yes. Daylite Notes migrate as Pipedrive Activities of type note, preserving the original creation timestamp in the note body and setting the Activity due date to the original Daylite date for timeline ordering. Daylite Appointments migrate as Pipedrive Activities of type calendar with start and end timestamps, timezone, location, and all-day flag preserved. We resolve the linked Person and Project references to Pipedrive person_id and deal_id at migration time, so the activity history appears on the correct record in Pipedrive.
How do we handle Daylite's Groups and Tags in Pipedrive?
Daylite Groups are static segment memberships for People and Companies. Pipedrive does not have a native Groups object; segmentation is handled via Tags. We map each Daylite Group to a Pipedrive Tag and create TagAssignment records for every Person and Organization that was a member. Tags are pre-created in Pipedrive before the Person and Organization import so tag IDs are available during insert. The customer can alternatively choose to map Groups to Organization categories if they prefer a hierarchical structure over flat tags.
Can FlitStack AI migrate iOSXpert plugin data from Daylite to Pipedrive?
Yes, when the plugin tables are present in the Daylite database export. iOSXpert plugins (Time&Budget, FinanceConnector) write data into additional tables within Daylite's database. If those tables are present in the export (which requires the plugin to have been installed at the time of export), we migrate the plugin data to Pipedrive custom fields on the relevant record type. If the plugin was not installed when the export was generated, those tables are absent and the data cannot be recovered. We audit the export for plugin table signatures during scoping and confirm with the customer whether plugin data should be included before beginning migration.
Related migrations
Pipedrive implementation
Set up Pipedrive and migrate into it as one engagement.
See the service → ActiveCampaign to PipedriveMapping · history · rollbackHousecall Pro to PipedriveMapping · history · rollbackClose to PipedriveMapping · history · rollbackZoho CRM to PipedriveMapping · history · rollbackHoneyBook to PipedriveMapping · history · rollbackSalesforce to PipedriveMapping · history · rollback Daylite to SalesforceMapping · history · rollbackDaylite to Zoho CRMMapping · history · rollbackSources: official documentation
- Importing data into Pipedrive with spreadsheets — Knowledge Base
- Updating Pipedrive data with a spreadsheet — Knowledge Base
- 5 Simple CRM Data Migration Methods — Pipedrive Blog
- Option fields and label-vs-ID matching — Pipedrive Knowledge Base
- Import fields — Pipedrive Knowledge Base
- Importing: errors and skip files — Pipedrive Knowledge Base
- Custom field types — Pipedrive Knowledge Base
Get a quote
Moving from Daylite to Pipedrive?
Tell us roughly how many records and objects you have. We scope the mapping and the Pipedrive setup with you, then send a quote.
Get a quote