Migrate your Mothernode data

Contacts are accessible via GET https://api.mothernode.com/contacts. The platform supports importing contacts from multiple external sources. We map Contact fields 1:1 via the documented endpoint, preserving standard fields and any custom contact-level properties included in the API payload.

Customers are accessible via GET https://api.mothernode.com/customers. The response returns a customers array keyed by customer_id. We extract the full customer record and cross-reference with associated Contacts and Invoices using the relationship IDs in the payload.

Leads and Opportunities are co-located under a single API endpoint: https://api.mothernode.com/leads-and-opportunities. The platform distinguishes Leads from Opportunities semantically (documented in their FAQ). We preserve the full Lead record including lead status, source, and assignment fields during migration.

Opportunities share the same API endpoint as Leads. We separate Opportunities from Leads during import scoping using the record type indicator in the API response and map them to the destination CRM's equivalent Deals or Opportunities object.

Notes and Events are accessible via the Notes/Events API endpoint. We extract note content, associated entity IDs, timestamps, and author attribution. Notes are mapped to Comments or Activity Notes in the destination system based on the target's object model.

Events follow the same API endpoint as Notes. We preserve event type, date/time, duration, and the associated Contact or Opportunity link. Calendar-bound events are mapped to the destination's Activities or Tasks object.

Invoices are accessible via the Invoices API. We extract line items, totals, status, and customer reference. Invoice records are migrated to the destination's Invoice or Billing object; we flag any orphaned invoices (missing customer link) for manual resolution.

User and Owner assignment is referenced in Lead, Opportunity, and Event records via owner_id. The Mothernode API does not expose a dedicated Users endpoint in the public documentation. We map owner_id to the destination's User lookup field but require the customer to provide a user cross-reference table if source owner names differ from the destination.

Custom fields on Contacts, Customers, Leads, and Opportunities are not explicitly documented in the API reference. We probe the API response schema during the extraction phase to identify any non-standard fields present in the customer's data. Any custom fields found are migrated as custom properties in the destination, with a field-mapping review scheduled before import.

Opportunity records include a pipeline stage value that governs workflow state. The stage names and count vary by Mothernode configuration. We extract stage names from the source data and create a stage-mapping table before writing to the destination pipeline object.

Project Folders are an Enterprise-tier feature documented on the Mothernode marketing site. API availability for Project Folders is not confirmed in the public API documentation. We attempt to extract Project Folder data via the API; if the endpoint returns a 404 or 403, we flag this as a manual-export item and document the steps to export from the UI.

Job Center Modules handle real-time job tracking for manufacturing or service operations. This is a specialized object set not covered in the public API reference. We flag Job records as requiring a manual export or custom API investigation during the scoping call.

Mothernode supports email marketing and follow-up sequences. The API does not expose campaign or sequence records in the documented endpoints. We migrate contact-level campaign association data where present in the Contact or Lead record; campaign-level configuration requires manual capture.