Migrate from Aidoo Mobile to HighLevel

Direct map. Aidoo Mobile contacts carry name, email, phone, and address fields that map directly to HighLevel's Contact object. Owner resolution happens via email match against HighLevel users. Contacts without an associated company in Aidoo Mobile land as standalone HighLevel contacts without a CompanyId link.

Direct map. Company name, domain, industry, employee count, and address fields map to HighLevel's Company object. Company hierarchies (parent/child) are not natively supported in HighLevel's Company model — parent-child relationships collapse to individual company records with a custom field for reference.

Aidoo Mobile's Job object is the core of the FSM model. HighLevel has no native Jobs equivalent — each job migrates as a HighLevel Opportunity with custom fields appended to capture job-specific context: job status, priority, job type, scheduled start and end, assigned technician, and service address. The Opportunity pipeline in HighLevel replaces Aidoo Mobile's job status workflow.

Aidoo Mobile job status values (Scheduled, In Progress, On Hold, Completed, Cancelled) are mapped to HighLevel custom picklist values. Probability weighting and pipeline stage assignments are applied per status value during migration so forecasting reflects the source job lifecycle. These mappings are stored in the migration configuration file, allowing you to review and adjust stage-to-status assignments before final data load.

Aidoo Mobile stores job type as a service category field. HighLevel has no native job-type field. We create a custom pick-list field (Job_Type__c) on the Opportunity object and populate it with the source values. If Aidoo Mobile uses custom job type values, those are preserved verbatim in the pick-list options.

Aidoo Mobile links jobs to field technicians by user ID. HighLevel does not have a technician-assignment field on Opportunities. The technician name or ID is stored as a custom text field (Assigned_Technician__c) on the Opportunity. Where a HighLevel user matches by email, we also link OwnerId so the opportunity surfaces under the correct user's dashboard.

Aidoo Mobile job scheduling dates map to two custom datetime fields on the HighLevel Opportunity. HighLevel's native Opportunity CloseDate is reserved for the deal close date — it does not serve the same purpose as a job scheduling window, so a separate pair of custom fields preserves the original scheduling context.

Aidoo Mobile's Equipment object has no native HighLevel equivalent. We create a HighLevel Custom Object named Equipment and populate it with serial number, model, manufacturer, warranty expiry, and service history fields. The custom object is then linked to related Opportunities via a custom relationship field so the asset context travels with the job.

Aidoo Mobile allows each job to be associated with multiple equipment records. HighLevel Custom Objects support relationship fields. We create a junction-style Custom Object (Job_Equipment__c) that links the Equipment custom object to Opportunity records, preserving the many-to-many relationship that Aidoo Mobile supports natively.

Aidoo Mobile job cost or estimated value maps directly to the HighLevel Opportunity Amount field. If the source stores both a cost and a quoted amount, the job cost migrates as the Opportunity Amount and a custom field (Job_Cost__c) preserves the cost figure separately.

Aidoo Mobile job notes and descriptions migrate to HighLevel notes attached to the relevant Contact or Opportunity record. Notes longer than 255 characters are stored as multi-line text in the HighLevel note body. Job-level notes attach to the Opportunity; client-facing notes attach to the Contact.

The original Aidoo Mobile record ID is stored as a custom field on every migrated object (e.g., Source_Aidoo_ID__c) for traceability and delta-run deduplication. This prevents duplicate records on re-runs and allows your team to reference the original Aidoo Mobile ID in HighLevel reports.