Migrate from Formaloo to monday CRM

Each Form in Formaloo maps to a dedicated Monday.com CRM Board. Each Form Response row becomes a Monday.com Item on that Board. We export Responses via the Formaloo REST API or Excel export, normalize date formats and field types per Formaloo's Excel import requirements, and import as Items. The Form field structure maps to Board Columns with field-type equivalence: text to Text Column, number to Numbers Column, email to Email Column, phone to Phone Column, date to Date Column, choice to Status or Dropdown Column, rating to Numbers Column. Signature fields do not transfer and are flagged during scoping.

If the customer uses a Formaloo Form to store Companies or Organizations, we map those Response records to Monday.com CRM's native Company object. The Company Name, Website, Industry, Phone, and Address fields map to their Monday.com CRM equivalents. Company records are imported before any related People records so that the Company-Contact relationship is established during People import.

If the customer uses a Formaloo Form to store Contacts or People, we map those Response records to Monday.com CRM's native People object. The Person Name, Email, Phone, Address, and any custom fields map to their Monday.com CRM equivalents. We resolve the Company lookup if the customer also has a Company Form that was mapped in the prior step.

The Form definition (field names, field types, conditional logic visibility rules) does not migrate as data but drives the Board schema. We document each Form's field structure as a Board design specification for the customer to recreate in Monday.com CRM, including recommended Column types and any Status column configurations that correspond to Formaloo choice fields.

Formaloo's relational Database layer links Forms together via reference fields. We export the Database structure as a set of related tables with foreign-key references preserved. During Monday.com CRM import, we create Item Links between Boards or configure Lookup Columns pointing to the related Board. Multi-level relational chains (Form A references Form B which references Form C) are resolved iteratively: parent records are imported first, then child records with lookup IDs attached. We flag any circular reference patterns during scoping.

Formaloo file upload field values are exported as file paths or URLs. We map file attachments to Monday.com Item attachments, downloading source files and uploading them to the corresponding Item. File size limits follow Monday.com's storage tier (5GB on Basic, higher on Standard and Pro). Files hosted externally are preserved as URL references if the customer prefers not to re-host.

Formaloo's conditional logic, field visibility rules, and calculation formulas are UI-defined automation that does not export as structured data. We document each Form's logic configuration as a text summary describing which fields are conditional, what triggers the condition, and what action occurs. The customer's admin uses this document to rebuild equivalent automations in Monday.com's Automation Builder. We do not translate Logic Rules into Monday.com automations as part of the migration scope.

Formaloo Workspace and Folder hierarchy maps to Monday.com Workspace structure. We export the workspace and folder path for each Form and use folder paths to determine the target Workspace in Monday.com CRM. Nested folder depth is preserved as Board Groups within each Workspace. The customer chooses whether to consolidate or flatten the hierarchy during scoping.

Formaloo's folder-level access control and role-based permissions are exported as a permission matrix listing each user, their role, and the Forms and Folders they can access. This matrix is delivered as a written document for the customer's Monday.com CRM admin to configure equivalent Workspace and Board permissions post-migration. Monday.com CRM's permission model differs from Formaloo's, so direct automated translation is not possible.