Migrate from BoldTrail to Twenty CRM

BoldTrail contacts and leads map to Twenty People. BoldTrail records without a primary company link are created as standalone People in Twenty. Email address is used for uniqueness deduplication and workspace member matching. Owner assignments resolve via email match to Twenty workspace members.

BoldTrail companies map directly to Twenty Companies, preserving the company name, domain, and industry values. Parent‑child hierarchies in BoldTrail are represented using Twenty's relation field for company‑to‑company links, ensuring nested structures are retained. When multiple BoldTrail contacts share the same company, they collapse into a single Company record in Twenty, with each Person linked via the companyId field.

BoldTrail listings (the real-estate deal object) map to Twenty Opportunities. Listing name becomes Opportunity name. Listing price becomes Opportunity amount. Listing stage maps to a custom Opportunity_Stage__c field with value-by-value translation. The property address migrates as a custom address field on the Opportunity.

BoldTrail listing pipeline stages (Active, Under Contract, Closed, etc.) have no native equivalent in Twenty's Opportunity model. We create a custom pick-list field (Opportunity_Stage__c) on Opportunities and map each BoldTrail stage value to the corresponding Twenty value. Stage-change timestamps are preserved as a custom audit field.

BoldTrail BackOffice transaction records (commission amounts, close dates, agent splits) do not map to a standard Twenty object. We create custom fields on the related Opportunity — Transaction_ID__c, Sale_Price__c, Close_Date__c, Commission_Amount__c — to preserve the closed-transaction history. If no linked Opportunity exists, the transaction is stored as a standalone custom object.

BoldTrail tags on contacts and listings migrate as a custom multi-select field (Tags__c) on Person and Opportunity. Multi-select ensures all tags are preserved. Tag frequency analysis is surfaced as a pre-migration report so your team can decide which tags to consolidate or drop.

BoldTrail notes on contacts and listings migrate as Twenty Notes linked to the corresponding Person or Opportunity record. BoldTrail call and email activity logs migrate as Twenty Tasks with Type set to 'Call' or 'Email'. Meeting notes migrate as Twenty Notes with the original timestamp preserved. Original owners are resolved by email match.

BoldTrail owner IDs are resolved by email match against Twenty workspace members. Any BoldTrail user whose email does not match a Twenty workspace member is flagged before migration. Your team either invites them to Twenty first or assigns their records to a fallback workspace member. No record lands without an assignee.

BoldTrail Smart Campaigns and drip sequences do not export — the automation logic lives in BoldTrail's proprietary engine. We create a Campaign_Reference__c custom object in Twenty to store the campaign name, status, and source system ID for each active campaign. Your team uses this as a rebuild reference for Twenty's workflow builder.

BoldTrail custom fields on contacts (beyond standard fields) map to custom fields on Twenty People. Field type is preserved: text stays text, number stays number, pick-list becomes select. Custom field metadata (label, type, required flag) is exported from BoldTrail's schema and created in Twenty before migration runs.

BoldTrail custom fields on listings map to custom fields on Twenty Opportunities. Examples include property type, MLS number, showing instructions, or offer terms. Each custom field is created in Twenty before the migration and mapped field-by-field with type-aware translation, including validation rules, default values, and required flags.

BoldTrail file attachments on contacts, companies, and listings are not accessible via API export. We re-upload them programmatically via Twenty's GraphQL API after the related Person or Opportunity records exist in Twenty. File size limits and inline image handling follow Twenty's storage constraints.