Migrate from Bolten CRM to Twenty CRM

Bolten Contact records map directly to Twenty People. We preserve name, phone, email, custom properties, assigned tags, and lead-source attribution stored on the contact record. The Bolten contact record's audit log (timestamped record changes) migrates as a chronological Note attached to the People record. AI-generated autofill field values migrate as the current confirmed field value, not the AI suggestion history, because the suggestion log is not accessible via the standard export.

Bolten maintains Leads as a separate list from Contacts. We migrate Bolten Leads to Twenty People records. Leads that reference a company name in Bolten are matched against migrated Companies in Twenty; if no matching Company exists, the People record is created standalone and the company name is stored in a custom text field for later Company linkage if needed. Lead lifecycle status and source campaign attribution migrate as custom fields on the People record.

Bolten Deals map to Twenty Opportunities. We migrate deal name, value, stage name, owner assignment, and linked contact references. Each Bolten Deal's stage name is resolved to an explicit ordinal position during the pre-migration mapping phase (see Gotcha: Kanban stage ordering). Deals that reference a linked Bolten Contact resolve to the corresponding migrated People record via email or name match before Opportunity import begins.

Bolten Kanban stages are free-text labels with no enforced ordering property in the API. We capture the intended stage sequence from the customer's confirmed stage list and configure Twenty Opportunity stages with explicit ordinal positions and probability percentages before Deal records load. Any Deals already in progress on cutover land in the correct stage position immediately because the stage schema is pre-validated.

Bolten Tasks migrate to Twenty Tasks with assignee, due date, status, and linked contact/deal association intact. Task assignment migrates by resolving Bolten owner email to the corresponding Twenty User. Recurring task rules (Bolten automation) do not transfer and are documented in the automation inventory for the admin to rebuild in Twenty's workflow builder.

Bolten's per-record change audit history (every edit, assignment, and stage move) migrates as Note records with timestamps attached to the relevant People, Company, or Opportunity. Activity log ordering is preserved by setting the Note's creation date to the original Bolten audit timestamp. AI suggestion history does not migrate because it is not accessible via the standard Bolten export.

Bolten custom fields (text, number, date, dropdown, multi-select) are supported per-object. We pre-create the corresponding custom fields in Twenty's data model (Settings, Data Model) before any record data loads. Type conversion is applied where Bolten and Twenty field types differ: Bolten multi-select maps to Twenty multi-select, Bolten date stores as Twenty date, and Bolten dropdown maps to Twenty select with the same option values.

WhatsApp message content cannot migrate because it is stored on Meta's infrastructure, not Bolten's database. We preserve the contact's phone number (as a People field), the conversation start timestamp, and the last-message timestamp as a Note on the People record. Full chat history requires a separate Meta data-portability request outside our pipeline.

Bolten Users are identified by email and name. We map source User email to destination User email during import. Suspended or inactive Bolten users are flagged for remapping to active Twenty Users before production migration. The customer provisions the destination Twenty users before the migration window begins.

Bolten tags are flat-label strings applied to contacts and deals. We migrate tag sets and preserve the tagging relationship per record. Tags that exceed Twenty's character limit are trimmed to fit and flagged in the reconciliation report. The customer chooses whether migrated tags are re-created as Twenty native tags or stored in a custom multi-select field.

Bolten tracks lead origin (Google, Meta Ads, direct) and real-time conversion events per-Lead and per-Contact. We migrate conversion attribution as custom fields on the associated Opportunity or People record. UTM-source and UTM-medium values may be incomplete in the export if they were overwritten or cleared in Bolten's UI; we flag any missing attribution data in the audit report and recommend re-enrichment via a UTM enrichment service post-migration.