Migrate from Kickserv to HubSpot

Kickserv stores customer name, email, phone, and company affiliation as flat fields. We split these into a HubSpot Contact record (personal properties) and a HubSpot Company record (business properties). The Kickserv customer-company relationship maps to the HubSpot contact-company association and ensures that each contact is linked to the correct company using the company ID property.

Kickserv business accounts map directly to HubSpot Companies. Company name, address, industry, phone, and website transfer as HubSpot Company properties. Kickserv parent-sub-account hierarchies translate to HubSpot's Parent Company field. We also preserve the original Kickserv account ID as a custom property on the HubSpot Company for audit trail purposes.

HubSpot has no native job object. Kickserv jobs migrate as HubSpot Deals holding revenue data (job amount, line items, close date) and HubSpot Tickets holding operational data (job status, assigned technician, location, scheduled date). Both records are cross-linked so context is preserved.

Kickserv job statuses (Scheduled, In Progress, Completed, Cancelled) map to HubSpot Deal stage values. We create a custom pick-list property (job_status) on the Deal to preserve the original Kickserv status label alongside HubSpot's native stage for reporting clarity and ensure that reporting dashboards reflect the exact terminology used in Kickserv.

Kickserv estimates carry line items (service description, quantity, unit price). These map to HubSpot Deal line items. Estimate status (Draft, Sent, Approved, Declined) migrates as a custom pick-list property on the Deal and as a Deal stage transition. We also preserve the original estimate ID as a custom field for reference.

Kickserv invoices carry total amount, payment status, and line items. In HubSpot, invoice financial data attaches as Deal line items. Payment status (Paid, Partial, Overdue) migrates as a custom property on the Deal since HubSpot lacks a native invoice object.

Kickserv employees who are technicians or dispatchers resolve by email match against HubSpot Users. Field technicians become HubSpot Sales Reps or Service Reps depending on HubSpot seat type. Admin staff without a HubSpot login are flagged as unmapped owners and assigned to a fallback HubSpot user.

Kickserv job scheduling events (job date, start time, technician assignment) map to HubSpot Meetings. Original scheduled time, assigned technician, and job association are preserved as meeting properties and linked to the associated Deal. These meetings also retain the original Kickserv event identifier for traceability.

Kickserv notes attached to jobs or customers migrate as HubSpot engagement notes on the associated Contact or Deal. Original timestamps and author are preserved. Rich-text formatting is converted to HubSpot's note format. We also ensure that any linked attachments are preserved and viewable within the HubSpot record.

Kickserv files attached to jobs (photos, signed documents, inspection reports) are downloaded and re-uploaded as HubSpot Files, linked to the associated Deal or Contact. File size limits apply (HubSpot's 25MB per file). Inline images in notes are extracted and rehosted.

Kickserv allows custom fields on Customers and Jobs. Each Kickserv custom field spawns a corresponding HubSpot custom contact or deal property. Field type is inferred from Kickserv's data type (text, number, date, pick-list) and created as the equivalent HubSpot property type before migration.

Kickserv tags on customers and jobs migrate as HubSpot contact or deal tokens. HubSpot tokens serve as a multi-value reference field equivalent to Kickserv tagging. Tags are migrated as flat comma-separated string properties or as HubSpot list memberships.

Kickserv's two-way QuickBooks sync stores accounting linkage IDs (QuickBooks customer ID, invoice ID, payment ID) as metadata. These have no HubSpot equivalent and are not migrated. The QuickBooks connection must be rebuilt using HubSpot's QuickBooks Online connector from the HubSpot App Marketplace.