Migrate your PCRecruiter data

The core record type in PCRecruiter. A Person record can serve as a Candidate, a Client contact, or both simultaneously due to the company-centric model. Standard fields include name, contact info, resume, status, and source. We migrate Person records 1:1 and tag them with the appropriate role context in the destination.

Position records contain job details, requirements, pipeline configuration, and associations to Candidate records. We preserve the full position structure including pipeline stage definitions, required fields, and automations attached to each position during migration.

Company records in PCRecruiter function as the parent entity for both client relationships and candidate affiliations. We migrate Companies as the central hub and reassign their associated People and Position records accordingly in the destination system.

Placement records represent successful hires and contain billing information, start dates, employee details, and client associations. We map Placements to the destination's equivalent object and preserve the link back to the originating Position and placed Candidate.

Activity records include emails, calls, notes, meetings, and tasks logged against People or Positions. PCRecruiter stores detailed activity history. We export activity logs and map them to the destination's activity/engagement objects, noting that email body content formatting may require post-migration review.

Resume files, documents, and uploaded files associated with People, Positions, or Companies are migrated via the attachments API endpoint. We preserve file associations to their parent records and handle duplicate file names during import.

Pipeline stages are configurable per-position or as shared templates. We extract the stage definitions, step names, order, and any automations triggered at each stage. Stages are recreated in the destination using equivalent workflow or pipeline configuration.

PCRecruiter supports custom fields on Person, Company, Position, and Placement records. We map custom field values to destination custom properties, applying field-type conversion (text, dropdown, date, checkbox) and preserving any picklist option values.

Workflow automations in PCRecruiter trigger emails, status changes, and field updates based on pipeline events or record conditions. We document automation logic and recreate triggering events in the destination system where equivalent automation features exist.

User accounts in PCRecruiter include login credentials, roles, and ownership assignments on records. We map Users to the destination's user model and reassign record ownership during import, noting any role permission differences that may require post-migration adjustment.

PCRecruiter accounts can have multiple independent databases for different markets, divisions, or archival purposes. We either consolidate all databases into a single destination account or migrate each database as a separate workspace, depending on the destination system's multi-database support.

Tags in PCRecruiter label People, Companies, and Positions for segmentation and filtering. We migrate tags as a flat taxonomy and recreate them in the destination as tags, labels, or segments depending on the target system's terminology.