Migrate from Levitate to Pipedrive

Levitate Contact records map to Pipedrive Person. The Levitate contact name, email, phone, company, and address fields map directly to standard Pipedrive Person fields. Custom properties from Levitate migrate as custom fields on Person. We extract via UI-based CSV export (the only available path since Levitate has no bulk API) and import via Pipedrive's CSV wizard or REST API v2. Email serves as the dedupe key; contacts with duplicate emails are flagged for customer review before final import.

If Levitate contacts have an associated company name, we extract that as a separate Organization record in Pipedrive. Levitate's contact-centric model means company data lives as a property on the Contact; we split it into a normalized Organization record and link via the Person-Organization lookup during import. This preserves the ability to run organization-level reports and aggregate contacts by company in Pipedrive.

Levitate Tags are the primary segmentation mechanism and drive automation triggers. We preserve the full tag taxonomy during migration by creating a custom field in Pipedrive to hold tag values. If a contact has multiple tags, we use a multi-select picklist or comma-delimited text field depending on the Pipedrive plan. Tag counts and tag-based segment membership are preserved so downstream Pipedrive filters and manual segmentation can resume without re-tagging.

Levitate Key Dates (birthday, renewal date, policy expiration, custom milestones) are a Levitate-specific date field type that drives date-triggered automations. These must be created as custom date fields in Pipedrive before any contact data is imported. We flag every Key Date field during discovery, confirm the list with the customer, create the corresponding custom date fields in Pipedrive (Settings > Data Management > Custom fields), and map the Levitate values to the new Pipedrive fields during import. Automations that were triggered by Key Dates must be rebuilt in Pipedrive Workflow Automation using different triggers (e.g., scheduled workflow based on date fields rather than Levitate's native date event).

Levitate Campaigns track email sends to a segment with engagement stats (opens, clicks, replies) aggregated per campaign. Pipedrive does not have a native Campaign object in the same sense. We migrate campaign metadata and aggregate engagement stats as Activity records attached to the relevant Person or Organization, with the campaign name stored as a label. Individual email performance data is not preserved as a discrete object; we deliver a campaign summary document with open/click counts and dates.

Levitate automations are server-side workflow sequences with email steps, delays, conditional branches, and tag actions. The automation logic itself is not exported as portable JSON or via any documented API. Only enrollment state (which contacts are enrolled in which automation) is extractable. We do not migrate automations as code. We deliver a written inventory of every active Levitate automation documenting its trigger, conditions, sequence steps, and tag actions, plus recommended Pipedrive Workflow Automation equivalents. The customer's admin rebuilds each automation in Pipedrive's visual workflow builder using the inventory as a spec.

Levitate engagement history (email logs, call records, meeting notes, tasks) migrates to Pipedrive Activities. Emails and calls become Task records with subtype; meetings become Event records with start/end times; notes become Note records linked to the Person or Organization. We preserve the original timestamp and user attribution from Levitate where available. Pipedrive's API rate limits and per-user export restrictions mean we batch activity imports and run them outside business hours when possible.

Levitate user accounts (owner, admin, member roles) are listed for mapping purposes. We match Levitate owner email to the customer's provisioned Pipedrive users. Any Levitate owner without a matching Pipedrive user goes to a reconciliation queue for the customer to provision before record import proceeds. Role and permission definitions are not exportable from Levitate and must be reconfigured in Pipedrive manually.

Levitate's industry-specific integrations with practice management systems (Clio for legal, Vertafore/AMS360 for insurance) store OAuth tokens and sync configuration server-side with no export capability. We document the active integrations and their current field mappings as a reference for reconfiguration in Pipedrive. Pipedrive's native integrations and Zapier-based alternatives serve as replacement paths; the customer must re-authorize OAuth connections post-migration.

Text message history in Levitate is stored per contact in a thread view but Levitate's export capability for SMS logs is limited. We migrate available SMS logs as Note records attached to the Person record, preserving the message content and timestamp where extractable. Long message threads may be truncated due to UI export limitations. SMS consent records migrate to a custom field for compliance documentation.