Migrate from Method:Field Services to HubSpot

Method contacts map directly to HubSpot contacts. Name, email, phone, address, and custom properties migrate as HubSpot properties. Primary company link resolves via the Company→Account map before contact migration runs, ensuring that associatedcompanyid associations are valid at load time. Any duplicate email addresses are flagged for resolution before the contact migration pass begins.

Method companies map to HubSpot companies (accounts). Company name, domain, industry, employee count, and address fields migrate as HubSpot company properties. Parent-company hierarchies map to HubSpot's parent-company association, preserving organizational structures. Companies without a domain are matched by name to prevent duplicates in HubSpot.

Work orders are the core migration challenge due to no native HubSpot equivalent. Method's work order status, type, priority, description, and line items translate to a HubSpot custom object 'Work Order' linked to Contact and Company. Alternatively, open work orders route to HubSpot Deals for revenue-tracking; closed work orders route to a custom object for historical reference. The routing decision must be confirmed before migration begins.

Method work order statuses (e.g., Scheduled, In Progress, Completed, Cancelled) map to HubSpot deal stages or a custom pick-list property on the Work Order custom object. Explicit value-by-value mapping is required because status labels differ between platforms. We capture the complete status inventory from Method before creating the mapping table.

Method technicians are users in the source system and migrate as HubSpot users (for owner assignment) with a corresponding contact record for customer-facing communication scenarios. Role-based pack permissions (Field Crew Pack) map to HubSpot's Service Hub seat assignment. Technicians without HubSpot user accounts are flagged and can be assigned to a fallback owner or have accounts provisioned before migration.

Method dispatchers are user accounts that migrate as HubSpot users with appropriate Sales or Service Hub roles. Dispatch permissions (Contact Management, Sales Transactions, Work Orders) map to HubSpot object-level permissions. Pack-based permission sets require manual recreation in HubSpot's permission model since the structures differ between platforms.

Method estimates and quotes map to HubSpot deals with associated line items. The estimate amount maps to deal amount; estimate status (Accepted, Declined, Pending) maps to a custom property or deal stage. Accepted estimates create open deals in HubSpot at migration time, preserving the estimate-to-opportunity pipeline continuity. Declined estimates can map to a closed-lost stage or custom stage per team preference.

Method's time tracking entries (hours worked per work order per technician) map to a custom 'Time Entry' object linked to the work order and technician contact. Original timestamps and duration are preserved as custom properties on the time entry record. This enables reporting on technician utilization and job duration after migration without relying on Method data.

Method invoices sync from QuickBooks and map to HubSpot deals with invoice status tracked as a custom property. QuickBooks invoice numbers are preserved as a custom text field for cross-reference during accounting reconciliation. Full QuickBooks invoice data, payment history, and QuickBooks-specific transaction IDs require a separate export from QuickBooks since the sync connection does not transfer.

Method custom fields on contacts, companies, and work orders migrate as HubSpot custom properties. Method custom tables (created via Method's development platform) migrate as HubSpot custom objects. We flag any custom field that uses Method-specific data types (formula fields, linked records, custom pick-lists) for manual type-mapping confirmation before the migration runs.

Work order attachments (photos, documents, e-signatures) download from Method's storage and re-upload to HubSpot Files linked to the corresponding deal or custom Work Order object. File size limits apply per HubSpot's upload restrictions; inline images embedded in notes are extracted and rehosted as separate file attachments. All attachments maintain their association to the parent work order record in HubSpot.