Migrate from Systeme IO to monday CRM

Systeme.io contacts migrate as Items on a monday CRM People board. The People column type stores name and email natively. Additional contact fields like phone and job title map to text columns. Owner assignment maps to the Assignee column. We resolve Systeme.io owner email against monday workspace members. Custom fields (dropdown, checkbox, date) migrate to their equivalent monday column types with values preserved verbatim during the load step.

Systeme.io companies map to Items on a monday CRM Companies board linked via Connect monday boards. Address, domain, and industry fields map to equivalent text and link columns. Companies must land before their associated contacts so the relationship can resolve.

Systeme.io allows N:N contact-to-company associations with a primary flag. monday CRM Companies board links to People board via Connect monday boards. We migrate the primary company as the linked item and surface secondary links in a text column listing other associated company names.

Each Systeme.io pipeline becomes a monday CRM board. Pipeline stages map to Status column values. Deal properties (name, amount, close date, owner) map to Name, Deal column, Date, and Assignee columns respectively. Probability may map to a Number column if the source tracks it.

A Systeme.io pipeline is a distinct deal container — it maps 1:1 to a monday CRM board. We create the board and configure its default columns (Name, Status, Deal, Assignee, Tags) before migrating any deals. The board name matches the pipeline name from Systeme.io. This ensures the board structure is ready to receive deal records with their associated column data when the migration load begins.

Systeme.io automation rules (tag triggers, email sequences, stage-change actions) do not migrate. We export a JSON description of every rule and its conditions so your monday admin can rebuild them as monday Automations. This export is delivered with the migration plan.

Systeme.io contact tags migrate as a Tags column on monday Items. Tags with semantic meaning (e.g., lifecycle stage labels, campaign identifiers) may alternatively map to a Dropdown column for cleaner filtering. We document the chosen approach during the planning phase before migration runs. If tags drive segmentation in Systeme.io, the rebuild guide covers recreating equivalent filters using monday's grouping and automation triggers.

Systeme.io custom fields on contacts (text, number, date, dropdown, checkbox) map to monday column types of the same category. We create the column in the destination board and map values during the load step. Field display order in Systeme.io is preserved in the board column sequence.

Systeme.io custom fields on deals migrate as additional columns on the destination deal board. We map the field type to the nearest monday column type — for example, a Systeme.io currency custom field maps to a Number column with currency formatting.

Systeme.io orders contain line items, amounts, and status. These migrate as Items or Subitems on an Orders board linked to the originating Contact and Company Items. Order status maps to a Status column. Order total maps to a Number or Deal column.

Systeme.io contact activity records (email opens, page visits, tag changes) do not have a native monday CRM equivalent. We surface the last 90 days of activity as Item Updates on the contact's migrated Item, preserving the event type, timestamp, and description as plain text.

Systeme.io account users (owners, admins) are matched to monday CRM workspace members by email address. Unmatched owners are flagged in a pre-migration report before the run — you can invite those users to the monday workspace first, or designate a fallback assignee for all unmatched records. This ensures no records land without an owner assignment in monday. Owner resolution applies to both contact owners and deal owners consistently.