Migrate from Swivl Tech to HubSpot

Swivl Customer maps directly to HubSpot Contact. First name, last name, email, phone, and address fields migrate as HubSpot native contact properties. Swivl customer type (residential/commercial) maps as a custom pick-list property on Contact. The customer type classification has no HubSpot native equivalent, so it requires a custom property to be created before migration.

Swivl Service Location maps to HubSpot Company — name, address, and site-type properties migrate as native Company fields. Swivl N-to-N contact-to-location associations require a custom association property or junction approach since HubSpot supports one primary Company per Contact by default. The N-to-N relationship must be reconstructed using secondary association properties.

Swivl Job maps to HubSpot Deal. Service type, job status, job description, and technician assignment become custom properties on the Deal. The Swivl Job amount maps to Deal Amount. Scheduling datetime and appointment date migrate as custom datetime properties on the Deal record.

Swivl job status values (Scheduled, In Progress, Completed, Cancelled) map value-by-value to HubSpot Deal Stage pick-list values. Each Swivl status term must have a corresponding HubSpot pipeline stage name created or renamed before migration to ensure accurate status translation across the system.

Swivl technician records resolve to HubSpot Users by email match. Each technician assigned to a Swivl job becomes the Deal Owner in HubSpot. Unmatched technicians are flagged before migration so the team can invite them to HubSpot or assign a fallback owner.

Swivl Invoice has no HubSpot native equivalent. Invoice number, invoice date, due date, payment status, and total amount migrate as custom properties on the associated Deal. Invoice line items require a custom text field or a separate custom object depending on complexity.

Swivl estimates migrate as a custom property on the HubSpot Deal, since HubSpot Quotes are available only on Enterprise-tier plans and require a connected product catalog to function properly. Estimate status (Pending, Accepted, Rejected) becomes a custom pick-list property on the Deal for status tracking.

Swivl equipment records associated with a service location become either a HubSpot custom object with a lookup to Company, or custom text fields on the Company record storing asset name, model number, and asset type — the approach depends on the volume of equipment records per location.

Swivl customer notes migrate as HubSpot engagements of type Note, attached to the corresponding Contact record. Original timestamps and note authors are preserved throughout the migration. Rich-text formatting is retained where HubSpot's note format allows, maintaining the original note content and context for future reference.

Swivl file attachments on jobs, customers, or locations are downloaded and re-uploaded to HubSpot Files, then linked to the corresponding Contact, Company, or Deal record via file associations. HubSpot's 25MB per-file upload limit and storage quotas apply and are checked before migration to prevent oversized file rejections.

Any custom fields created in Swivl Tech require pre-creation as HubSpot custom properties before migration runs. Field type matching (text, number, date, pick-list) must be validated against HubSpot's supported property types to ensure proper data conversion. Custom field count directly impacts migration complexity and pricing estimates.