Migrate from Zavvie Power Buyer to Twenty CRM

Zavvie's client records (borrowers represented by real estate agents) map directly to Twenty's People object. Each borrower becomes a People record with name, email, phone, and address fields carried over. Agent-linked borrowers without a direct email are flagged for manual enrichment before import.

Real estate agents using Zavvie map to Twenty People records. Agent names, emails, and license numbers migrate as custom text fields on the People record. If agents appear as both a contact and a company stakeholder, they are stored as People records with their brokerage link preserved as a Companies relation.

Lender partners and mortgage companies from Zavvie map to Twenty's Companies object. Company name, domain, NMLS ID (stored as a custom field), and address details are preserved. Parent-brokerage relationships map to Twenty's Company.domain link for hierarchy resolution. Additionally, any referral codes or partnership tiers associated with lenders are captured as custom text fields for reference.

The primary brokerage account in Zavvie becomes a Company record in Twenty. All nested agents, partner lenders, and property listings associated with that brokerage link to this top-level Company via the Companies relation field on People and Opportunities. This top-level Company also captures the brokerage’s primary contact information and any administrative notes.

Zavvie's property-level offer records—containing offer amount, property address, offer type (cash, buy-before-you-sell), and status—map to Twenty Opportunities. The property address is stored as a custom text field on the Opportunity. Offer amount maps to Opportunity.amount, and the offer type becomes a custom select field (offer_type__c).

Zavvie's offer lifecycle stages (Offer Submitted, Offer Accepted, Due Diligence, Closing Scheduled, Closed Won/Lost) map value-by-value to Twenty Opportunity Stage names. Each stage carries a probability and forecast category re-applied from Twenty's stage configuration after migration. If your team uses custom stage names or additional sub-stages, these are mapped to the nearest Twenty stage equivalents during the import.

Zavvie's transaction records combine deal data and closing details that map to a single Opportunity record in Twenty. The closing date, final sale price, and commission data become fields on the Opportunity. If Zavvie separates deal and closing into two records, they are merged into one Opportunity on the destination side.

Zavvie supports custom attributes per offer—cash_ready_status, bridge_loan_terms, earnest_money_amount—that have no native Twenty equivalent. These are migrated as custom fields on the Opportunity object. Custom fields must be pre-created in Twenty's Settings → Data Model before the migration run. These custom fields also preserve any historical values so reporting can reflect the full offer history in Twenty.

Offer documents, purchase agreements, and loan disclosures attached to records in Zavvie are downloaded and re-uploaded as Notes in Twenty. Each document is attached to the corresponding Opportunity or People record. File size limits are respected per Twenty's upload constraints.

Zavvie's partnership relationships between brokerages and lenders use a many-to-many model. In Twenty, these map to a custom junction object (BrokeragePartner__c) linking two Company records. The junction stores partnership start date, status, and any referral fee terms as custom fields.

Agent follow-up tasks, document collection reminders, and offer-status updates from Zavvie migrate as Task records in Twenty. Each Task links to the related People or Opportunity record. Original due dates and assignees are preserved during migration. If a task lacks a valid assignee in Twenty, it is flagged for manual assignment to a workspace member.