Migrate from Uptick to HubSpot

Uptick Accounts map directly to HubSpot Companies. Account name becomes Company name, primary contact email populates the primary contact on the Company. Billing and service addresses migrate to the HubSpot address properties; phone and website URL map to the Company phone and domain fields. The original Uptick account ID is stored as a custom Source_System_ID__c field for later reconciliation.

Each Uptick Account's primary contact migrates as a HubSpot Contact linked to the corresponding Company via the primary-company association. Contact name, email, phone, and job title map directly. Additional named contacts on an account become additional HubSpot Contacts with the same CompanyId.

Uptick Locations linked to an Account carry an address and a location name. If an account has multiple service locations, each location's address migrates as an address property set on the Company record, with the location name stored in a custom text field for reference.

Uptick Assets require a HubSpot custom object (Professional/Enterprise) because HubSpot has no native asset-equivalent. Each Asset migrates as an Asset__c record with a lookup to the parent Company and, optionally, to the related Contact who owns the asset on site.

Uptick Asset Types such as Fire Extinguisher, Hose Reel, and Emergency Light are mapped to a custom pick‑list field named Asset__c.Asset_Type__c. All distinct type values present in the Uptick instance are extracted, pre‑loaded as pick‑list options in HubSpot, and validated before the migration run so every asset row receives a matching value.

The Uptick Variant attribute (e.g., 2.5kg CO2, 9kg Water) transfers into Asset__c.Variant__c as a free‑text field. If Uptick stores variant options in a controlled pick‑list, we replicate each option as a text entry; any special characters or blank values are preserved as‑is. This ensures the variant data is searchable in HubSpot without loss of formatting.

Uptick Work Orders map to HubSpot Tickets with a rich set of custom fields: service type, scheduled date, completed date, assigned technician, job status, labour hours, and materials used. The Ticket is linked to the Asset__c record and the Company record so the full service context is visible in one place.

Uptick work order statuses such as Scheduled, In Progress, Completed, and On Hold are matched one‑to‑one to HubSpot Ticket pipeline stages. We create a Ticket pipeline that replicates the Uptick status sequence, populating each stage with the corresponding label. This configuration is validated against the source data so every Ticket lands in the correct pipeline step during migration.

Uptick Quotes convert to HubSpot Deals, preserving the quote number as the Deal name and the total amount as the Deal amount. Each line item—products, labour, or subcontracted services—becomes a HubSpot Product and a Line Item attached to the Deal, retaining quantity, unit price, and any custom cost fields. The quote status (Draft, Sent, Accepted) aligns with a Deal stage via value mapping to reflect the sales pipeline stage.

Uptick Quote product rows (Name, Supplier Cost, Estimated Sell Price, Unit of Measure) map to HubSpot Line Items on the Deal. Sell price maps directly; cost price requires a custom field on the Line Item since HubSpot records only unit price by default.

Uptick Products—materials, labour rates, equipment, and subcontracted items—are created as HubSpot Products. The Uptick product type codes (M, R, E, S, X) are transferred into a custom pick‑list field on the Product record for classification. Supplier name and any reference numbers are stored as text properties on the Product, enabling downstream reporting and purchasing workflows.

Uptick asset hierarchies such as a building floor containing child detectors are represented as self‑lookups on the Asset__c custom object. Each parent asset is loaded before its children, allowing the Parent_Asset__c field to resolve correctly. Orphaned or circular references are flagged for manual resolution before the migration run, ensuring a clean hierarchical structure in HubSpot.

Uptick technicians and staff members resolve by email match against HubSpot users. If a technician has no HubSpot user account, their name and email are stored as a custom Contact property on the related Ticket so the assignment is preserved even without a full HubSpot login.

Uptick attachments on work orders, assets, and quotes — including PDF inspection reports and photos — are downloaded and re-uploaded to HubSpot Files associated with the relevant Company or Asset__c record. File size limits (25MB per file in HubSpot) are enforced during the re-upload step.

Uptick scheduling rules, compliance reminder triggers, and asset-service-due workflows have no HubSpot equivalent and cannot be migrated. We export Uptick workflow definitions as a reference document for your HubSpot admin to rebuild using HubSpot Workflows, and we include a rebuild guide as part of the migration package.