Migrate from Mothernode to monday CRM

Mothernode Contacts map to People items in a Monday.com CRM People board. The Person Type column on each People item is set to Contact. We extract all Contact fields from the Mothernode API (name, email, phone, address, custom fields) and map them to the equivalent Monday.com People column types. The Mothernode owner_id resolves to a Monday.com team member by email match. Contact records requiring merge with a Customer record sharing the same email are flagged in the dedupe pass before import.

Mothernode Customers map to People items in the same Monday.com CRM People board with Person Type set to Company. Customer records include company-level fields (company name, industry, revenue tier) that map to Monday.com Organization-linked columns or custom text columns on the People item. Customers with the same email as an existing Contact record are held for customer review during the dedupe pass rather than auto-merged, to avoid unintended Contact data loss.

Mothernode Leads migrate to People items in the Monday.com CRM board with Person Type set to Lead. The lead status value from Mothernode (prospecting, qualified, nurturing, or other custom stage names) maps to a Monday.com Status column on the People board. If the destination team uses Monday.com's separate Leads board, Leads land there instead with the same field mapping. Source attribution and lead score fields migrate as numeric or text columns. We confirm the Lead versus Contact routing during scoping based on the customer's pipeline definition.

Mothernode Opportunities map to Monday.com CRM Deals. Each Opportunity becomes a Deal item in a Deals pipeline board, preserving deal name, value, stage, expected close date, and owner assignment. The Mothernode pipeline stage names translate to Monday.com Deal Status column values that the customer configures in their pipeline board. Custom Opportunity fields (discount percentage, competitive flags, product interest) migrate as Monday.com dropdown or text columns on the Deal item and require column configuration in the target board before import.

Mothernode Invoices map to Deal sub-items in Monday.com's Items in boards feature. Each invoice becomes a sub-item attached to the corresponding Deal item, preserving invoice number, line items, totals, status, and customer reference. Monday.com's native Invoices product (Pro and Enterprise CRM tiers) can receive structured invoice data if the customer licenses that tier; otherwise, invoice records land as structured sub-items. Any Mothernode invoice attachments migrate as Monday.com file attachments on the sub-item.

Mothernode Events migrate as Activity updates on the corresponding People board item in Monday.com CRM. We extract event type, date/time, duration, and associated Contact or Opportunity link from the Mothernode API and write them as structured updates or comments on the linked People item. Calendar-bound events with an address or location create a Location column value. The activity timestamp preserves the original Mothernode event date for timeline ordering. Mothernode Events do not map to a native Monday.com Calendar integration; calendar sync requires a separate setup step post-migration.

Mothernode Notes migrate as comments on the linked Mothernode Contact, Customer, or Opportunity record's corresponding Monday.com CRM People item. We extract note content, author attribution, and the original timestamp. Notes attached to Opportunities migrate as comments on the linked Deal item. Note body text migrates as a comment with author and date preserved. Image attachments on notes migrate as file uploads to the Monday.com People item.

Mothernode Owner IDs on Contact, Customer, Lead, Opportunity, and Event records resolve by email match to Monday.com team members in the destination account. We extract the distinct owner_id list during scoping and cross-reference against the Monday.com team member roster. Owners without a matching Monday.com account go into a reconciliation queue for the customer's admin to provision before record import resumes. Active versus inactive status on the destination team member is preserved from the Monday.com account setup.

Mothernode Project Folders are gated behind the Enterprise tier and their API availability is not confirmed in the public documentation. Monday.com CRM does not have a native project management board structure within its CRM entity model; teams that rely on Project Folders for job tracking or service delivery would need to build a separate Work Management workspace in Monday.com as a parallel implementation. We flag Project Folder records as requiring a manual UI export and do not include them in the automated migration scope.

Mothernode Job Center Modules track real-time manufacturing or service operations and are an Enterprise-tier feature not covered in the public API documentation. Monday.com has no equivalent native job-tracking entity in its CRM product; operational job data would require a separate Monday.com Work Management board or a custom integration. We flag Job Center records as out-of-scope for the automated migration and deliver a written list of job record fields and dependencies for the customer's admin to assess and build manually if needed.