Migrate from Lofty to monday CRM

Lofty leads map directly to items in Monday CRM's People board. Each lead record becomes a new item with columns created to match Lofty's standard and custom fields. Primary contact status is preserved as a boolean column and can be set to true or false based on the lead's primary flag in Lofty.

Lofty company records become items in the Monday CRM Companies board. Company hierarchy (parent/child relationships stored in Lofty's parent_company_id field) maps to a linked Company column in Monday CRM pointing to the parent item. If a company has no parent, the column remains empty; child items retain a link to their parent company record for accurate organizational structure.

Lofty deal records map to items in the Deals board. Deal amount, close date, and stage all map to corresponding Monday CRM columns. The deal owner resolves by email match to a Monday CRM team member. If multiple owners are assigned in Lofty, the first matched email is used; unmatched owners trigger a pre-migration flag for team assignment.

Lofty pipeline stages map to Monday CRM status column values in sequence order. Stage names are preserved verbatim; if stages contain spaces or special characters, Monday CRM normalizes the internal value key while keeping the display label intact and retains the original ordering for reporting.

Lofty text, number, and date custom fields create equivalent column types in Monday CRM's corresponding board. Field labels are copied directly as Monday CRM column names. Data type parity is enforced at migration time to prevent type-cast errors. If a Lofty field contains unsupported characters, FlitStack AI sanitizes the column name while preserving the original label in a secondary description field.

Lofty single-select custom fields map to Monday CRM dropdown columns. Each pick-list option in Lofty becomes a dropdown choice in Monday CRM. Option order is preserved from Lofty's field configuration. If a pick-list value contains a colon or other punctuation, Monday CRM normalizes the internal identifier while displaying the original text for user clarity.

Lofty multi-select fields become Monday CRM tags columns. Each selected value in Lofty creates a tag on the Monday CRM item. Tags allow filtering across the board, which mirrors Lofty's multi-select filtering behavior. If the original selection order matters, FlitStack AI stores the order in a secondary numeric column for reference.

Lofty's N:N lead-to-company association migrates as a Monday CRM relationship column linking the People item to the corresponding Companies item. If a lead associates with multiple companies, multiple relationship links are created on the item. This ensures that each affiliation is preserved, and the relationship column can be filtered to view all companies associated with a contact.

Lofty deal associations to leads and companies migrate as Monday CRM item links on the Deals board. The deal item links to the relevant People item (contact) and Companies item (account) simultaneously. If a deal references a lead or company that hasn't yet been imported, FlitStack AI queues the link for later resolution to maintain referential integrity.

Lofty tags applied to leads or companies migrate as Monday CRM tags on the corresponding board item. Tags are migrated per board — a tag applied to a lead lands on the People item, not on the Deals item and can be filtered across the board for reporting.

Lofty activity history — calls, emails, and notes — migrates as updates or subitems on the associated Deals or People item in Monday CRM. Original timestamps and owner names are preserved in the update body. Each activity entry retains its original text content, and any attachments referenced in Lofty are noted as links for manual reattachment if needed.

Files attached to Lofty leads or deals are downloaded and re-uploaded to Monday CRM's file storage attached to the corresponding item. Monday CRM file size limits apply — files over 500 MB are flagged for chunked re-upload. During re-upload, FlitStack AI verifies the file checksum to ensure data integrity and logs any upload failures for retry.