Migrate from Mothernode to Zoho CRM

Mothernode Customers represent organizations or companies. We map them directly to Zoho CRM Accounts using the customer_id as an external reference and the company name as the Account Name. If the customer record contains billing address data, we map it to the Account's billing address fields. Accounts are created first in the migration sequence so that subsequent Contact imports can resolve the AccountId lookup. Mothernode Customers with no organization name (sole traders) are flagged for the Contact-first mapping pattern.

Mothernode Contacts represent individuals linked to Customer records. We map them to Zoho Contacts with the Contact's parent customer_id resolved to the newly created Zoho Account. Name fields, email, phone, title, and mailing address migrate 1:1. If the Contact has no associated Customer in Mothernode, we create a placeholder Account or attach it to a designated default Account during scoping. The Contact's owner_id resolves to the Zoho User via email match.

Mothernode Leads and Opportunities share the /leads-and-opportunities endpoint with a record-type field distinguishing them. We separate Leads at extraction time using this indicator and map them to Zoho Leads. The Lead's status, source, and score fields (if present) migrate to Zoho Lead Status, Lead Source, and a custom field. Mothernode custom fields on Leads are probed during the schema audit phase and created in Zoho before import.

Mothernode Opportunities are separated from Leads at extraction using the record-type indicator and map to Zoho Deals. The opportunity amount, stage, close date, and probability migrate to Zoho Deal Amount, Stage, Expected Close Date, and Probability. Pipeline assignment in Mothernode maps to a Zoho Sales Pipeline that we configure before migration. Owner resolution runs against the User mapping table.

Mothernode stage names are extracted from the source data and mapped to Zoho Sales Pipeline stages. We create the Zoho pipeline and stage configuration before migration begins so that incoming Deal records reference valid stage values. Stage probability percentages migrate as numeric fields on each Deal. If Mothernode uses a multi-stage pipeline, we create multiple Zoho Sales Pipelines or use the Stage field with multiple values within a single pipeline.

Mothernode Notes are accessible via the Notes/Events endpoint. We extract note content, associated entity IDs (customer_id, contact_id), timestamps, and author attribution. Notes attached to a Contact or Customer are mapped to Zoho Tasks linked to the corresponding Contact or Account. Standalone notes without a parent entity are mapped to Zoho Notes (using Zoho's Notes module if available in the target edition). The original creation timestamp is preserved as Activity Date.

Mothernode Events (meetings, appointments) are separated from Notes at extraction and mapped to Zoho Events. Start time, end time, location, and description migrate directly. The associated entity links (customer_id, contact_id) resolve to Zoho Account or Contact via the parent lookup. Event attendees are not a standard Mothernode API field but are preserved if present in the payload.

Mothernode Invoices are mapped to Zoho CRM Invoices if the destination is Zoho CRM Professional, Enterprise, or Ultimate. The invoice number, date, due date, line items, totals, and status migrate. Note that Zoho CRM Standard edition does not include a native Invoice module; in that case, we map invoice data to Zoho Books (a separate Zoho product) or flag it as a manual-rebuild item. The customer selects the handling during scoping.

Owner assignment in Mothernode is referenced via owner_id on Lead, Opportunity, Event, and Note records. Mothernode does not expose a dedicated Users endpoint in the public API documentation. We resolve owner_id by probing the contact and customer records for created_by and modified_by fields, extracting email addresses where available, and matching against the Zoho destination org's User table. Users without a match enter a reconciliation queue for the customer's admin to provision in Zoho before record import.

Mothernode custom fields on Contacts, Customers, Leads, and Opportunities are identified during the schema audit by probing the API response payload for non-standard field names. We create matching custom fields in Zoho CRM before import using the appropriate field types (text, number, picklist, date, lookup). Zoho's field limits vary by edition: custom fields are not available in the Free edition, and Lookup and Formula fields are restricted in the Standard edition. We confirm the target edition during scoping and advise on field placement accordingly.

Project Folders are a Mothernode Enterprise-tier feature with no confirmed API availability in the public documentation. We probe the API during the extraction phase, but if the endpoint returns 403 or 404, we flag Project Folders as requiring a manual UI export. The customer schedules a parallel manual export step. Zoho CRM does not have a native Project Folder equivalent; if the customer needs project tracking, we recommend Zoho Projects as a separate product outside the CRM migration scope.

Job Center Modules handle real-time job tracking for manufacturing or service operations. This is a specialized object set not covered in the Mothernode public API reference. We flag Job records as requiring a manual export during the scoping call and document the recommended replacement in Zoho (Zoho Projects, Zoho FSM, or a custom module depending on the customer's use case). The customer decides whether to create a custom module in Zoho for job data or handle it in a separate system post-migration.