Migrate from BSI CRM to monday CRM

BSI CRM Contact records (name, email, phone, title, custom fields) map to Monday.com CRM Contact Items. The BSI contact ID is preserved in a custom column for lookup integrity. Multi-value custom fields from BSI translate to Monday multi-select columns. BSI's organizational hierarchy fields (department, reporting structure) become text or relation columns in Monday. Note that Monday's Contact Items lack a native activity timeline; activity history migrates as structured columns on the Item rather than a separate linked object.

BSI Company records map to Monday.com Contact Items on a separate Companies Board, linked via a relation column to the Contact Board. BSI's hierarchical parent-company structure becomes a relation column pointing to the parent Company Item. Industry classification and sector fields from BSI map to single-select columns. If the customer uses BSI's multi-company hierarchy, the flat Monday structure requires the customer to decide whether to model parent-child relationships via relation columns or accept a flat list.

BSI Deal records map to Monday.com CRM Items on a dedicated Deals Board. The BSI pipeline stage becomes a Monday board Group or a status column, and deal value maps to a number column. Expected close date becomes a date column. Owner assignment from BSI maps to the Person column in Monday, referencing the mapped User record. BSI deal probability (if used) migrates as a number column; Monday does not have a native probability field so this requires a custom column or a workaround using the deal value as the probability proxy.

BSI's structured pipeline stages (with stage names, probabilities, and ordering) map to Monday board Groups that represent each stage. Each Group becomes a column section in the Kanban view. If the customer uses multiple BSI pipelines, each BSI pipeline becomes a separate Monday Board with its own Group structure. Stage ordering is preserved by the visual board layout.

BSI Activity records (calls, emails, meetings, tasks linked to Contacts or Deals) migrate to Monday as structured column entries on the parent Item. Call disposition and duration become text and number columns on the Contact Item. Email subject and body become text columns. Meeting details (date, duration, attendees) become date and text columns. Task status and due date become status and date columns. Monday does not have a first-class Activity object; the customer accepts the flattened column representation of activity history.

BSI CRM custom objects defined within its modular architecture map to dedicated Monday Boards with column types matching the original field definitions. Custom object discovery is required before migration design because BSI does not publish a self-service schema export. We enumerate all custom object names, field types, and record counts during discovery, then recreate the schema as Monday Boards with matching column configurations. Lookup relationships between custom objects become relation columns in Monday.

BSI file attachments associated with Contacts, Deals, or Activities are exported individually and linked back to their parent Item in Monday via the file upload column. BSI's file storage structure varies by configuration, so we validate attachment accessibility during discovery. Files that cannot be extracted are flagged for manual re-upload post-migration.

BSI CRM Users referenced as record Owners map to Monday.com workspace members. We resolve by email match. Any BSI Owner without a matching Monday account is placed in a reconciliation queue for the customer's admin to provision before record import. Role and permission information from BSI is preserved as a text field on the owner record rather than as native permission settings since Monday's permission model operates at the board and item level.

BSI CRM tagging and custom classification fields map to Monday's Tags feature (a native tagging system on Items) or to multi-select columns depending on the customer's preferred organization model. Tags used for lead segmentation become label columns. Classification fields with a defined value set become single-select columns. We preserve all original tag names and classification values; the customer chooses the target representation during scoping.