Migrate from Mothernode to Salesforce Sales Cloud

Mothernode Contact records map directly to Salesforce Contact. We extract the full Contact payload including name fields, email, phone, address, and owner_id. The Contact's associated Customer or Account reference is resolved during the Account import phase. If the Mothernode Contact has no parent Customer, we create a standalone Account with the Contact's company name to satisfy Salesforce's Contact-Account relationship.

Mothernode Customers map to Salesforce Account. Mothernode's multi-entity model treats Customers as top-level organizational records distinct from Contacts, which mirrors Salesforce's Account model more closely than its Contact model. The Customer name becomes Account Name, and Customer custom fields probe the API response schema for any non-standard fields to map as custom Account fields.

Mothernode Leads are returned from the shared leads-and-opportunities endpoint with a record-type field indicating Lead status. We filter by this field during extraction and route Lead records to Salesforce Lead. Lead status, source, and score fields map to Salesforce LeadStatus, LeadSource, and custom rating or scoring fields respectively. Any converted Leads in Mothernode that point to existing Opportunities are flagged for a pre-import review call.

Mothernode Opportunities are also returned from the shared leads-and-opportunities endpoint with a record-type field indicating Opportunity status. We filter by this field and route Opportunity records to Salesforce Opportunity, resolving the parent AccountId by matching the associated Customer record. Stage, amount, close date, and owner_id migrate directly.

Mothernode stage names vary by customer configuration and are stored as strings in the opportunity record. We extract distinct stage names from the source data, create a Salesforce Sales Process with matching StageProbability values, and map each stage to the correct StageName. If the customer uses multiple pipelines, we create corresponding Record Types on Opportunity.

Mothernode Notes are accessible via the Notes/Events API endpoint. We extract note body, associated entity ID, timestamp, and author attribution. Notes migrate to Salesforce Note records linked via ContentDocumentLink to the parent Contact, Account, or Opportunity. Rich text formatting is preserved where the API returns it.

Mothernode Events share the Notes/Events API endpoint. We preserve event type, start and end datetime, duration, and the associated Contact or Opportunity link. Events map to Salesforce Event with ActivityDateTime, Location, and WhoId linking to the resolved Contact or Lead.

Mothernode Invoices migrate to Salesforce Invoice if the destination org includes Salesforce Billing or a billing app from the AppExchange. If not, we map Invoice to a custom Invoice object with line items, totals, status, and customer reference. We flag any post-migration billing workflow requirements during scoping.

Mothernode does not expose a dedicated Users endpoint in the public API documentation. Owner references appear as owner_id fields on Contact, Lead, Opportunity, and Event records. We resolve owner_id by matching email addresses against the destination Salesforce org's User table. Any owner without a matching User goes to a reconciliation queue for the admin to provision before record import resumes.

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 field names and values. We pre-create matching custom fields in Salesforce with appropriate types before migration and map them during the transform phase.

Project Folders are an Enterprise-tier feature with no confirmed API coverage. We probe the API endpoint during extraction; if it returns 403 or 404, we flag Project Folders as requiring a manual UI export. The customer schedules a parallel manual export step. We do not attempt to migrate project folder relationships as code because there is no documented endpoint to extract them.

Job Center Modules are specialized for manufacturing or service operations and are not covered in the public API reference. We flag Job records as requiring a manual export and handoff document for the customer's admin. If the customer has an active Job Center dependency, we discuss custom object migration as a separate scoping engagement before migration begins.

Mothernode's email marketing and follow-up sequences are not exposed in the documented API endpoints. We extract contact-level campaign association data where available, but sequences, email templates, and campaign automation cannot be migrated programmatically. We deliver a written inventory of any detected sequences for the admin to rebuild in Salesforce Flow or a sales engagement tool.