Migrate from Thunderbolt Pipeline to Nutshell

Thunderbolt Pipeline contacts map 1:1 to Nutshell People. Fields including name, email, phone, job title, and address migrate as standard Person fields. Owner resolution matches by email against Nutshell user list; unresolved owners are flagged before the full migration runs.

Thunderbolt Pipeline companies map to Nutshell Companies. Company name, website, industry, address, and phone fields map directly. Parent-company hierarchies in Thunderbolt Pipeline flatten to a single Nutshell Company record with the parent name stored in a custom text field if the hierarchy is non-trivial.

Thunderbolt Pipeline projects do not have a native Nutshell equivalent. We map each project to a Nutshell Deal, preserving the project name as the Deal name and the project start date and estimated completion date as custom date fields on the Deal. The Deal stage maps from the project's current pipeline stage in Thunderbolt Pipeline.

Bids in Thunderbolt Pipeline are associated with a project and carry bid_amount, bid_status, and bid_submitted_date. Bid data merges into the Nutshell Deal representing that project — bid_amount maps to a custom number field, bid_status maps to a custom pick-list, and bid_submitted_date stores as a custom date field. A project with multiple bids generates one Deal with each bid's details stored as a separate linked custom record.

Thunderbolt Pipeline tasks map to Nutshell Tasks. Subject, due date, assigned user (resolved by email), and completion status transfer directly. Task descriptions map to Nutshell Task notes. Open tasks at migration time are created in Nutshell; completed tasks with relevant historical context are imported as completed records.

Thunderbolt Pipeline notes attached to a project, bid, or contact migrate to Nutshell Notes linked to the corresponding Person, Company, or Deal. Note body text transfers as-is. Timestamps and author information are preserved for audit continuity. All note metadata including creation dates and owning user references are maintained to ensure historical context is not lost during the migration process.

File attachments on Thunderbolt Pipeline projects, bids, or contacts are downloaded and re-uploaded to the corresponding Nutshell record. File size limits follow Nutshell's attachment constraints. Files with unsupported characters in filenames are renamed during migration to comply with Nutshell's storage naming rules.

Thunderbolt Pipeline project stages (Bid Invited, Bid Submitted, Bid Won, Bid Lost, Project Active) map to Nutshell pipeline stages via value-by-value lookup. We match each Thunderbolt Pipeline stage label to the closest Nutshell stage name and flag any stages with no direct equivalent for manual assignment before the migration run.

Thunderbolt Pipeline users and project owners are resolved by email against Nutshell's user list. Active Nutshell users matching by email receive their assigned records automatically. Unmatched owners are flagged before migration commits so your team either invites them to Nutshell first or assigns records to a fallback owner.

Thunderbolt Pipeline's construction-specific fields have no Nutshell native equivalent and require custom field creation before migration. We create custom fields on the Nutshell Deal object — contract_type (pick-list), project_phase (pick-list), bid_status (pick-list), estimated_value (number), and project_address (text) — and map each source value directly. Custom field limits scale with your Nutshell plan.

Thunderbolt Pipeline's workforce planning data (labor forecasts, crew assignments, resource schedules) has no equivalent in Nutshell CRM. This data does not migrate. We export the workforce planning records as a CSV reference file you can hand to your operations or HR tool of choice for manual re-entry.

Thunderbolt Pipeline workflow rules and bid-status automation triggers do not have a Nutshell equivalent. Nutshell's automation features (email sequences, task triggers, stage-change actions) must be rebuilt in Nutshell Pro or Business. We export a structured JSON representation of your Thunderbolt Pipeline workflow definitions as a rebuild reference for your Nutshell admin.