Migrate from Homesnap Pro to Twenty CRM

Homesnap Pro agent profiles (name, email, phone, license number, brokerage) map to Twenty People records. Agent-specific fields (license number, MLS ID) migrate as custom text fields on the People record. The Agent_Type__c custom field is set to 'Agent' to distinguish from generic contacts. Agent email is used for owner resolution if the agent also has a Twenty user account.

Brokerage records from Homesnap Pro map to Twenty Companies. Company name, address, website, and industry fields migrate directly. Team size and company type (brokerage, franchise, independent) are preserved as custom select fields. The primary agent on the brokerage record links via a relation field to the People record.

Homesnap Pro listings become Twenty Opportunities. Listing status (Available, Under Contract, Sold, etc.) maps to a custom select field Listing_Status__c on the Opportunity. The listing address, MLS number, and property type migrate as custom text fields on the Opportunity record. The Opportunity is linked to the property People record (agent) via the standard assignee field and to the brokerage Company record.

Homesnap Pro property records map to a custom Property object in Twenty. The object must be created in Settings → Data Model before migration with fields for address, city, state, zip, MLS number, list price, property type (select), bedrooms, bathrooms, square footage, and listing status. Property records are the 'one' side of the one-to-many relationship with Opportunities and Tasks.

Homesnap Pro showing records map to Twenty Tasks with a custom field Showing_Type__c set to 'Showing'. The task is linked to the relevant Property custom object (via relation) and to the agent People record. Original showing date and time are preserved as the Task due date and a custom datetime field. Showing outcome (attended, cancelled, no-show) is stored as a custom select on the Task.

Buyer and seller client contacts from Homesnap Pro map to Twenty People records. Client type (buyer, seller, both) is stored as a custom select field Client_Type__c. Clients with a linked company map to that Company record. Clients without a company are standalone People records with no CompanyId relation.

Homesnap Pro listing stages (Available, Under Contract, Pending, Closed, Withdrawn, Expired) are mapped to a custom Opportunity field Listing_Status__c via a value-by-value lookup. Stage probabilities are noted but not applied automatically in Twenty's Opportunities since real estate deal probabilities vary by market.

Homesnap Pro notes and activity log entries migrate to Twenty Notes. Each Note is linked to the relevant record (People, Company, or Opportunity) via the standard relation field. Original creation timestamp is preserved as a custom field since Twenty's CreatedAt is set at import time. Note body text is preserved verbatim.

Homesnap Pro agent production metrics (units sold, volume, commission) do not map to any standard Twenty object. We create a custom AgentPerformance object with fields for period (month/year), units sold, sales volume, commission earned, and a relation to the agent People record. This preserves historical context for reporting continuity post-migration.

Homesnap Pro listing alerts, showing reminders, and task triggers do not have a migration path to Twenty CRM. Twenty's workflow engine uses its own trigger-action model that is not API-accessible for import. We export workflow definitions as a reference document so your admin can manually rebuild them in Twenty's Settings → Workflows.