Migrate from Aidoo Mobile to HubSpot

Aidoo customer records map to HubSpot companies. Customer name becomes Company Name, domain maps to Website, and industry maps via value-mapping against HubSpot's default industry pick-list. Records without a company name default to the contact's name stored in the HubSpot contact record.

Named contacts in Aidoo become HubSpot contacts. First name, last name, email, phone, job title, and address fields map directly. If the Aidoo contact lacks an email address, we create a stub contact and flag it for your team to complete before workflows activate.

Aidoo work orders map to HubSpot deals. The work order title and description map to the deal name; amount maps to deal amount if Aidoo stores service revenue. Aidoo work order status (Open, In Progress, Completed, Invoiced) maps to HubSpot dealstage values through a value-by-value mapping table. Priority level, scheduled date, and assigned technician migrate as custom deal fields.

Aidoo's FSM status values must be mapped to HubSpot deal stages one-by-one. We create a mapping table — for example, Aidoo 'Open' maps to HubSpot 'Appointment Scheduled', 'In Progress' maps to 'Qualified to Buy', and 'Completed' maps to 'Closed Won' — with your confirmation before migration runs. Unmapped statuses default to the first stage in the pipeline.

Aidoo work order priority (Low, Medium, High, Critical) has no native HubSpot deal field. We create a custom pick-list field (Work_Order_Priority__c) on the Deal object and map Aidoo priority values exactly as they appear in the source system. This field enables filtering and reporting on priority across all migrated work orders.

The technician appointment date from Aidoo migrates to a custom datetime field (Scheduled_Date__c) on the HubSpot deal. HubSpot's native Closedate field is reserved for deal close dates, so the Aidoo scheduling date requires a separate custom field for field-service reporting.

Aidoo technicians are mapped to HubSpot contacts with a custom property (Technician_Role__c) set to 'Field Technician'. Certification and skill-set fields from Aidoo migrate to custom contact properties. Technicians are matched to HubSpot users by email for deal ownership resolution and workflow assignment.

Aidoo asset records have no direct HubSpot equivalent. We create a custom object (Asset__c) with fields for asset name, asset type, serial number, location, and parent company lookup. Assets are linked to HubSpot companies and to the work-order deals that serviced them.

Aidoo asset latitude and longitude coordinates migrate to custom number fields on the Asset__c custom object. HubSpot does not have native geo-positioning; these values are preserved as reference fields for use in third-party map integrations post-migration to maintain location context.

Aidoo work order notes and technician comments migrate as HubSpot Notes attached to the corresponding deal record. Original timestamps and the creating technician's contact record are preserved as note metadata for full audit trail and traceability.

Completed work order records with timestamps and outcomes migrate as HubSpot engagements (logged calls or notes) on the deal and contact records. The Aidoo outcome status maps to the engagement subject line for quick reporting filtering and historical reference in the customer timeline.

Aidoo captures customer signatures on completed work orders. These images are exported as files and re-hosted securely; the URL is stored in a custom text field (Customer_Signature_URL__c) on the HubSpot deal for compliance, audit, and proof-of-service purposes.