Migrate from PeopleStrong to Crelate

PeopleStrong candidate records (from the Talent Acquisition module) map to Crelate Person records. The mapping includes full name fields, email address, phone number, current title, current company, location, source attribution, and stage history. PeopleStrong stores stage history as a timeline with stage names and transition timestamps; we preserve the full stage progression in Crelate's Activity timeline linked to the Person. Resume data is extracted from the PeopleStrong candidate attachment and uploaded to Crelate as a document linked to the Person record.

PeopleStrong applications (candidate applied to a job requisition) map to Crelate Activity records of type Job Person, which represent the relationship between a Person and a Job. The application date, submission method, and referred-by attribution migrate as Activity metadata. The PeopleStrong application stage maps to a corresponding Crelate pipeline stage; we perform stage-name mapping during scoping because stage names are configurable per organization in both platforms.

PeopleStrong job requisitions with title, department, location, employment type, and description migrate to Crelate Job records. The requisition status (open, filled, on hold, cancelled) maps to Crelate Job status. PeopleStrong stores job owner and hiring manager as separate fields; we map these to Crelate's assigned User on the Job record. If the PeopleStrong requisition links to an internal employee record (internal posting), we flag this for manual review because Crelate does not have an Employee object.

PeopleStrong interview scorecards (evaluator, rating, comments, date) migrate to Crelate Activity records of a configured type such as Interview or Evaluation. Crelate supports custom Activity types and freeform notes fields. We map PeopleStrong's structured score fields (overall rating, criteria ratings) to Crelate's freeform Activity notes field, and include the evaluator name and interview date in the Activity metadata. If the customer requires structured scoring fields in Crelate, we document the configuration needed post-migration.

PeopleStrong offer letters stored as candidate attachments migrate to Crelate as Activity records of type Offer linked to the Person and Job, with the offer letter PDF attached as a document. Offer details (salary, start date, offer status) are mapped to Activity metadata fields or stored as structured notes depending on what PeopleStrong exposes via API. We flag that offer data in PeopleStrong may also be stored as fields on the application record rather than as separate objects; we enumerate these during schema discovery.

PeopleStrong recruiter assignments on requisitions and applications map to Crelate User assignments on Job and Activity records. We resolve by matching PeopleStrong recruiter email against Crelate User email. Any PeopleStrong recruiter without a matching Crelate User is held in a reconciliation queue for the customer's admin to provision the User before Activity import begins.

PeopleStrong tracks candidate sourcing channels (direct, referral, job board, agency) as a property on the candidate record. We map these to Crelate's Source field on Person. Custom source values created in PeopleStrong are preserved as freeform text if no matching Crelate Source option exists, or remapped to the nearest Crelate Source value during scoping.

PeopleStrong organizational structure entities (departments, cost centers, locations) are referenced by job requisitions. These migrate as lookup tables into Crelate's Department and Location objects, then resolved by reference during Job import. We preserve the full hierarchical structure from PeopleStrong in a Crelate configuration document so the customer's admin can rebuild the hierarchy in Crelate Settings if needed.

PeopleStrong job title and grade lookups used in requisitions and candidate records migrate to Crelate's Job Title field on Person. We treat these as value maps migrated before Person records so that the lookup reference is satisfied at import time. Grade bands and compensation ranges stored in PeopleStrong are flagged as out-of-scope for Crelate because it has no compensation object.

PeopleStrong candidate tags (used to categorize talent pools, skill tags, or status flags) map to Crelate Tags on Person records. We perform a schema discovery step during scoping to enumerate all active tag values and map them to Crelate Tags. The customer chooses between Crelate's native Tags or Lists during scoping based on how they intend to use the segmented groups.

PeopleStrong resume documents are stored as binary attachments linked to candidate IDs. They cannot be retrieved in the same API call as candidate record metadata. We separate the migration into a record phase and a document phase. The record phase migrates candidate profiles and structured fields. The document phase runs as a secondary batch, fetching each resume file by candidate ID and uploading to the corresponding Crelate Person record. Large file volumes (over 5,000 documents) are chunked to avoid timeout errors.

PeopleStrong Employee records (the core HCM object) have no equivalent destination in Crelate, which is a recruiting platform, not an HRMS. Employee fields (personal details, employment status, department, manager assignment, hire and termination dates) cannot migrate to Crelate Person because Crelate Person is a candidate and contact record, not an HR employee record. We flag all Employee object data as out-of-scope and recommend the customer evaluate a separate HRMS migration if employee data needs a destination platform.