Migrate from Thunderbolt Pipeline to Twenty CRM

Thunderbolt Pipeline stores individual contact records with name, email, phone, and job title. These map directly to Twenty CRM's People object. The People record must reference a Companies record via companyId once the company import is complete. Owner assignment resolves by email match against Twenty Workspace Members.

Thunderbolt Pipeline's company records store business name, domain, address, industry classification, and employee count. These map to Twenty CRM's Companies object using the same field names where conventions align. Parent-company hierarchies in Thunderbolt Pipeline (used by large subcontractors managing regional entities) map to Twenty's single parent-company reference via a custom field or by denormalizing to flat relationships.

Thunderbolt Pipeline's bid records carry bid name, estimated value, stage (Bid, Awarded, Lost, Withdrawn), expected start date, and primary contact. These map to Twenty CRM's Opportunities object. The bid stage label in Thunderbolt Pipeline becomes a Select field value on the Twenty Opportunity record — stage names are mapped value-by-value. Bid amount maps to Opportunity.amount. If the bid is Awarded, a flag migrates so admins can create a follow-on project opportunity in Twenty.

Thunderbolt Pipeline projects track active job records with crew assignments, resource allocation, compliance documents, and schedule data. These do not map to Twenty's standard Opportunities alone — we recommend creating a 'Projects' custom object in Twenty matching the project fields (name, status, start/end dates, assigned crew, location) and linking it to the originating Opportunity via a custom relation field.

Thunderbolt Pipeline task records with title, description, due date, assigned user, and linked record map directly to Twenty CRM's Tasks object. Tasks without a linked record migrate as standalone Tasks. Completion status (completed, open, overdue) maps to Tasks.status. The linked record reference is preserved as a custom relation field, allowing you to reconnect tasks to their parent opportunities or contacts after migration if needed.

Notes attached to bids, projects, contacts, or companies in Thunderbolt Pipeline migrate as Twenty CRM Notes. The note body and creation timestamp are preserved. Notes are linked to the parent record (People, Companies, or Opportunities) using Twenty's attachment mechanism. If a Thunderbolt Pipeline note contains rich text or embedded images, the body is preserved and inline image URLs are re-hosted.

Thunderbolt Pipeline user accounts (name, email, role) map to Twenty CRM Workspace Members. Role-based permissions in Thunderbolt Pipeline (Admin, Project Manager, Field Crew) have no direct equivalent in Twenty's standard role model — we create a custom 'Thunderbolt_Role__c' text field on each Workspace Member for reference and map admin-level users to Twenty admin roles.

Thunderbolt Pipeline's compliance module tracks OSHA logs, insurance certificates, permit statuses, and inspection results per project or contractor. These have no equivalent standard object in Twenty CRM. We create a 'Compliance_Record__c' custom object with fields for certificate type, expiration date, status, and a relation to the associated Companies record — this lets admins audit compliance history post-migration.

Thunderbolt Pipeline workforce records assign crew members to projects with labor-hour allocations. We split these into two Twenty records: a 'Labor_Assignment__c' custom object (linked to both Companies and Opportunities) for allocation hours, and a Task record per assigned crew member for actionable work items. This handles the N:1 crew-to-project relationship that a flat opportunity field cannot express.

Thunderbolt Pipeline file attachments (drawings, RFIs, submittals) linked to bids or projects are downloaded and re-uploaded to Twenty CRM's file storage. File size limits and inline image handling follow Twenty's attachment constraints. All files are linked to the parent Opportunities or Companies record in Twenty after upload.