Migrate from MotionOps to HubSpot

MotionOps clients map to HubSpot contacts with company association. The client's primary service address becomes the HubSpot contact address; the business name and industry data map to the associated HubSpot company record. MotionOps supports N:N client-to-business associations, which we preserve using HubSpot's contact-to-company associations.

MotionOps stores client first name, last name, email, phone, and mobile on the client record. These map directly to HubSpot's firstname, lastname, email, phone, and mobilephone contact properties. Address fields map to HubSpot's address property group using street, city, state, postal code, country format.

MotionOps business/company name on a client maps to HubSpot company Name. Domain, industry, number of employees, and annual revenue map to their HubSpot company equivalents. Parent-company or franchise relationships in MotionOps become HubSpot company hierarchy via the parent company association field.

MotionOps jobs are the core operational record — work description, assigned technician, scheduled date, service type, and status. These map to a HubSpot deal with job-level data stored as custom properties on the deal (Job_Status__c, Scheduled_Date__c, Service_Type__c). Deal amount comes from the job's estimated or final revenue field. Jobs linked to clients map via the contact and company associations on the deal.

MotionOps job statuses (Scheduled, In Progress, Completed, Invoiced, Cancelled) have no direct HubSpot equivalent on a deal. We create a custom pick-list property on the HubSpot deal object and map each MotionOps status value to the corresponding HubSpot pick-list value by your specified rule.

MotionOps proposals and estimates map directly to HubSpot deals. Proposal name becomes deal name, proposal amount becomes deal amount, and proposal status (Draft, Sent, Accepted, Lost) maps to HubSpot deal pipeline stage values. The client linked to the proposal becomes the deal's primary contact and company association.

MotionOps proposal line items (service description, quantity, unit price, total) have no native HubSpot equivalent. We map line items to a series of custom properties on the deal (Line_Item_1_Service__c, Line_Item_1_Qty__c, etc.) or store the full line-item JSON in a custom long-text field for reference — your team rebuilds line items as HubSpot product line items post-migration.

MotionOps invoices with payment status, amount, and date have no native HubSpot invoice object. We create custom properties on the associated deal (Invoice_Number__c, Invoice_Date__c, Payment_Status__c, Amount_Paid__c) to preserve invoice history. Payment records and QuickBooks sync links require re-establishment in HubSpot Payments or your accounting integration.

MotionOps employee records with technician assignment become HubSpot users. We match each MotionOps employee email to an existing HubSpot user — matched users become deal owners in HubSpot. Unmatched employees are flagged as inactive users or fallback owners. Role and permission data does not migrate; HubSpot's role system is destination-side configuration.

MotionOps scheduled appointments with technician assignment and time window map to HubSpot meetings (for scheduled time blocks) and calls (for in-field service visits). Original start/end timestamps, technician as owner, and client association are all preserved on the HubSpot activity record to maintain scheduling history and service documentation.

MotionOps time entries linked to jobs have no native HubSpot equivalent. We create custom numeric properties on the deal (Total_Hours__c, Time_Entry_Count__c) and store time entry details as a custom long-text field or JSON blob for audit reference. Payroll prep data requires HubSpot + a separate payroll tool integration.

MotionOps custom fields on job records (certification type, service-area code, special instructions, routing priority) become HubSpot custom properties on the deal object. Field type mapping is type-aware: select fields become pick-list properties, text fields become string properties, number fields become number properties, and date fields become date properties.

MotionOps custom client properties (preferred payment method, billing terms, customer tier, referral source) map to HubSpot custom properties on the contact or company object. HubSpot's property type constraints apply — for example, a MotionOps multi-select property maps to a HubSpot checkbox or multiple single-value properties depending on the data shape.

MotionOps notes on clients, jobs, or proposals all migrate to HubSpot notes associated with the corresponding contact, company, or deal record. File attachments migrate to HubSpot Files. The original author name and create timestamp are preserved as note metadata for audit trail continuity and accountability tracking.