Migrate from Road Runner to HubSpot

Road Runner customer maps directly to HubSpot contact. The customer_id becomes Source_System_ID__c for traceability. Email, phone, and address properties transfer as direct field mappings. If Road Runner stores multiple contacts per customer, each row creates a separate HubSpot contact associated to the same company.

Road Runner customers with a business name or company flag create a HubSpot company alongside the contact. Company name, domain, industry, and employee count map to HubSpot company properties. The company_id becomes Source_System_ID__c on the company record. This ensures each business entity is linked to its corresponding contacts for unified reporting.

Road Runner jobs with a billed amount or estimated revenue convert to HubSpot deals. Job name becomes deal name; job total becomes deal amount; job status (Scheduled, In Progress, Completed, Cancelled) maps to a HubSpot deal pipeline stage. Jobs with no monetary value map to a custom object instead.

Road Runner jobs that carry no revenue (internal maintenance, site visits with no charge) land as a custom HubSpot object called Service_Record__c. The object stores job_id, scheduled_date, route_id, driver_id, and completion notes. It is associated to the contact and company via HubSpot's association API.

Road Runner invoices have no native HubSpot equivalent. We create an Invoice__c custom object with properties for invoice_id, invoice_number, total_amount, tax_amount, payment_status, and due_date. Each invoice is associated to the originating contact, company, and the related deal or service record in HubSpot.

Road Runner containers and equipment records map to a HubSpot Equipment__c custom object with container_id, container_type, capacity, current_status (Active, Rented, In-Transit, Retired), and current_location. Each equipment record associates to the contact and company it is assigned to in Road Runner.

Road Runner route assignments and driver IDs merge into HubSpot users. Each unique driver creates a HubSpot user record with their email and name. Their route_id and vehicle assignment store as custom properties on the user. Route-to-driver assignments are preserved as a custom property for reporting.

Road Runner tracks job status transitions with timestamps. These migrate as a custom datetime field on the deal or service record — Status_Changed_To__c plus a custom JSON blob of the full transition log for audit purposes. The JSON structure preserves each status change with its timestamp for detailed audit trails.

Road Runner custom properties per entity (customer, job, invoice, container) migrate as HubSpot custom properties. String types map directly; numeric types map to HubSpot number properties; date types map to HubSpot date properties. Pick-list values require value-by-value mapping if the property is a dropdown in Road Runner.

Road Runner file attachments on jobs, invoices, or equipment records download and re-upload to HubSpot Files. Files re-associate to the target contact, deal, or custom object record by ID. File size limits per HubSpot apply; files exceeding 25MB are flagged for manual handling.