Migrate from Skyward CRM to HubSpot

Skyward contact fields map directly to HubSpot contact properties. The contact's primary organization link in Skyward becomes a HubSpot company association via the hs_associations field. Skyward's contact owner ID resolves by email match against HubSpot user records. If the email lookup fails, the contact is flagged for manual owner assignment before the final load.

Skyward organizations map to HubSpot companies 1:1. Organization name maps to the company name property. Multi-branch organizations in Skyward require decision on whether to map as a single HubSpot company or parent-child company hierarchy preserved via the Parent Company association.

Skyward deals map to HubSpot deals with pipeline and stage translation. Each Skyward sales process maps to a HubSpot pipeline. Deal stage names map value-by-value to the corresponding HubSpot pipeline stage. Deal owner resolves by email match to HubSpot user.

Skyward sales processes contain stage definitions with probabilities. Each sales process becomes a HubSpot pipeline. Within each pipeline, stages map to HubSpot deal stages. Stage probabilities are stored as custom numeric properties on the deal record since HubSpot stages have their own probability fields.

Skyward activities map to HubSpot engagement objects: calls to HubSpot calls, emails to emails, meetings to meetings. Each activity preserves its original timestamp, associated contact or deal link, owner, and notes body. The activity type distinction (call, email, meeting) maps to HubSpot's engagement type property.

Skyward leads that have not yet converted to contacts map to HubSpot contacts with lifecyclestage set to 'lead'. Converted Skyward leads that created both a contact and an organization map to the HubSpot contact-company association model. The conversion timestamp is preserved as a custom property for reporting continuity.

Skyward contact custom fields become HubSpot contact custom properties. The property name is normalized to snake_case. Property type (text, number, date, picklist) maps to the corresponding HubSpot property type. Picklist values require value-by-value mapping when HubSpot already has a matching picklist.

Skyward organization custom fields map to HubSpot company custom properties. Industry classification fields from Skyward may require value mapping to HubSpot's built-in industry picklist if one exists. We also normalize field names to snake_case and set the appropriate property type (text, number, date, or select) based on the source field definition.

Skyward deal custom fields map to HubSpot deal custom properties. Deal priority, probability override, and custom forecast category fields become custom properties on the deal record. We map each field type to the corresponding HubSpot property type, and for picklist fields we create a matching picklist option set if it does not already exist.

Skyward's partner management module has no direct HubSpot equivalent. Partner company records migrate as HubSpot companies. Partner contact records migrate as HubSpot contacts associated with the partner company. Partner-specific deal routing rules must be rebuilt as HubSpot workflow actions. We export the existing routing logic as JSON and provide a mapping table to help the admin recreate the workflow enrollment criteria and associated property updates.

Skyward's sales performance grading (report card feature) has no HubSpot equivalent. Grade scores and performance history migrate as custom properties on the associated contact or deal record for historical reference only. We preserve the original grading period as a custom date property, enabling time‑based filtering in custom reports.

Skyward file attachments linked to contacts, organizations, or deals download and re-upload to HubSpot Files. Files are re-associated to the corresponding HubSpot record via the file associations API. File size limits of HubSpot's file hosting apply. We also verify that each file's MIME type is supported and rename any duplicate file names to avoid collisions during upload.