Migrate from monday CRM to Freshsales

monday CRM People records map directly to Freshsales Contact. The People entity stores name, email, phone, and CRM-specific properties as a distinct API object separate from board Items. We migrate People by email as the dedupe key and preserve all standard fields (first_name, last_name, email, phone, CRM specific columns) against the Freshsales Contact schema. monday People with no email address are flagged during scoping for manual review; Freshsales requires an email for Contact creation via API.

monday CRM Deals are Items typed as CRM deals on a Pipeline board. They carry standard columns (deal value, close date, stage) plus optional custom columns. We map deal value to Freshsales Amount, close date to Close Date, stage to the Freshsales deal Stage field, and the owning Person to a Contact lookup. The monday pipeline becomes a Freshsales Sales Process or Deal Stage set that we configure before migration. Custom column values map to Freshsales custom fields on the Deal object, with type conversion (monday text to Freshsales text, monday numbers to Freshsales number fields, etc.).

Each monday CRM Pipeline defines an ordered set of Stages with stage names and optional probability percentages. We map each monday Pipeline to a Freshsales Deal Stage configuration, preserving stage name, order, and probability. If the customer has multiple monday Pipelines, we create corresponding Freshsales deal stage sets; Freshsales Growth supports a single deal pipeline, and multiple pipelines require Pro or Enterprise. We flag pipeline multiplicity during scoping so the customer understands any Freshsales tier implications.

monday CRM Boards used for account-level tracking (e.g., an Account Board with company info stored as Item columns) map to Freshsales Account records where possible. monday board column values representing company data (name, domain, industry, size) map to Freshsales Account fields. Boards without a natural Account equivalent are scoped as a custom field mapping exercise; we document the full column inventory during discovery and propose an Account or custom field mapping for each board.

Non-deal Items on monday boards that represent tasks, activities, or notes migrate to Freshsales Tasks or Notes attached to the parent Contact or Account. Items with assignee columns map to Freshsales Task records with an assigned User lookup. Items with a date column map to Freshsales due date. Items without a natural CRM equivalent are flagged in the scoping report for the customer to decide whether to migrate, archive, or rebuild in Freshsales.

monday Subitems are nested rows inside an Item, often used to track line items on a deal or related activities. They are not included in monday's bulk account export or per-board Excel export; we enumerate them individually via the monday API using each parent Item ID, which multiplies API call volume. Subitems with numeric values migrate as Freshsales Deal Line Items (Pro and above) or as Tasks on the parent Deal. We flag the total subitem count during scoping because it directly impacts API load and timeline.

monday board custom columns (text, numbers, dates, formulas, status, dropdown) map to Freshsales custom fields on the relevant object (Contact, Account, Deal). monday column types are preserved as field definitions in our export; we convert them to Freshsales field types (text, number, date, picklist, multi-select picklist). Formula columns and dependency columns in monday have no Freshsales equivalent and are flagged as 'no direct mapping' with the formula or dependency logic captured as a text note on the record.

monday Users map to Freshsales Users by email address match. We resolve every distinct owner referenced on a monday Item or Deal and match to a Freshsales User. Any monday User without a matching Freshsales User is held in a reconciliation queue for the customer's admin to provision before record import proceeds. monday Enterprise permission structures (multi-level permissions, SAML SSO) do not export and are documented separately.

monday Item Updates (comment threads) are enumerable per item via the API. We preserve update text and timestamps, mapping them to Freshsales Note records attached to the parent Contact or Deal. Activity timeline ordering is preserved by setting Freshsales activity timestamps to the original monday timestamp. monday activity log entries from the Standard tier (one-week log) may have truncated history; we document the available window during scoping.

monday CRM automations built on the Recipe (Sentence Builder) system are being deprecated and the logic is not portable to Freshsales Workflows or any other platform. Freshsales Workflows use a different trigger-action model with different conditions and actions. We do not migrate automations as code. We capture a written inventory of every active monday automation rule (trigger, conditions, actions, board context) during pre-migration review and deliver it to the customer's admin for rebuild in Freshsales Workflows. This inventory is included in the standard migration scope at no additional charge.