Migrate from Uptick to HighLevel

Direct map. Uptick contacts (customers, site contacts) land as HighLevel Contacts with their full name, email, phone, and address fields preserved. Primary company link resolves via email match against HighLevel Users for owner assignment. All existing contact tags are also transferred, ensuring that segmentation and marketing lists remain intact after migration.

Direct map. Uptick company records (facilities, client businesses) map to HighLevel Companies. Company address, phone, and website transfer directly. Multiple Uptick sites for one company collapse to one HighLevel Company with site-specific details stored as custom fields or notes. This consolidation simplifies reporting and prevents duplicate company entries in the CRM.

Uptick assets (fire extinguishers, suppression systems, alarm panels) have no native HighLevel equivalent. We create a HighLevel Custom Object named 'Asset' with fields for asset type, location, serial number, install date, and certification status. Asset-to-site link uses a Custom Object association to the related HighLevel Company record.

Uptick work orders (inspection visits, repair jobs, maintenance calls) map to a HighLevel Custom Object named 'Work Order' with fields for work order number, type, status, scheduled date, technician assigned, and completion notes. The related Asset is linked via Custom Object association.

Uptick quotes with an approved status map to HighLevel Opportunities. The quote total becomes the Opportunity amount. Draft or expired quotes migrate as Opportunities with a 'Lost' or 'Abandoned' stage — your team decides the mapping rule before migration runs.

Quote line items (materials, labor, equipment) are merged into a HighLevel Opportunity as a custom multi-line text field or attached note. HighLevel does not have a native quote-line model, so the flattened line-item summary preserves the quote composition for reference.

Uptick asset type groupings (e.g., Wet Chemical Extinguisher, CO2 System, Fire Pump) map to a pick-list custom field on the Asset Custom Object in HighLevel. This preserves the certification-type classification for filtering and reporting. When you create new assets in HighLevel, the pick-list ensures consistent categorization and simplifies the generation of compliance reports by asset type.

Uptick technicians and staff map to HighLevel Users by email match. Uptick user roles (Admin, Technician, Viewer) do not map directly to HighLevel's permission groups — those require manual configuration in HighLevel's Access Controls after migration. After the migration, you should assign the appropriate team membership and permission sets to each user to reflect their original Uptick responsibilities.

Uptick inspection records linked to an asset migrate as a separate 'Inspection' Custom Object associated to the Asset. Each inspection captures date, result (pass/fail), technician, and notes. Historical inspection photos are re-hosted and linked. This structure enables you to run compliance queries across all assets, filter by inspection outcome, and schedule follow-up work orders directly from the inspection record.

Uptick files attached to assets, work orders, or quotes are downloaded and re-uploaded to HighLevel Files. Files are linked to the corresponding Contact, Company, or Custom Object record. File size limits follow HighLevel's storage policy. During re-upload, file naming conventions are preserved to help you locate the original documents within HighLevel's file manager.

Uptick tags applied to contacts, companies, or assets migrate as HighLevel Tags. Tag names are preserved exactly. Uptick tags that encode business logic (e.g., inspection due status) can be mapped to HighLevel Custom Fields if tags alone are insufficient for filtering.

Uptick job templates, recurring inspection schedules, and automated assignment rules do not migrate. We export Uptick's workflow configuration as a structured reference document that your HighLevel admin uses to rebuild equivalent automations in HighLevel's Workflow Builder. The reference includes trigger‑action mappings, condition examples, and suggested settings to streamline the rebuild process.