Migrate your Lofty data

The primary record type in Lofty. Standard fields (name, email, phone, source, status) map cleanly. Custom fields (up to 350 across 7 types on higher tiers) require per-type mapping. Starter tier caps at 10 custom fields per type — we flag any overflow records early.

Contact records mirror Lead fields but represent clients rather than prospects. Name, email, phone, address, and notes transfer 1:1. We deduplicate against existing Leads during import to prevent double records.

Transaction records capture deal status, associated contacts, property addresses, and monetary values. Standard fields map directly. Pipeline stage assignments transfer as-is and must be verified against destination stage names.

Property records store listing details, addresses, status, and associated images. Auto-update rules for property data do not export — we transfer the current snapshot and note which fields had dynamic updates so you can re-enable tracking post-migration.

Seven data types supported: Text, Date, Number, Percentage, Currency, Single-Select, Multi-Select. Starter tier is capped at 10 per type. We map each field by type and flag any that will be truncated or lost due to tier-based limits. Multi-select values are serialized as JSON arrays.

Tags are flat label strings attached to Leads and Contacts. We extract all tags per record and write them as a simple array. Tag counts are preserved; tag taxonomy (categories, colors) does not transfer.

Segments are saved lead groupings based on filter criteria. We export segment membership as a tag or custom property so the group relationships survive even if the segment definition itself does not copy.

Lofty organizes Leads into pipeline stages. Stage names and order transfer, but the transition rules or automation triggers attached to stages do not export. We document which stages exist and note any that may need manual recreation at the destination.

Webhook configurations require OAuth re-authentication and endpoint registration on the destination side. We document which webhooks are active and the events they subscribe to, but the subscriptions themselves cannot be transferred programmatically.

Attachments associated with Leads, Contacts, or Transactions transfer via URL reference where available. Files stored in Lofty's native file manager are downloaded and re-uploaded to destination storage. Large attachments may require extended migration windows.

User records (agent profiles, roles, team assignments) transfer with basic profile data. Team hierarchy and permission configurations vary by plan and often require manual verification post-import to ensure correct access levels.

Source attribution (where the lead originated — website, referral, IDX, etc.) is a standard Lead property. We preserve source strings and map them to equivalent fields in the destination CRM. Custom source types are treated as text values.