Migrate from Mothernode to Freshsales

Mothernode Contacts map directly to Freshsales Contact records. We extract via GET https://api.mothernode.com/contacts using paginated offset reads, preserving first_name, last_name, email, phone, address fields, and any custom field values discovered in the response schema. The primary email address becomes the dedupe key during Freshsales import to prevent duplicate Contact creation.

Mothernode Customers map to Freshsales Account records. Mothernode's customer_id becomes a reference stored in a custom Account field for reconciliation. The Customer name maps to Account Name, and any associated contact links are resolved after both Contact and Account imports complete. We probe the API response during extraction to capture any customer-specific fields not documented in the public API reference.

Mothernode Leads migrate to Freshsales Lead records. Both Lead and Opportunity records in Mothernode return from the same API endpoint (https://api.mothernode.com/leads-and-opportunities) with a record type indicator in the payload. We separate Leads from Opportunities using this indicator before writing to Freshsales. Lead status and source fields map to Freshsales standard Lead fields. We preserve any lead score value from Mothernode in a custom field for review after migration.

Mothernode Opportunities map to Freshsales Deal records. The shared leads-and-opportunities API endpoint requires the record type split before import. Opportunity amount, stage, expected close date, and owner_id transfer to Freshsales Deal fields. Pipeline stage names from Mothernode are extracted and mapped to Freshsales pipeline stages; if the stage names do not match an existing Freshsales pipeline, we create one during the schema configuration phase.

Mothernode Notes and Events share an API endpoint and migrate to Freshsales Notes attached to the parent record. We extract note body, associated entity IDs (contact_id or opportunity_id), timestamps, and author attribution. Notes are linked to the parent Contact, Account, or Deal in Freshsales via the appropriate ID resolution after the parent records exist in the destination.

Mothernode Events (calendar-bound entries) migrate to Freshsales Task records with event type, date/time, duration, and associated Contact or Opportunity link preserved. The original timestamp is carried into the Freshsales Activity Date to maintain the chronological sequence in the Contact or Deal timeline.

Mothernode Invoice records contain line items, totals, and status. Freshsales does not have a native Invoice object in the standard CRM tier; invoices map to Deals with custom fields capturing invoice_number, invoice_total, and invoice_status. We flag any invoice records with an associated Customer and merge them into the corresponding Account or Deal context in Freshsales. If the customer requires a full invoicing module, Freshsales Suite includes billing capabilities as an add-on.

Mothernode does not expose a dedicated Users endpoint in the public API. Owner IDs referenced in Lead, Opportunity, Event, and Note records are resolved by matching against the source payload's owner attribution. We create a mapping table of Mothernode owner_id to Freshsales User records based on email where available. Any owner without a matching Freshsales User is held in a reconciliation queue for the customer's admin to provision before record import.

Custom fields on Contacts, Customers, Leads, and Opportunities are not explicitly documented in the Mothernode API reference. We probe the API response schema during the extraction phase to identify any non-standard fields present in the customer's data. These are then recreated as custom fields in Freshsales with appropriate field types before migration begins. Field type mapping follows Freshsales type constraints (text, number, picklist, date, checkbox, etc.).