Migrate from Mobile Service App to HighLevel

All standard contact fields (name, email, phone, address, job title) map directly to HighLevel Contacts. Owner resolution uses email match against HighLevel user accounts — unmatched owners are flagged before migration commits for manual assignment review. A pre-migration validation report identifies any email discrepancies that require resolution before the data transfer begins.

HighLevel Companies store business name, domain, industry, employee count, and annual revenue. Multi-company associations in the source collapse to a primary Company lookup on the Contact record, with secondary companies surfaced as tags for reference and segmentation purposes.

Service tickets and deal records map to HighLevel Opportunities using the same record identifiers. Pipeline stages in the source map directly to HighLevel Pipeline stage values — each pipeline becomes a named HighLevel Pipeline with its own configured stage sequence for deal progression tracking.

Source pipeline definitions translate to HighLevel Pipelines using a one-to-one mapping. Stage names map value-by-value to HighLevel stage pick-list values within the corresponding destination pipeline. Stage-enter timestamps are preserved as custom datetime fields to maintain historical stage-transition records.

HighLevel does not have a native multi-value tag field equivalent to the source platform. We create a Tags__c custom field on Contact and populate it with comma-separated source tags to preserve all label associations. Smart Lists in HighLevel can then filter on this field after migration completes.

Phone calls and emails map to HighLevel Tasks with Type='Call' or Type='Email' respectively. Meetings and appointments map to HighLevel Events for calendar integration. Original timestamps, assigned owners, and parent-contact links are all preserved during the migration process.

Text notes migrate as HighLevel Notes attached to the parent Contact or Opportunity record. File attachments are re-uploaded to HighLevel Files and linked to the parent record for complete attachment traceability. File size limits are enforced per HighLevel's storage configuration during the migration.

Custom objects from the source map one-to-one to HighLevel Custom Objects for complete data preservation. We create the destination custom object schema first via the HighLevel API, then migrate all records including all custom field data. Relationships between custom objects use HighLevel's lookup field system to maintain data integrity.

Source user records are matched to HighLevel users by email address for ownership continuity. If a source owner has no corresponding HighLevel user account, records are assigned to a designated fallback owner and flagged for review by the admin team. Active user count in HighLevel determines the required license tier post-migration.

The original record ID from the Mobile Service App platform is stored as a custom text field on each migrated record. This enables delta-run de-duplication to prevent duplicates, rollback identification for error recovery, and full audit traceability if records need to be reconciled post-migration.

HighLevel sets CreatedDate at migration time rather than preserving the original source timestamp. To preserve reporting continuity for records with historical create dates, we store the original source creation timestamp as a custom datetime field so historical age and tenure reporting remains accurate and valid.

Automation logic from the source cannot be transferred to HighLevel's Workflow engine due to platform-specific differences. We export all workflow definitions as JSON reference documents delivered alongside the migration package. Your HighLevel admin can rebuild triggers and actions in the HighLevel Workflow Builder using the exported definitions as a logical guide.