Migrate from Bright to Twenty CRM

Bright's person records (contacts, leads, partners) map directly to Twenty CRM's People object. Every field on the Bright record — name, email, phone, job title — transfers to the equivalent Twenty People field. The companyId link to the parent Company resolves after the Companies migration batch completes, so People are imported in step two of the sequence.

Bright companies map to Twenty CRM's Companies object. Company name, domain/website, industry, employee count, and annual revenue transfer as standard fields. Industry pick-list values require value-by-value mapping against Twenty's allowed values. Parent-company hierarchies in Bright map to Twenty's parentId field on the Company record — the parent must land in Twenty first, which our migration sequence ensures.

Bright deals become Twenty CRM Opportunities. The deal name maps to Opportunity.name, amount maps to amount, close date maps to closedAt, and stage maps to the stage pick-list. The stage pick-list in Twenty must be pre-populated with Bright's stage names before the migration runs — we deliver the required stage values as part of the schema setup plan before data lands.

Bright tasks migrate as Twenty CRM Tasks. Each task links to its parent record (Person, Company, or Opportunity) via the relationId field. The task body, due date, assignee (matched by email to Twenty users), and completion status all transfer. Completed tasks from Bright retain their completedAt timestamp as a custom field since Twenty's built-in status does not preserve the exact completion datetime.

Bright notes migrate to Twenty CRM's Notes object. Note title, body text, and rich-text content transfer directly. Notes in Twenty can be attached to Person, Company, or Opportunity records — we map the Bright note's parent record reference to the correct relationId and objectName in Twenty during the import.

Bright call activity logs — recorded calls with subject, duration, outcome, and notes — migrate as Twenty CRM Tasks with type set to 'Call'. The call outcome maps to a custom pick-list field on the Twenty Task since Twenty's standard task model does not include an outcome field. Owner and timestamp are preserved from the Bright activity record.

Bright meeting records — title, description, start time, end time, and attendees — map to Twenty CRM Events. The Event links to its parent Person or Opportunity via relationId. Meeting notes from Bright transfer as the Event description field. We preserve original start and end timestamps since these drive calendar views in Twenty.

Bright email activity logs — subject, body, timestamp, direction (sent/received), and recipient — migrate as Twenty CRM Tasks with type set to 'Email'. The email body and subject transfer to the task body and title fields. We create a custom 'EmailDirection' pick-list on the Twenty Task to preserve whether the email was sent from or received into Bright.

Bright custom objects map 1:1 to Twenty CRM custom objects. If Bright has a custom object named 'Project' or 'Subscription', we create the equivalent custom object in Twenty with matching field types before the migration. Custom object relationships in Bright that use N:N associations require a junction object in Twenty — we identify these during the planning phase and include them in the schema setup plan.

Every Bright custom field — whether on People, Companies, Deals, or custom objects — creates a corresponding custom field in Twenty CRM. Field type mapping is type-aware: Bright text fields become Twenty TEXT fields, pick-lists map to Twenty SELECT fields with the same options, date fields map to Twenty DATE fields, and number fields map to NUMBER. We do not charge extra for custom field creation since Twenty includes unlimited custom fields on all tiers.

Bright owner assignments on records map to Twenty CRM Workspace Members. We match Bright owner email addresses to Twenty user accounts by email. Any Bright owners who do not have a corresponding Twenty user are flagged before migration — the team either creates the Twenty user first or assigns those records to a fallback owner. No record lands in Twenty without a resolved owner.

Bright file attachments on any record type do not transfer via Twenty's CSV import tool. Files must be exported from Bright separately (via API or manual download), then uploaded to Twenty via the API or manually. After upload, each file must be re-linked to its parent record. This step is scoped separately from the core data migration because it involves file handling outside the structured data pipeline.

Bright workflows — automations triggered by field changes, date conditions, form submissions, or API events — have no equivalent in Twenty CRM's workflow engine. We export Bright workflow definitions as a structured reference document (JSON or markdown) so your team can rebuild them in Twenty's workflow builder. The reference document maps each Bright trigger to Twenty's trigger types and each Bright action to the corresponding Twenty action.

Bright integrations with third-party tools — email providers, calendar systems, telephony platforms, or data enrichment services — do not transfer. Each connection must be re-established in Twenty CRM using Twenty's API, webhooks, or available integrations. We document every active Bright integration during the audit phase so your team has a complete rebuild checklist before go-live.