Migrate from Bluetrait to Twenty CRM

Bluetrait Tickets map to Twenty CRM Case records with ticket status, priority, due date, assignee, and internal notes preserved. Custom fields on Bluetrait Tickets require pre-creation in Twenty's custom field schema before migration; we create the equivalent custom fields via the Twenty Custom Objects API. Ticket tags map to a multi-select picklist field. Ticket conversations migrate as Comments linked to the Case record.

Bluetrait Company records map directly to Twenty CRM Company. The Company name, website, address, phone, and custom fields migrate as typed fields. We use the Company name as the dedupe key during import and resolve any duplicate Company names with a numeric suffix. Company-linked Client records are mapped after Company insertion so the relationship is satisfied.

Bluetrait Client records map to Twenty CRM Person with first name, last name, email, phone, role, and custom fields preserved. Clients linked to a Company via Bluetrait's company association are linked to the corresponding Twenty Company via the Person's workspaceKey field. Any Bluetrait Client without a last name set is flagged for manual review during scoping because Twenty Person requires a non-empty last name.

Bluetrait Timesheet entries (date, hours, user, task/project link, timesheet type) map to a Twenty CRM Custom Object we create called Timesheet with fields for date, duration, user reference, project reference, and billable flag. The timesheet type (billing or non-billing) is preserved as a custom field. Historical timesheet entries migrate as completed records; future entries are not generated.

Bluetrait Project records (name, budget, task count, linked timesheets) map to Twenty CRM Opportunity if the project has a commercial pipeline component, or to a Custom Object called Project if it is an internal work tracker. Project budget thresholds and custom statuses migrate as custom fields. Task counts transfer as a numeric field for reporting purposes.

Bluetrait invoices, quotes, and purchase orders map to a Twenty CRM Custom Object called Invoice with fields for invoice number, date, line items, tax amount, payment status, and linked Opportunity. Open invoices migrate with their full line item history. Closed invoices migrate as historical records. Recurring billing automation configurations are not migratable; we document every recurring billing rule encountered during scoping as a written handoff for the customer's admin to re-create in their billing tool of choice.

Bluetrait Products (name, SKU, quantity, pricing, recurring billing frequency) map to a Twenty CRM Custom Object called Product with fields for name, code, unit price, quantity, and billing cadence. Product-to-billing associations map as lookup relationships in the custom schema. Subscription cadence requires manual re-setup in the destination billing system post-migration.

Bluetrait Agents (endpoints with watchdog status, installed software, alert configurations) are MSP-specific and have no direct equivalent in Twenty CRM. We export agent metadata as a CSV inventory and create a Note on the associated Company record in Twenty for reference. Alert configurations and health monitoring data do not migrate because Twenty has no RMM module; these are documented separately as out-of-scope for CRM migration.

Bluetrait Users (username, role, permissions group, 2FA status) map to Twenty CRM WorkspaceMember records. Active users are invited during migration; inactive users are created as deactivated members. Bluetrait passwords do not migrate for security reasons and must be reset in Twenty post-migration. Owner assignment on Tickets, Companies, and Projects resolves via email match against the WorkspaceMember list.

Bluetrait Knowledge Base articles export via CSV and map to Twenty CRM Note records linked to the relevant Company or Person. Article-to-ticket associations are preserved as a mapping table (article ID to ticket ID) provided as a written reference for manual re-linking in Twenty. No native article management module exists in Twenty; customers requiring a KB rebuild use a dedicated knowledge base tool post-migration.

Bluetrait Passwords module entries cannot be extracted via API or CSV for security reasons. We generate a full inventory of password entry names, associated systems, and folder structure as a reference document. The customer recreates entries in their chosen password manager (Bitwarden, 1Password, or similar) post-migration. This is a customer-admin task, not a data migration task.