Migrate from Lofty to Twenty CRM

Lofty contacts and leads map directly to Twenty People as the primary CRM record type. The contact's primary email address serves as the unique import key to prevent duplicate creation. Since Twenty's native CreatedAt timestamp is set at the time of import rather than preserving the original date, the original Lofty create date is stored in a custom datetime field on each record for historical accuracy and reporting purposes.

Lofty companies map 1:1 to Twenty Companies without any transformation required. The company name field serves as the unique import key to ensure each company is created once. Standard fields including employee count, annual revenue, and industry classification map directly to their corresponding Twenty Company fields. For companies with multiple addresses in Lofty, only the primary address is imported to maintain clean data.

Lofty deals are migrated as Twenty Opportunities, representing the deal lifecycle in Twenty's data model. The deal name maps to Opportunity name, amount transfers directly, and close date becomes the expected close date. Pipeline stage is translated through value-mapping to the OpportunityStatus pick-list field, ensuring deal progress is reflected accurately.

Lofty's pipeline stages including Prospect, Active, Under Contract, Inspection, Appraisal, and Closed reflect real estate transaction milestones that do not exist in Twenty's default OpportunityStatus configuration. We create a custom pick-list in Twenty's Data Model with option values matching each Lofty stage name exactly. Each deal's pipeline_stage value is then mapped by name to the corresponding Twenty OpportunityStatus value, preserving the full sales cycle representation in the new CRM.

Every Lofty pipeline stage receives a direct mapping to a corresponding Twenty OpportunityStatus option value during migration. Probability weights associated with each stage in Lofty are preserved as a custom number field on the Twenty Opportunity record. Stage-entered timestamps recording when a deal moved into each pipeline stage are saved as custom datetime fields to maintain historical reporting continuity in Twenty's analytics.

Lofty notes are transferred to Twenty Notes using the standard relation model that links each note to its parent record. Notes attached to People, Companies, or Opportunities in Lofty are associated with the corresponding Twenty object through the standard note relationship mechanism. Rich text formatting including bold, italic, lists, and embedded links is preserved during migration where Lofty's note format supports these elements.

Lofty's call and email activity logs are transformed into Twenty Tasks, with the activity type determining the Task type field value. Call activities receive type='Call' and email activities receive type='Email', while the subject line from each activity becomes the Task title. Original activity timestamps are preserved as the task due date or completion date, and assigned owner information is transferred to maintain accountability records.

Lofty meetings are migrated as Twenty Tasks with Task type set to 'Meeting'. Start and end times are preserved in datetime fields, location transfers as text, and attendees are stored as custom fields. Each meeting task links to its associated People or Opportunity record using Twenty's standard relationship model.

Lofty custom fields including lead_type, lead_source, and mortgage_info are created as custom fields in Twenty's Data Model under the matching object. Select and multi-select fields require option-value mapping where each Lofty option matches a Twenty option. Custom fields are positioned in the correct column view before migration.

Lofty owner and agent IDs are resolved to Twenty workspace members by matching email addresses. Each Lofty owner is compared against Twenty's user list using email as the matching key. Owners without a corresponding Twenty account are flagged in a pre-migration report — your team either invites them to Twenty first or assigns their records to a fallback member.

Lofty file attachments including documents and images are downloaded and re-uploaded to Twenty's file storage system. File size limits imposed by Twenty are respected during re-upload, and inline images in notes are extracted as separate attachments. The parent record linking each file to its associated People, Company, or Opportunity is preserved.

Lofty's bundled texting flows and AI virtual assistant are real-estate-specific automation tools with no direct equivalent in Twenty CRM. The 10DLC-compliant texting platform, AI lead generation, and automated response sequences are tied to Lofty's contact and property model. These constructs cannot be exported and must be rebuilt using Twenty's workflow builder or a third-party texting integration such as Twilio post-migration.