Migrate from BoldTrail BackOffice to Twenty CRM

BoldTrail contacts map 1:1 to Twenty People records. The email address is used as the unique identifier for import and for resolving duplicate records. Contacts without an email are assigned a generated placeholder so they land in Twenty and can be manually linked.

BoldTrail stores company names on the contact record. FlitStack extracts unique company names, creates a Company record in Twenty, and back-links the People record via the companyId relation. Company domains, where present, populate the Companies website field.

BoldTrail also supports standalone company records. These map to Twenty Companies directly. If a standalone company shares a name with a company extracted from a contact, the records are merged into a single Twenty Company.

BoldTrail transactions are the core data unit in BackOffice — each represents a real estate deal with a property address, sale price, stage, and agent assignment. Each transaction maps to one Twenty Opportunity. BoldTrail's transaction ID is stored as Source_System_ID__c on the Opportunity for traceability.

BoldTrail's real-estate-specific stages (Under Contract, Inspection, Closing) have no direct Twenty equivalent. We map them to Twenty's generic Opportunity stage values: 'Proposal' for Under Contract, 'Negotiation' for Inspection, and 'Closed Won' for Closing, preserving the original BoldTrail stage name in a custom field for reporting continuity.

Twenty Opportunities do not have a native address field. The transaction property address is stored as a custom text field on the Opportunity so agents can identify which property the deal relates to. If your brokerage uses multiple address components (street, city, state, zip), these are concatenated into a single formatted string.

BoldTrail calculates total commission per transaction based on the commission plan and agent split. This dollar amount migrates to a custom currency field on the Twenty Opportunity so reporting can still reference commission values without recalculating them.

BoldTrail agents map to Twenty WorkspaceMembers by email. FlitStack resolves BoldTrail agent IDs on transactions to the corresponding Twenty user. If an agent does not yet have a Twenty account, their records are assigned to a fallback owner and flagged for admin review before go-live.

BoldTrail commission plans define the rules (percentage, cap, tier) that govern how agents are paid per transaction. Twenty has no commission calculation engine. We preserve each plan's configuration as a record in a CommissionPlan custom object, linking it to the relevant agents so admins can reference the source plan when rebuilding commission logic manually.

BoldTrail commission splits define what percentage of the commission each agent (or team) receives per transaction. Each split migrates as a record in a CommissionSplit custom object with fields for agent, transaction reference, split percentage, and calculated payout amount. The Opportunity record links to its related split records.

BoldTrail generates invoices for agent payouts based on closed transactions. These migrate as records in an AgentInvoice custom object with fields for invoice number, agent, amount, date, and payout status. Twenty has no accounting module — this data serves as a historical record for audit purposes.

BoldTrail stores transaction documents (contracts, disclosures, e-signatures). Files attached to a transaction are downloaded and re-uploaded to Twenty's Files system, linked to the corresponding Opportunity record. File size limits in Twenty's storage tier apply.

BoldTrail custom fields per contact, company, or transaction map to custom fields on the corresponding Twenty object. Custom fields must be created in Twenty's Settings → Data Model before the migration runs — FlitStack delivers a field-creation manifest as part of the setup plan.

BoldTrail Smart Campaigns and playbooks are automation logic with trigger conditions, action sequences, and enrollment rules. Twenty's workflow builder does not import these. FlitStack exports each Smart Campaign's configuration as a JSON file so your admin can reference it when building equivalent automations in Twenty.