Migrate from Ready_ to HubSpot

UKG Ready employee records map to HubSpot contacts. Standard fields (firstname, lastname, email, phone) migrate as direct field-to-property mappings. Employment-specific fields (jobtitle, department, manager) migrate as HubSpot custom contact properties. The contact's original UKG Ready create timestamp is preserved as a custom datetime property for reporting continuity.

UKG Ready departments map to a custom pick-list property on HubSpot contacts (e.g., Department__c) or as a custom property on a HubSpot company record representing the organization. If UKG Ready's departments have parent-child hierarchies, those relationships are flattened into the pick-list value with parent context preserved as a secondary property.

UKG Ready position titles map directly to HubSpot's jobtitle contact property — this is the standard CRM field for professional title. No custom property creation required unless UKG Ready's position titles include internal job codes that need separate storage. These codes are stored in a separate text property for reference.

UKG Ready's manager_id foreign key cannot map to a native HubSpot contact field because HubSpot has no built-in manager hierarchy. We map the manager reference to a custom contact property (e.g., Manager_Email__c) storing the manager's email, enabling the migration to resolve the manager to their own HubSpot contact record after load. Teams requiring a formal org chart rebuild it post-migration.

UKG Ready's time-off request records — including request type, dates, status, and approver — have no native HubSpot equivalent because HubSpot has no HR module. We create a HubSpot custom object to store these records and associate each request to the requesting contact's HubSpot record via a custom lookup field after migration.

UKG Ready's benefits enrollment records (plan type, coverage level, enrollment date, dependents) cannot map to any native HubSpot CRM object. These migrate as a HubSpot custom object with associations to the relevant contact records. The enrollment history is preserved but requires post-migration relationship setup.

UKG Ready's performance review records — rating, review date, reviewer, comments — migrate to a HubSpot custom object linked to the contact. Review cycles and rating scales require value-mapping because UKG Ready's rating schema may differ from any existing HubSpot custom property values used for other purposes.

UKG Ready's holiday calendar and scheduling rules have no HubSpot CRM equivalent. Holiday dates and applicable regions migrate as a HubSpot custom object or as a list of dates stored in a custom multi-select property on the company record, depending on whether the schedule applies per employee or per location.

If UKG Ready's recruiting module stores candidate profiles, those map to HubSpot contacts with a custom 'Candidate_Source__c' property indicating the original application. Candidate pipeline stages (applied, screened, offered, hired) migrate as a custom pick-list property on the contact since HubSpot's deal pipeline applies to opportunities, not candidates.

Documents attached to UKG Ready employee records (offer letters, contracts, certifications) are downloaded and re-uploaded to the corresponding HubSpot contact's file storage. Original filenames and upload dates are preserved in HubSpot's file metadata. File versioning is preserved where possible, and any missing attachments are flagged for manual upload.

UKG Ready's single sign-on configuration, SCIM provisioning, and identity provider mappings cannot migrate to HubSpot. These are destination-side configuration that your IT team must set up in HubSpot's authentication settings using the same identity provider. Test the SSO configuration in a staging environment before enabling it for all users.

UKG Ready's payroll integration connections (ADP, Paychex, or internal payroll feeds) do not have a HubSpot equivalent because HubSpot has no payroll module. These integrations must be rebuilt or decommissioned as part of the HRIS migration separate from the CRM migration.