Migrate from Sercom to monday CRM

Sercom accounts map to Items on a monday CRM Account board. Each account becomes a single Item with address, industry, and primary-contact columns. Monday's board-level column types replace Sercom's account schema fields. Parent-account hierarchies in Sercom map to monday Group structure or Item Links between account Items.

Sercom contacts map to Items on a monday CRM Contacts board. Each contact becomes one Item with name, email, phone, and role columns. Monday's People column type captures the contact owner. Multiple contacts per Sercom account are represented as separate Items linked back to the Account Item via one-way Item Linking.

Sercom service requests are the most complex object to migrate. We map them as Items on a dedicated Service Requests board — using monday Status columns for request status and priority, Date columns for SLA and resolution timestamps, and Text columns for description and resolution notes. Technician assignments use monday People columns. Sercom's FSM status workflow becomes a monday Status column with matching values.

Sercom technicians map to Items in a Resources board, capturing name, email, phone, and skill set. If technicians also log into Monday CRM, they are provisioned as monday users and matched by email. Sercom role and certification fields migrate as monday Text or List columns depending on value count.

Sercom equipment and asset records migrate as Items on an Asset board. Serial number, equipment type, model, and install date become monday columns. Asset-to-account linkage migrates as monday Item Links so each asset is connected to its associated Account Item.

Sercom service request statuses (Open, In Progress, Pending Parts, Resolved, Closed) map to monday Status column values. We create the monday Status column with values matching the Sercom pick-list exactly so that filtering and reporting continuity is preserved. Probability weights from Sercom's FSM stages do not transfer — those must be rebuilt as monday automation conditions if needed.

Sercom custom fields on accounts migrate as monday custom columns. Text fields become monday Text columns, date fields become Date columns, numeric fields become Number columns, and pick-list fields become monday List or Status columns. We create all required columns in monday before the migration run so data lands in the correct column without type-mismatch errors.

Sercom custom fields on service requests migrate as monday columns on the Service Requests board. Complex Sercom field types (e.g., multi-select) that have no direct monday equivalent are flattened into a Text column or split across multiple List columns — we document the transformation logic in the migration plan before execution.

Sercom file attachments on service requests and accounts are downloaded and re-uploaded as monday Files attached to the corresponding Items. File size limits follow monday's per-plan storage quota (5 GB Standard, 20 GB Pro, 100 GB Enterprise). Inline images in Sercom notes are extracted and attached as monday Files.

Sercom location records with structured address components (street, city, state, postal code, country) migrate to monday Address columns if available on the plan, or to separate Text columns for each component. We preserve the full original address string as a reference Text column in addition to the structured split, so nothing is lost during migration.

Sercom scheduling rules and FSM workflow configurations have no monday CRM equivalent. Monday's automation builder can recreate simple time-based triggers and routing logic, but complex scheduling dependencies and field-service dispatch rules cannot be migrated. We export the Sercom workflow configuration as a reference document and provide a rebuild guide for your Monday admin.

Sercom service history entries (status changes, technician notes, parts used) migrate as monday Updates on the corresponding Service Request Item. Each history entry becomes a timestamped Update with the author name and content preserved. This preserves the full operational timeline without requiring a separate Activity board.