Migrate from Mothernode to Pipedrive

Mothernode Customer records map to Pipedrive Organization. The Customer company name becomes the Organization name; billing address fields map to Organization address fields. Customer_id is preserved as a reference field for deduplication. Organizations are imported before Persons so that the Organization lookup is available at Contact insert time.

Mothernode Contact records map to Pipedrive Person. Each Contact is matched against existing Organizations using domain extraction from the Contact email address. If a matching Organization exists, the Person-Organization link is established at import. If no matching Organization is found, the Organization is created from the Contact's company field before Person import.

Mothernode Lead records (extracted using the record-type indicator from the shared leads-and-opportunities endpoint) map to Pipedrive Lead. The Lead status value maps to Pipedrive Lead Status. Any lead score or qualification field migrates as a custom field on the Pipedrive Lead object.

Mothernode Opportunity records (extracted using the record-type indicator from the shared endpoint) map to Pipedrive Deal. Opportunity name, value, stage, expected close date, and owner_id transfer directly. The Mothernode pipeline stage name maps to a Pipedrive Pipeline stage that we configure during schema setup.

Each Mothernode pipeline stage value is extracted from the Opportunity records and mapped to a corresponding Pipedrive Pipeline stage. We create the Pipedrive Pipeline and its stages during the configuration phase, matching stage names and probability percentages from the source data. If the customer uses multiple Mothernode pipelines, we create multiple Pipedrive Pipelines.

Mothernode Notes map to Pipedrive Activity Notes. Note content, the associated entity ID (Contact, Customer, or Opportunity reference), timestamp, and author attribution transfer. Notes are written after the parent Person and Deal records exist so that the activity link is satisfied.

Mothernode Event records map to Pipedrive Activity records of type Event. Event type, start and end time, duration, location, and associated Contact or Opportunity link transfer. Calendar-bound events are mapped to the Pipedrive Activity with the correct date and time preserved from the source.

Mothernode Invoices migrate as Pipedrive Deal fields or as a custom Invoice object depending on the customer's Pipedrive plan and preference. Line items, totals, status, and customer reference transfer. We flag any Invoice PDF attachments for manual transfer if the API response does not include a downloadable URL.

Mothernode owner_id references on Lead, Opportunity, Event, and Note records are resolved via email match against Pipedrive Users. We extract every distinct owner from the source data during scoping. Any owner without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

Mothernode custom fields on Contacts, Customers, Leads, and Opportunities are probed during the extraction phase by inspecting the full API response schema. Discovered custom fields are created in Pipedrive as equivalent typed fields (text, number, date, picklist, or checkbox) before the data phase begins. Custom field values transfer as part of the parent object import.

Project Folders are an Enterprise-tier feature in Mothernode with unconfirmed API availability. We probe the endpoint during extraction; if it returns 403 or 404, we flag Project Folders for manual UI export and deliver a written inventory of the records requiring manual transfer. This step is scoped and priced separately during discovery.

Job Center Modules handle real-time job tracking and are gated behind Mothernode Enterprise with no confirmed public API endpoint. We flag Job records as requiring a manual export step and deliver a structured CSV template for the customer's operations team to populate. This data is migrated as a custom object or linked records in Pipedrive depending on the customer's workflow requirements.