Migrate from WORKetc to HubSpot

WORKetc contacts migrate as HubSpot contacts using direct field mapping. Name, email, phone, job title, and address fields map directly to their HubSpot equivalents. The WORKetc contact type field (client vs. lead) determines whether lifecycle_stage on the HubSpot contact is set to 'customer' for clients or left blank for leads that require follow-up scoring. Owner assignments resolve via email match to HubSpot users.

WORKetc companies map to HubSpot companies with direct field mapping for name, domain/website, industry, employee count, and annual revenue. WORKetc parent-child company hierarchies map via HubSpot's parent company association using the same relationship logic, preserving organizational structure in the target CRM.

WORKetc leads (status: New, Contacted, Qualified) merge into HubSpot deals on the default pipeline. Lead status and priority values map to HubSpot deal stage and a custom deal priority field. The original lead creation date is preserved as a custom datetime property.

WORKetc deals (status: Open, Won, Lost, Dead) map directly to HubSpot deals. Deal name, amount, stage, close date, owner, and associated contacts migrate. WORKetc deal stage names map value-by-value to HubSpot pipeline stages, with original stage-entered timestamps preserved as custom datetime fields.

WORKetc invoices have no HubSpot native equivalent. Invoice number, total amount, status, and date migrate as custom properties on the linked HubSpot deal. Line items on the invoice become HubSpot deal line items. Invoice payment status maps to a custom pick-list field on the deal. This preserves financial reference data without forcing a custom billing object.

WORKetc projects (with Gantt stages, milestones, tasks, timesheets) require a HubSpot custom object created under Enterprise licensing. Project name, description, status, and milestone summary migrate as custom object fields. Milestones map as custom datetime fields. For non-Enterprise accounts, projects associate to the related company or deal as a named association with a custom project status property.

WORKetc support tickets map to HubSpot tickets. Ticket subject, description, status (open, pending, resolved, closed), priority, owner, and associated contact/company all migrate. WORKetc ticket create/update timestamps are preserved as HubSpot ticket custom datetime fields. Ticket comments and internal notes migrate as HubSpot ticket engagement logs.

WORKetc call logs, emails, meetings, and notes migrate as HubSpot engagements linked to the associated contact record. Original activity timestamps, assigned owners, and full body content are all preserved during migration. HubSpot associations connect each engagement to the correct contact and company record in the destination CRM.

Any WORKetc custom field on contacts, companies, deals, tickets, or projects creates a HubSpot custom property. Field type is mapped: text → string, number → number, date → datetime, pick-list → pick-list. Custom field visibility and permissions are not migratable — your HubSpot admin sets those after migration.

WORKetc user records resolve to HubSpot owners by email match. Any WORKetc user without a matching HubSpot email is flagged before migration — your team either invites them to HubSpot first or assigns records to a fallback owner. Owner display names are preserved from WORKetc.

WORKetc discussion threads on any record (contact, deal, project, ticket) migrate as HubSpot engagement notes linked to the corresponding HubSpot record. Original author information and timestamp from WORKetc are preserved as note metadata. Discussion threading structure is flattened into chronological note entries for linear review.

WORKetc file attachments on contacts, companies, deals, tickets, or projects are preserved as HubSpot file attachments linked to the same record. The original file URL is retained where WORKetc storage is accessible; files are re-uploaded to HubSpot Files where the original URL is unavailable.