Migrate from Field2Base to monday CRM

Each Field2Base Form Template maps 1:1 to a Monday CRM Board. The board name inherits the form template name. Board type (CRM vs. Work Management) is selected based on whether the form captures customer/prospect data — forms with contact fields become CRM boards; operational forms become Work boards. Groups inside the board correspond to form submission groups or regions.

Every Field2Base Form Submission becomes a single Monday CRM Item within the corresponding Board. The Item Name defaults to a human-readable identifier derived from the submission (e.g., work order number, customer name, submission date). All field values from the submission populate the item's columns. Submission timestamps are preserved as a Creation Log column or a custom Date column in Monday.

Field2Base Regions of type Text, Numeric, and Date map directly to Monday's equivalent column types. Text regions become Text columns; Numeric regions become Numbers columns with optional precision settings; Date regions become Date columns. The Monday column name matches the Region label from the form template. Validation rules set in Field2Base (required, numeric range, date range) are noted for Monday-side column configuration.

Field2Base Drop-Down regions map to Monday Dropdown columns, with option values copied one-for-one. Multi-Select regions in Field2Base (where multiple choices can be selected per submission) map to Monday's Tags column, which supports multiple labels per item. This is the most common non-direct mapping for operational forms with status or category fields.

Checkbox regions in Field2Base map directly to Monday's Checkbox column type. Each form checkbox becomes its own Checkbox column on the target board, preserving the true/false state for each submission. If the checkbox represents a specific flag such as 'Signature Obtained', the Monday column label is updated to match that description, keeping the original boolean values intact and allowing them to drive Monday automation triggers without further transformation.

Field2Base photo regions (captured images submitted with a form) are downloaded from Field2Base storage and re-uploaded to Monday as File Upload column attachments. Photo filenames include the field label and submission ID for traceability. Monday's file size limit per upload is 500MB; large photos are compressed before loading if they exceed this threshold.

Signature regions in Field2Base store PNG or JPEG images of captured signatures. These are downloaded and uploaded to Monday as File Upload column entries on the corresponding item. The column is labelled with the field name (e.g., 'Customer Signature'). Signature capture date is preserved in a paired Date column or as a file naming convention.

Field2Base GPS regions capture latitude and longitude coordinates at the time of form submission. These are mapped to Monday's Location column, which displays a map pin. If Field2Base stores GPS as separate numeric fields (latitude, longitude), those are combined into a single Location value. Address text captured alongside GPS is stored as a parallel Text column.

Barcode and QR code region values captured by Field2Base are plain-text or numeric strings. These map to Monday Text or Numbers columns depending on content type. The original scan timestamp is preserved as a custom Date column if available in the submission data.

Field2Base users who submitted forms are resolved by email match against Monday CRM workspace members. If a Monday user exists with the matching email, the submission item is assigned to that person via a Person column in Monday. Unmatched Field2Base users are flagged before migration — teams either invite them to Monday first or the submission is assigned to a fallback owner.

Field2Base does not maintain a native Companies object in the CRM sense — companies appear as form field values (e.g., a 'Company Name' text field). If teams used Field2Base with company-level context, that context is migrated as a Monday CRM entity board (Contacts/Companies board) with items representing each unique company. Company data embedded in form submissions is mapped to custom text fields on those entity items.

Field2Base Workflow definitions for multi-step review and approval chains are not data records and cannot be exported. These must be rebuilt in Monday as Automations. FlitStack provides a Workflow Audit Export — a structured list of each Field2Base Workflow's triggers, conditions, and actions — that serves as a rebuild reference for your Monday admin.

Field2Base Data Integration Module configurations (ODBC connections, XML mappings, web service endpoints) are system-level settings that do not export. They must be rebuilt as Monday native integrations, Zapier/Make scenarios, or custom API connections. FlitStack documents each active DIM configuration during discovery so the rebuild scope is clear.

EDM dispatch data — pre-populated field values sourced from back-office systems for form templates — is stored as submission metadata in Field2Base. These values migrate as custom columns on the relevant board items. If EDM sourced data from a specific ERP or SQL system, the Monday admin must configure a replacement data-pull integration post-migration.

Field2Base tracks form template revision history, which affects how older submissions were structured. Monday's Activity Log captures item-level changes. If template versioning impacted field definitions over time, submission data from older versions is mapped against the most recent Monday column schema, with a note added to each affected item identifying the original template version.