Migrate from Bidtracer to Twenty CRM

Bidtracer contacts map directly to Twenty People records. We resolve the primary company association using Bidtracer's company link and map it to the companyId relation in Twenty. All standard contact fields — name, email, phone, job title, address — transfer directly. Owner resolved by email match against Twenty workspace members.

Bidtracer companies map to Twenty Companies with a direct name, domain, industry, and address transfer. Bidtracer's company hierarchies (parent / child) map to Twenty's Parent Company relation. Multi-contact companies collapse to a single Company record with all linked People associated via companyId.

Bidtracer deals map to Twenty Opportunities. The deal name becomes Opportunity name, amount transfers as a currency field, stage maps via value mapping to Twenty's stage pick-list, and close date maps to the expectedCloseDate field. Linked People and Company relations are resolved via email and domain matching before the Opportunity import runs.

Bidtracer call logs, emails, and meeting records become Twenty Tasks. Call duration and disposition notes append to the Task body. Email subject lines map to Task subject. Meeting subject, start time, and attendee list become a Task with the location field set from Bidtracer's meeting location. Original timestamps and owner assignments are preserved on every migrated activity.

Bidtracer notes migrate to Twenty Notes with full fidelity. Each note is linked to its parent record — People, Company, or Opportunity — using the ID mapping established during import. Rich-text formatting is preserved where Bidtracer's export format supports it. Notes that have no associated parent record in Bidtracer are imported as standalone Notes in Twenty without any relation constraint.

Bidtracer user records — name, email, role type — map to Twenty workspace members. Resolution happens by email match: if a Bidtracer owner email matches an invited Twenty user, that user is assigned as the record owner. Unmatched owners are flagged before migration so the team can invite them to Twenty first.

Bidtracer bid tracking has no native Twenty equivalent. We create a 'Bid' custom object in Twenty's Settings → Data Model before migration, with fields for bid number, bid title, bid status, bid type, bid amount, awarded date, expiration date, and contract type. Bid records link to the associated Company and Opportunity via relation fields.

Bidtracer's BAC estimating module — estimate number, total cost, labor cost, material cost, overhead, markup — maps to a custom 'Estimate' object in Twenty. Construction-specific fields like building type, square footage, and specification notes migrate as custom fields. These require schema pre-creation before any estimate records can be imported.

Bidtracer project management entries — project number, project name, project status, project type, start date, projected completion — migrate as a custom 'Project' object in Twenty. Custom fields capture scope details and budget information from Bidtracer's project records. Projects link to their associated Company via companyId.

Bidtracer service agreement records — agreement number, status, term length in months, start date, end date — migrate as a custom 'Service Agreement' object. Linked People (primary contact) and Company associations are preserved via relation fields in Twenty's custom object model.

Bidtracer file attachments on records are downloaded and re-uploaded to Twenty's file storage. Files link to their parent record (People, Company, Opportunity, or custom object) via relation. File size limits apply per Twenty's upload configuration. We re-create the original folder hierarchy where Bidtracer's export preserves it.

Bidtracer custom fields on any object — construction-specific properties, user-defined pick-lists, numeric fields — migrate as Twenty custom fields. They require pre-creation in Settings → Data Model before the import runs. Pick-list values are mapped value-by-value; numeric and text fields transfer directly. Custom fields with no Twenty equivalent become generic text fields and are flagged for admin review.