Migrate from Market Leader to Twenty CRM

Market Leader contacts and leads both map to Twenty's People object. We preserve the source object type in a custom field (Original_Object_Type__c) so you can filter reports by what the record was in Market Leader. Email, phone, name, and address fields map directly; owner resolution happens via email match against Twenty Workspace Members.

Market Leader companies map to Twenty's Companies object. Brokerage names, agent affiliations, and office associations migrate as text fields or custom fields depending on how Market Leader structures them. Multi-agent companies collapse to a single Company record with People linked via relationship fields.

Market Leader deals map to Twenty Opportunities with a value-mapping pass on the stage field. Real estate-specific fields (property_address, market_value, listing_type) migrate as Twenty custom text and currency fields on the Opportunity record. The deal owner maps to Twenty Opportunity assignee via email match.

Market Leader deal stages (New Lead, Showing Scheduled, Offer Made, Under Contract, Closed Won, Closed Lost) map value-by-value to Twenty Opportunity stage pick-list values. You choose which Twenty stages receive which Market Leader stages during the planning phase before migration runs. This mapping decision is documented in your field-mapping spreadsheet and reviewed with you before the migration commit.

Market Leader activities — calls, emails, showing notes, and general activity logs — map to Twenty Tasks. The original activity type is stored in a custom Task_Type__c field for reporting segmentation. Showing-specific fields (showing_date, feedback) become custom fields on the Task record. All activity timestamps map to Twenty's dueDate or completionDate fields depending on activity status.

Market Leader notes and deal comments migrate to Twenty Notes attached to the corresponding People, Company, or Opportunity record based on the record context in Market Leader. Rich-text formatting is preserved as plain text during migration. Timestamp and author information maps to Twenty's built-in note metadata fields, ensuring your team retains full context on who created each note and when.

Market Leader's lead_source and referral_source fields have no native equivalent in Twenty. We create a custom pick-list field (Lead_Source__c) on the People object before import, populate it from Market Leader's source values, and flag any unmapped values for your review.

Market Leader stores listing-specific data (mls_number, property_type, bedrooms, bathrooms, square_footage) as deal properties. These map to custom fields on Twenty's Opportunity record. Fields are created in Twenty's Data Model before migration; their types match the source data (text, number, currency).

Market Leader campaigns (lead groups for bulk outreach, market-wide campaigns) have no direct Twenty equivalent. Campaign membership data is preserved as custom fields on People (Campaign_Name__c, Campaign_Date__c) as a reference record. The campaign's automation logic must be rebuilt in Twenty's workflow builder.

Market Leader users and deal owners resolve against Twenty Workspace Members by email match. Unmatched owners are flagged before migration — your team either invites them to Twenty first or assigns their records to a fallback member. No record lands without a Twenty assignee.