Migrate from BoldTrail to Nutshell

BoldTrail contacts map directly to Nutshell People records. The primary company association migrates as the Person's linked Company in Nutshell's Company lookup field. The Company record must be created first for the lookup reference to resolve correctly during migration. Original BoldTrail create timestamps are preserved in a custom datetime field since Nutshell's system-created date reflects migration execution time rather than the original record creation date.

BoldTrail company records map 1:1 to Nutshell Companies without any structural transformation. The company name, website, address, phone, and industry fields migrate directly using standard field-to-field mapping. Parent-child company hierarchies in BoldTrail map to Nutshell's parent company lookup field when that relationship is configured in the source system.

BoldTrail contacts with lead_status values of 'New', 'Active', or 'Contacted' route to Nutshell Leads rather than People records during migration. This split preserves the distinction between unqualified prospects and established client relationships in the destination data model, maintaining data integrity across the CRM transition.

BoldTrail deals map to Nutshell Deals. Pipeline stage names are mapped value-by-value to Nutshell's stage pick-list. Deal amount, close date, owner, and associated contacts migrate with the deal record. BoldTrail's transaction-specific fields (listing ID, property address) are stored as custom fields since Nutshell Deals lack a native listing link.

BoldTrail permits a contact to belong to multiple companies simultaneously. Nutshell assigns one primary Company per Person. FlitStack AI migrates the most recently modified company association as the primary link and preserves the others as a custom multi-value field for reference.

BoldTrail call logs, emails, meetings, and notes migrate as Nutshell Activities linked to the respective Person or Deal record using the original record's unique identifier. Original timestamps and owner assignments are preserved throughout the migration process. Rich-text formatting in BoldTrail notes converts to Nutshell's note format to maintain content fidelity and readability.

BoldTrail custom properties on contacts create matching custom fields in Nutshell's Person object. Field types map appropriately: text to text, number to number, pick-list to choice fields. Nutshell's field name character limits apply to migrated field labels, so long custom property names may be truncated to fit within Nutshell's 50-character field name limit.

BoldTrail company-level custom properties migrate to Nutshell Company custom fields following the same type-aware mapping as person fields. Custom properties referencing external IDs or linked records preserve their values as text fields in Nutshell to maintain data accessibility. Nutshell's character limits for field labels and option values apply during migration.

BoldTrail owner and agent records resolve to Nutshell Users by email address match. If a BoldTrail owner has no matching Nutshell user, their records are assigned to a designated fallback user and flagged for admin review before the full migration runs.

BoldTrail Smart Campaigns, drip sequences, and workflow automations do not migrate to Nutshell since the two platforms use fundamentally different automation architectures. BoldTrail's event-based triggers have no direct Nutshell equivalent, so these must be rebuilt in Nutshell using Personal Email Sequences and task automations. FlitStack AI exports a human-readable inventory of BoldTrail Smart Campaigns as a rebuild reference document for Nutshell admins.

BoldTrail listings and property records have no direct Nutshell equivalent. If listings are tied to deals, the listing ID and address migrate as custom fields on the Deal record. Standalone property records may require a separate migration workflow or external listing tool.

BoldTrail's IDX websites, lead dropbox configurations, and website lead sources are platform-specific infrastructure tightly coupled to BoldTrail's real estate data model. These configurations do not transfer to Nutshell because they depend on BoldTrail-specific integrations and MLS connectivity. Lead capture forms and website integrations must be reconfigured to point to Nutshell after migration is complete.