Migrate your PeopleForce data

The central PeopleForce object. We migrate all standard fields (name, contact info, employment dates, department, manager assignment) and preserve the full employment history timeline. Active and inactive statuses are mapped directly to the destination equivalent.

PeopleForce stores profile photos, bio data, emergency contacts, and skills as structured sub-objects linked to each Employee. We flatten these into the destination profile structure, preserving attachments and custom profile fields.

Positions capture job title, department, employment type, and effective dates for each employee. Where the destination HRMS uses a different job-title schema, we apply a mapping table to align titles across systems during migration.

PeopleForce supports multiple leave types with configurable accrual rules and approval workflows. Leave balances and request history are migrated as transactional records; policy definitions require reconfiguration in the destination system based on its own leave engine.

Review cycles, review forms, and submitted feedback are stored as linked objects. We migrate completed review records and scores, but the review form builder configurations (questions, scales, weightings) are platform-specific and typically require re-implementation.

PeopleForce PeopleRecruit handles job postings, applications, and candidate pipelines. Open positions and application history are migrated; multiposting configurations and job board connections do not transfer across platforms.

Custom triggers and automated sequences are built on PeopleForce's workflow engine using employee profile attributes and key dates. Workflow logic is documented and described during scoping, but automation rules must be rebuilt in the destination HRMS.

Employee documents (contracts, ID copies, certifications) are stored per employee record. We migrate document metadata and content where accessible via API, noting that file attachments may require re-upload in the destination system.

The recognition module stores Kudos given between employees with timestamps and optional messages. These are migrated as historical records in a supplemental table, as most destination HRMS platforms do not have a native equivalent object.

PeopleForce generates automated checklists tied to onboarding and offboarding events. Task completion status and history are migrated; the checklist templates themselves are platform-specific and require reconfiguration.

PeopleForce supports custom fields on the Employee object. We inventory all active custom fields during discovery, map their data types to destination equivalents, and migrate custom field values as structured properties on each record.

The audit trail is a platform-generated, read-only log of user actions and system events. It is not portable data — it belongs to the PeopleForce tenant and cannot be exported or migrated. We document the audit trail schema for compliance reporting purposes but do not transfer records.