Migrate from BoldTrail BackOffice to Nutshell

BoldTrail contacts map directly to Nutshell People. Nutshell People stores name, email, phone, address, title, and social links. BoldTrail CRM-synced contact fields (first name, last name, email, phone) land as direct field mappings. Nutshell does not have a separate Lead object by default for every contact — contacts that represent unqualified prospects can be flagged with a custom lead_status field.

BoldTrail companies map to Nutshell Companies 1:1. BoldTrail stores company name, domain, industry, employee count, and address. These map to Nutshell Company name, website, industry, number of employees, and address fields. BoldTrail company associations on contacts (CRM sync) translate to Nutshell's party association model.

BoldTrail transactions are the core deal record in the source system — they include property address, transaction status, close date, commission split, agent split, and document checklist. These map to Nutshell Deals inside a single pipeline. Pipeline stage values map to Nutshell deal status values through a value-mapping table. The transaction ID is preserved as source_transaction_id on the Nutshell Deal for traceability.

BoldTrail agents are separate records used for commission routing and agent management. Nutshell has no native Agent object — agents are represented as Nutshell People records with custom fields (agent_id, license_number, team_name) and are assigned as Deal owners. We match BoldTrail agent emails to Nutshell users; unmatched agents are flagged for manual assignment before the full run.

BoldTrail tracks per-agent commission splits inside each transaction — each split includes agent name, split percentage, and payout status. Nutshell has no native commission split object. We store each split as a custom field on the Nutshell Deal (e.g., split_agent_1, split_pct_1, split_agent_2, split_pct_2) for reference. Commission plan logic itself does not migrate — it must be rebuilt in Nutshell or through an external commission tool.

BoldTrail file attachments on transactions (contracts, disclosures, e-signed forms) are downloaded and re-uploaded to Nutshell Files attached to the corresponding Deal record. File names and original upload timestamps are preserved in the Nutshell file metadata. Large files or batch attachments may require chunked upload handling per Nutshell's file size limits.

BoldTrail transaction checklists map to Nutshell Tasks attached to the corresponding Deal. Each checklist item becomes a Task with a subject and due date. Completion status and assignee are preserved where the source data includes them. BoldTrail's automated task triggers (e-sign sent, disclosure received) do not migrate — they require rebuild as Nutshell workflow rules.

BoldTrail CRM-synced activity history (logged calls, notes, email threads linked to contacts) migrates to Nutshell Activities attached to the corresponding Person or Deal record. Original activity timestamps and owners are preserved. BoldTrail's automated engagement tracking (opens, clicks) does not exist in Nutshell — those metrics are not transferred.

BoldTrail allows custom fields on transactions (e.g., referral_source, property_type, mls_listing_id). Nutshell supports custom fields on Deals. We create equivalent custom fields in Nutshell and map values directly. Field types are mapped: text → text, number → number, date → date. Pick-list values in BoldTrail require value-by-value mapping to Nutshell pick-list options.

BoldTrail's QuickBooks integration settings and MLS sync configurations have no Nutshell equivalent. These must be rebuilt or re-configured manually after migration. We document the source integration settings during discovery so your team has a rebuild checklist ready before go-live. This documentation includes API endpoints, authentication methods, and field mapping rules.

BoldTrail custom reports and dashboard configurations do not transfer to Nutshell. The underlying data (deals, activities, agent performance) migrates fully, but the report layouts, scheduled exports, and chart configurations require rebuild using Nutshell's report builder. We provide a data dictionary so your team can reconstruct reports accurately.

BoldTrail agents and users are matched to Nutshell users by email address. Active BoldTrail users who have a corresponding Nutshell login receive ownership of their migrated records. BoldTrail users without a Nutshell account are flagged before migration — your team either creates their Nutshell account first or assigns a fallback owner for their records.