Migrate from BSI CRM to Twenty CRM

BSI CRM Contact records map directly to Twenty CRM Person objects. Standard fields (name, email, phone, title) transfer directly. Any custom contact fields defined in BSI's modular configuration migrate as custom fields on Person, which Twenty creates via the /metadata API. BSI contact-industry classification fields map to custom fields on Person or to a link to a Company record depending on the field's intended use. The Person.companyId link is resolved by the Company mapping phase before Person import begins.

BSI CRM Company records map to Twenty CRM Company objects with hierarchical parent-child relationships preserved. Industry classification, annual revenue, employee count, and address fields transfer directly where field types are compatible. BSI's company domain field maps to the Company domain field in Twenty. Parent-company linkages resolve through the Twenty Company lookup field, which we validate after Company import by comparing record counts against BSI's reported totals.

BSI CRM Deal records map to Twenty CRM Opportunity objects. Pipeline stage names from BSI vary by industry configuration, so we define an explicit stage mapping table during scoping before migration. Deal value, owner assignment, expected close date, and currency fields transfer directly. Any BSI-specific deal fields (such as deal source, win/loss reason, or custom deal attributes) become custom Opportunity fields created via Twenty's metadata API before import.

BSI CRM pipeline stages are configurable per industry module and may not align with Twenty's default stage set. We enumerate all active pipeline stages during discovery, then create matching stage options in Twenty's Opportunity workspace before any Deal records are imported. Probability percentages from BSI map to Twenty's stage probability values with rounding to the nearest supported integer.

BSI CRM Activity records — logged calls, emails, meetings, and tasks — map to Twenty's Task and Event objects with type differentiation by activity.kind. Call disposition and duration transfer to custom Task fields. Meeting records with start and end times map to Twenty Event. Email records map to Twenty's email-capable Task or Activity model depending on how the destination workspace is configured during setup. All activities link to their parent Person and Company via the relationship fields that Twenty provides. We validate the count of migrated activities against BSI's reported totals before closing the phase.

BSI CRM custom objects are defined within its modular configuration and require a pre-migration discovery phase because the platform does not publish a self-service export or schema introspection for custom objects. We enumerate every custom object name, its field definitions (name, type, required/optional), and record counts manually during scoping. Twenty receives these as custom objects created via its /metadata API before any BSI data loads. Custom object relationships to Person, Company, or Opportunity resolve after the parent standard object is already present in Twenty.

BSI CRM User records are migrated first in the load sequence because every other object references owners as foreign keys. We resolve BSI user emails against Twenty's user table by email match. Any BSI Owner without a matching Twenty User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Role and permission sets do not transfer because they are platform-specific configuration; we document the role structure for manual reconstruction.

BSI CRM file attachments associated with Contacts, Deals, or Activities are exported individually from BSI's file storage and must be linked back to their parent record in Twenty. Twenty's CSV import does not include file attachments, so we migrate attachments via the Twenty REST API or flag them for manual re-upload with a record linkage map documenting which files belong to which Person, Company, or Opportunity. The linkage map is delivered as a CSV with the original filename, parent object, and parent record ID from both systems.

BSI CRM tagging and custom classification fields may not have a direct Twenty equivalent depending on how the tagging system is implemented in BSI's modular configuration. We capture these as custom multi-select or text fields on the relevant Twenty object and flag any tagging logic that represents business rules rather than simple categorization. Business-rule tagging that should trigger workflow actions in BSI is documented separately for workflow rebuild in Twenty.

BSI CRM workflow automation rules and AI-generated inferences are configuration artifacts that do not export as portable data. We document every active workflow and automation configuration during discovery and deliver a written rebuild checklist with trigger, conditions, actions, and recommended Twenty workflow equivalent. This includes AI enrichment logic, lead scoring rules, automated data triggers, and compliance logging workflows that BSI's built-in AI generates. Rebuild time is scoped at 2-4 weeks for moderate automation complexity and is outside the migration fee.