Migrate from Salesboom to Twenty CRM

Salesboom Leads with their distinct field structure (lead source, status, rating, industry) map to Twenty People records with a lead_status custom field capturing the original Salesboom Lead Status value. We resolve the Lead Owner to a Twenty workspace Member by email match during import. If the customer uses Salesboom's Lead scoring, the score value migrates to a custom People field. People records are created before any Opportunity import so that Opportunity-to-People lookups are satisfied.

Salesboom Accounts map 1:1 to Twenty Companies. The Account hierarchy (parent-child relationships), billing address, shipping address, and annual revenue transfer to the equivalent Company fields. Account Name becomes the Company name; Account Website maps directly. We use Company name and domain as the dedupe key during import. Company is the first object migrated because Contacts require an AccountId lookup.

Salesboom Contacts attach to Accounts and carry name, email, phone, title, and address fields. We map Contacts to Twenty People with the AccountId (from Account→Company mapping) resolved before People insert. Custom Contact fields migrate to custom People fields that we pre-create in Twenty Settings → Data Model before migration begins. Any Contact without a resolved Company gets a placeholder Company record to avoid orphaning.

Salesboom Opportunities with stage, amount, close date, and probability map directly to Twenty Opportunities. We pre-create the Opportunity stage values (win/loss/custom stages) in Twenty before migration. Stage names transfer as-is if they match; custom stage names are documented for the admin to configure post-migration. Opportunity Owner resolves to a Twenty workspace Member by email lookup.

Salesboom Tasks (subject, status, priority, due date, assigned owner) map to Twenty Tasks. Recurring tasks require flattening into individual records unless Twenty's recurring task configuration handles the pattern; we document any recurring task patterns that do not map cleanly. Task owner resolves via email-to-Member lookup. Activity timestamp preserves the original Salesboom CreatedDate for timeline ordering.

Salesboom Calendar Events migrate as Twenty Tasks with an activity type designation. Start time, end time, and location transfer to the corresponding Task fields. We create EventRelation-equivalent records by linking the Task to the relevant People or Company in Twenty. Attendees from Salesboom events link to multiple People records where attendee emails are resolvable.

Salesboom Notes attach to any parent record (Account, Contact, Opportunity) and migrate as Twenty Notes linked via the target object type and ID. Note body text transfers as-is; rich-text formatting is converted to plain text for compatibility. Ownership migrates by email-to-Member resolution.

Salesboom Cases (status, priority, origin, resolution) do not have a direct Twenty standard equivalent. We migrate Cases to a custom Case object that we pre-create in Twenty's Data Model with status, priority, and origin picklists configured before import. Auto-assignment rules and escalation workflows do not migrate; these are documented for the admin to rebuild in Twenty's workflow settings.

Salesboom allows unlimited custom fields on standard tabs at no additional charge. We extract all custom field definitions during discovery, map field types to their Twenty equivalents (text, number, date, picklist, boolean, currency), and pre-create them in Twenty Settings → Data Model before any CSV import runs. This is a critical dependency: Twenty's CSV import creates records, not fields, so all custom fields must exist in the target schema before migration. We document any Salesboom formula fields as computed-field notes for the admin to implement post-migration.

Salesboom ERP modules (Accounts Payable, HR Policy Tracking, Payroll, PTO Management) have distinct schemas from standard CRM objects. We migrate ERP transaction records as custom objects in Twenty, pre-creating the schema to match the source module structure. ERP data migration requires explicit scope confirmation during discovery because licensing for these modules ($10/user/month) varies per customer and affects record volume and complexity.

Territory Management in Salesboom Enterprise is a structured feature with its own data model. Twenty has no native territory object. We migrate territory assignments as a custom picklist field on Company or Opportunity, pre-creating the picklist values from Salesboom's territory list. Active territory-based routing rules do not migrate; we document the rule logic for the admin to implement in Twenty's workflow or custom code layer.