Migrate from People First to Crelate

People First Employee records map to Crelate Contact records. We extract name, email, job title, department, start date, and any custom employee properties from the available People First export. The employee's email address serves as the dedupe key during Crelate import. Note that Crelate's Contact object is recruiting-centric (client contacts and candidate contacts); if the customer's People First data includes both current employees and recruiting candidates, we recommend splitting into two Crelate Contact lists rather than co-mingling them under one record type.

People First Department records with parent-child hierarchy map to Crelate Company records. The department name becomes the Company name; the parent department becomes a separate Company record with a custom field parent_department__c linking them. Crelate's Company object supports hierarchical structures via custom fields but not native org-chart hierarchies, so we flatten the People First structure into a linked list of Company records with explicit parent references.

People First admin and end-user accounts map to Crelate User records. We match by email address; any Crelate User provisioned with the same email receives the migrated records. If Crelate User provisioning is pending, we hold the relevant records in a user-reconciliation queue and resume after the customer's admin provisions accounts.

People First PTO or time-off balance data maps to Crelate Contact custom fields. We request the customer provides a field inventory for their PTO data structure during scoping, as no public schema was confirmed in research. Balances and accrual history transfer as numeric or currency custom fields on Contact; accrual change history transfers as Activity Form records or Note attachments.

People First engagement and recognition records (awards, shoutouts, recognition data) have no direct Crelate equivalent. We map these to Crelate Activity Forms with custom question fields capturing the recognition type, date, and recipient, or as Note records attached to the Contact. The customer chooses the approach during scoping. Recognition trend data spanning multiple employees maps to a custom Crelate report using Activity Form responses.

People First benefits data (health plans, retirement, supplemental benefits) migrates to Crelate Contact custom fields for structured data (enrollment status, plan type) or to Note records for plan documents. No public benefits schema was confirmed in People First research, so we request the customer provides a benefits field inventory before migration. Benefits data is flagged for manual verification post-migration.

People First employee documents (contracts, policies, offer letters) cannot be confirmed as migratable via a documented export endpoint. We handle document migration via file-level transfer where the customer provides the document repository directly. Documents attach to the corresponding Crelate Contact via ContentDocumentLink. If no document export is available from People First, we document this gap in the migration report and recommend the customer maintain the original document source.

People First's conflict resolution records have no direct Crelate equivalent since Crelate is an ATS, not an HRMS. We map conflict resolution case data to Crelate Activity Forms with custom fields capturing case ID, resolution status, and key dates, or to Note records attached to the relevant Contact. The customer specifies the mapping during scoping. HR teams migrating to Crelate for recruiting purposes should consider whether conflict resolution data is relevant to the new system or should remain in People First as a read-only archive.

No public custom fields schema was confirmed for People First. If the customer has employer-specific custom fields on Employee or Department objects, we request a field inventory before migration scoping is complete. Custom field names, data types, and picklist values must be provided by the customer. We create matching Crelate custom fields (Text, Number, Currency, Picklist) under Settings | Core Records | Contacts/Companies before import, and map values row-by-row during the transform phase.

People First workflow and automation rules do not migrate to Crelate. Crelate's Automation and Sequencing features are only available on Business Plus and Enterprise tiers, and even then they are recruiting-specific (candidate nurture sequences, job posting triggers). HRMS-specific workflows (onboarding checklists, conflict escalation paths, PTO approval chains) have no equivalent in Crelate's recruiting data model. We deliver a written inventory of every active People First workflow with its trigger, conditions, and actions for the customer's admin to evaluate against Crelate's automation capabilities.

If the customer's People First instance includes job posting or requisition data, these map to Crelate Job records. The Job object in Crelate supports title, description, status, assigned recruiter, and custom fields. Job Posting integrations to Indeed, CareerBuilder, Monster, and Dice migrate as Crelate integration configurations rather than data records.

If the customer's People First instance tracks candidate pipeline data (from a prior ATS use), these map to Crelate Opportunity records. Crelate Opportunity tracks pipeline stage, probability, value, and associated Contact and Job. Each pipeline stage in People First maps to a Crelate Opportunity stage value configured in Settings. We resolve the Opportunity-Contact and Opportunity-Job lookups at migration time.