Migrate from REDA to monday CRM

REDA contacts migrate as individual items in a monday CRM Contacts board. The item Name maps to the contact's full name or first/last name columns. Each item is assigned to a monday user as the owner, resolved by email match against REDA's owner_id field. Primary company relationship is stored as a linked item or text column since monday has no native AccountId lookup.

REDA accounts become monday CRM items in a Companies board. Company name maps to the item Name field; address, industry, phone, and employee count become monday text, dropdown, and number columns. Parent-child company hierarchies in REDA are preserved by linking child company items to their parent company item in monday.

REDA deals map to monday CRM items in a Pipeline board. The deal name becomes the item Name; amount maps to a number column; close date maps to a date column; pipeline stage maps to a monday status column. REDA's multi-stage pipeline is recreated as monday columns representing each stage. Probability and forecast category are stored as separate number and dropdown columns with no native equivalent.

REDA tasks attached to a contact or deal migrate as monday subitems on the parent item, or as items in a separate Activities board linked by monday's item-linking feature. Original due dates, owners, and task status are preserved as monday date, assignee, and status columns respectively.

REDA calendar events map to monday CRM items in an Activities board. Start and end times become date columns; location becomes a text column; associated contacts and deals become linked monday items. There is no native calendar view in monday CRM for event items.

REDA notes attached to any object become monday CRM item Updates (preserving the original text, author, and timestamp) or items in a Documents board depending on whether the note is standalone or linked to a specific record. Standalone notes with no parent record are migrated to the Documents board to preserve the content. Inline images embedded in REDA note rich-text fields are extracted, uploaded to monday file storage, and re-inserted as file references.

REDA file attachments are downloaded and re-uploaded to monday CRM's file storage, attached to the relevant item via a file column. There is a per-file size limit in monday. Large files or files not attached to a specific record are migrated to a separate Documents board.

REDA custom fields on contacts, accounts, or deals become monday CRM columns in the appropriate board. Each custom field type (text, number, date, dropdown, checkbox) maps to the nearest monday column type. Boards have approximately 90 column slots — REDA setups exceeding this require splitting into multiple boards or archiving deprecated fields before migration.

REDA allows a contact to belong to multiple accounts with a primary flag. monday CRM has no native junction object for contact-company relationships. We create a linked-item relationship from each contact item to its primary company item in the Companies board. Secondary company associations are stored as a text column listing company names, or as additional linked items if monday's linked-item feature is available in your plan tier.

REDA owner records map to monday CRM user accounts by email address. We match REDA owner_id values against monday user email addresses. Any owner without a matching monday account is flagged before migration; the team either creates the monday user first or assigns those records to a designated fallback owner in monday.

REDA leads are treated as contact items in monday CRM, since monday has no separate Lead object. Lead status is stored as a dropdown column (Lead_Status__c). Conversion date and converted-by information are preserved as text and date columns on the item. A separate Leads board can be created for pipeline isolation if needed.

REDA opportunity contact roles define which contacts are associated with a deal and their role (e.g., Decision Maker, Technical Buyer). In monday CRM, we link the relevant contact items to the deal item. Role names are stored as a text or dropdown column on the linked relationship. This is a manual reconstruction step — the role label has no native equivalent in monday.