Migrate from Mothernode to HubSpot

Mothernode Customer records map directly to HubSpot Company records. Standard fields including company name, domain, address, phone number, city, state, country, industry, number of employees, and annual revenue transfer as HubSpot standard properties. Mothernode customers that lack an explicit domain receive a placeholder domain (such as 'no-domain-provided.com') to satisfy HubSpot's duplicate-detection algorithm and prevent duplicate company records during migration.

Mothernode Contact maps to HubSpot Contact. Email, first name, last name, phone, job title, and address fields map directly. HubSpot requires each contact to have an associated HubSpot Company — we match contacts to companies by email domain first, then by explicit company_id field in the source record.

Mothernode Lead records have no direct HubSpot equivalent — they are contacts in HubSpot's model. We map each Lead to a HubSpot Contact and set lifecycle_stage to 'lead' (or 'subscriber' if the source has an opt-in flag). Lead source and status fields migrate as HubSpot custom properties if no standard HubSpot field matches.

Mothernode Opportunities map to HubSpot Deals. Deal name, amount, close date, and owner transfer directly. Mothernode's opportunity status (open, won, lost) maps to HubSpot pipeline stages — we map each distinct Mothernode status value to a corresponding HubSpot stage name during the planning phase before migration runs.

Mothernode notes map to HubSpot engagement notes. Subject line becomes the note title, body text transfers as-is, timestamps and owner are preserved. Notes are associated to the parent contact or company record using the record ID stored in the source note's linked record field.

Mothernode events map to HubSpot meetings. Event title, start time, end time, location, and description transfer. HubSpot meetings require an organizer and optional attendees — we resolve the owner as organizer and populate attendee emails from the event's linked contact list. All-day events receive a flag in HubSpot's start/end datetime fields.

Mothernode custom fields on contacts need explicit HubSpot custom property creation before migration. We audit all custom field names and data types from the Mothernode API, propose HubSpot property types, and create them in your HubSpot portal during the planning phase. The field names in HubSpot can match Mothernode's or be renamed per your naming convention.

Mothernode custom fields on opportunities migrate to HubSpot deal custom properties. Fields such as 'probability_override', 'competitor', 'next_step', 'decision_timeline', or 'purchase_process' that have no direct HubSpot standard equivalent become deal-level custom properties created during the planning phase. We audit each custom field from the Mothernode API, map it to an appropriate HubSpot property type, preserve all original field values, and maintain data type integrity throughout the migration.

Mothernode quotation records carry product line items, quantities, unit prices, and totals. HubSpot has no native quotation object — we map quotation data to HubSpot Deals with line items as a reference structure. The commercial workflow (quote generation, approvals, e-signature) needs HubSpot's connected quoting tool or a third-party app post-migration.

Mothernode sequences and email campaigns do not migrate. HubSpot has its own sequence tool (Sales Hub Professional+) with enrollment triggers and step delays. We export your Mothernode sequence definitions as a structured CSV so your HubSpot admin can rebuild them as HubSpot sequences with appropriate enrollment criteria.

Mothernode invoice records (linked to opportunities and customers) have no direct HubSpot equivalent. Invoices in HubSpot require the Payments product or a third-party integration. We preserve invoice data as a reference file and document the mapping so your billing team can re-enter or integrate a QuickBooks/NetSuite connection in HubSpot.

Mothernode owner IDs resolve to HubSpot users by email address lookup. If a Mothernode owner has no matching HubSpot user email, we flag the record for your team to either create the HubSpot user first or reassign to a fallback owner before migration. All opportunity and contact owner assignments resolve using this email-match logic.