Migrate from BoldTrail BackOffice to Zoho CRM

BoldTrail contacts split by transactional status: contacts linked to closed transactions are routed to Zoho Contacts, while those with open or pending transactions become Zoho Leads. Agent contacts receive a custom Agent_ID__c field that preserves the original BoldTrail owner identifier, enabling smooth post‑migration reporting and owner tracking.

BoldTrail company records map directly to Zoho Accounts. Company name, address, phone, and website transfer as standard Account fields, preserving the original data for immediate use. Parent‑child relationships in BoldTrail are reflected in Zoho through the Parent Account lookup, maintaining organizational hierarchies after migration.

BoldTrail transactions map to Zoho Deals — the primary translation object for this migration. Property address becomes the Deal name; transaction status maps to a custom pick-list field (Transaction_Status__c) matching BoldTrail's status values. Commission amount, split percentages, and agent IDs migrate as custom fields on the Deal.

BoldTrail transaction stages (such as Active, Under Contract, Closed, Cancelled) are mapped to a Zoho custom pick‑list field (Transaction_Status__c) on the Deal module. These stage values must be created in Zoho before the migration run to prevent import errors caused by unrecognized pick‑list entries, ensuring a smooth data load.

BoldTrail commission records (including split amounts, agent percentages, and broker percentages) lack a native Zoho CRM equivalent. FlitStack AI extracts the commission data for each transaction and writes it into custom fields on the associated Deal, specifically Commission_Amount__c, Agent_Split__c, and Broker_Split__c, thereby preserving the full commission logic within Zoho.

BoldTrail agents are matched to Zoho Users by email address. Unmatched agents receive a custom Agent_ID__c field on their Deals for traceability. BoldTrail agent onboarding and performance data does not map to a Zoho object and is preserved as a reference file for manual record-keeping.

BoldTrail eSignature documents attached to transactions are exported and re-uploaded as Zoho Attachments linked to the corresponding Deal record. Documents are re-hosted in Zoho's file storage; the original BoldTrail document URL is preserved in a custom field (Original_Doc_URL__c) for audit purposes.

BoldTrail property details—such as address, MLS number, and listing status—that do not map to standard Zoho Deal fields are accommodated as a Zoho custom module or as custom fields on the Deal object. Fields like Property_Address__c, MLS_Number__c, and Listing_Status__c are pre‑created in Zoho before the migration run to ensure accurate data placement and avoid import failures.

BoldTrail notes and activity entries attached to transactions are migrated as Zoho Notes on the corresponding Deal record. Transaction‑level comments, status‑change logs, and other annotations retain the original BoldTrail author name and timestamp, providing a complete audit trail within Zoho after the migration.

BoldTrail custom reports and analytics dashboards are not transferred during migration. However, the underlying transaction, contact, and commission data that drives those reports is loaded into Zoho Deals and associated custom fields, enabling Zoho’s built‑in reporting and analytics tools to rebuild comparable dashboards after the migration is complete.