Migrate your Levitate data

Contacts are the primary object in Levitate. Every contact has a name, email, phone, company, and a rich set of custom properties including key dates (birthday, renewal date, policy expiration). We export all standard fields plus all active custom properties. Import maps cleanly to any CRM's contact schema using our field-matching engine.

Tags are the primary segmentation mechanism in Levitate. They drive automation triggers, conditional branching, and contact filtering. We preserve the full tag taxonomy during migration and can map tag sets to equivalent lists, segments, or static groups in the destination CRM.

Automations in Levitate are server-side workflow sequences (email steps, delays, conditional branches, tag actions). The automation logic itself is not exported as portable JSON — only the enrollment state of each contact (which automation they are in, which step they reached). We migrate the contact's automation history and flag that destination automations must be rebuilt using equivalent triggers.

Key Dates are a Levitate-specific custom field type storing birthday, anniversary, policy renewal, and other personal dates used to trigger automations. These are stored as custom date fields on the contact record. We migrate them as-is; destination CRMs may require a custom field to be created first.

Campaigns track a group of emails sent to a segment. Engagement data (opens, clicks, replies) is stored per-campaign. We export campaign metadata and aggregate engagement stats. Individual email performance data requires separate export from Levitate's reporting views.

Social media posts are stored as template references with scheduling metadata rather than as structured records. There is no documented export endpoint for social content. We do not migrate social media post history; instead we document the post count and scheduling cadence for re-creation at the destination.

Handwritten card orders are managed through a third-party fulfillment integration and do not store recipient addresses as standalone contact data. Card order history is not accessible via export. We exclude handwritten card records from migration scope.

Text message history is stored per contact but Levitate's export capability for SMS logs is limited to the contact's recent message thread view. We migrate available SMS logs as activity entries; long-threading and consent records should be reviewed separately.

Attachments referenced in automations or campaigns are stored as URLs or references to Levitate's content library. We export the attachment reference URLs and flag any attachments that must be re-uploaded to the destination platform's content library.

Levitate user accounts (owner, admin, member roles) can be listed but role definitions and permission scopes are not fully exportable. We map the primary owner and active user list and flag that role parity must be manually configured at the destination.

Engagement events are tracked per contact per campaign but the raw event log is not bulk-exported via API. We capture the last engagement date and aggregate open/click counts as contact properties, then note that full engagement history requires a separate reporting export.

Industry-specific integrations sync contact and account data with practice management and agency management systems. Integration configuration (OAuth tokens, sync direction, field mappings) is stored server-side and is not portable. We document the active integrations and their sync scope so they can be re-connected at the destination.