Migrate from PCRecruiter to Bullhorn ATS & CRM

PCRecruiter Person records with candidate activity (submissions, pipeline entries, placement history, skill tags) migrate to Bullhorn Candidate. We identify candidate activity by querying Position associations, Placement links, and skill tags on each Person record. The original PCRecruiter Person ID is preserved in a custom field pcr_person_id__c for reconciliation. Contact information, address, and employment history migrate as typed Bullhorn Candidate fields.

PCRecruiter Person records used purely as client contacts (no candidate activity, no submission history) migrate to Bullhorn ClientContact. We identify these by flagging Person records with Company associations but no Position or Placement links. ClientContact is linked to the corresponding ClientCorporation record via the corporationID field. Email, phone, and title migrate directly; any client-specific custom fields map to ClientContact custom properties.

PCRecruiter Company records map directly to Bullhorn ClientCorporation. The Company name becomes the corporationName field, and the company website maps to the webURL field. ClientCorporation is created before any Person or ClientContact import so that the corporationID lookup is satisfied at insert time. Parent-subsidiary relationships in PCRecruiter map to ClientCorporation's parentCorporationID lookup.

PCRecruiter Position records map to Bullhorn JobOrder. Job title, description, requirements, and address migrate to the corresponding JobOrder fields. Position status maps to JobOrder status (Open, Placed, Cancelled). The JobOrder ownerID is resolved from the PCRecruiter User mapping. We preserve the full position structure including any job-specific custom fields against JobOrder custom properties.

PCRecruiter Placement records map to Bullhorn Placement. Billing information, start date, end date, employee details, and client associations migrate to the corresponding Placement fields. Placement is linked to the migrated Candidate record (via candidateID), the migrated ClientCorporation record (via clientCorporationID), and the migrated JobOrder record (via jobOrderID). All three parent-record IDs must be resolved before Placement insert begins.

PCRecruiter Activity records against People or Positions migrate to Bullhorn Task (for calls, emails, tasks) and Event (for meetings). The activity type determines the destination object: emails and tasks become Task, meetings become Event, and notes become Note. We resolve the parent record reference (candidateID for Candidate activities, clientContactID for ClientContact activities, jobOrderID for Position activities) using the migrated record IDs from the ID mapping table generated during earlier phases.

PCRecruiter attachments (resumes, documents, uploaded files) associated with Person, Company, or Position records migrate to Bullhorn's ContentDocument model with ContentDocumentLink associations to the parent migrated record. We use the Bullhorn REST API file upload endpoint to transfer binary attachments, preserving the original filename and MIME type. Resume files are linked to the Candidate record's primary resume field where applicable.

PCRecruiter's configurable pipeline stages per Position migrate to Bullhorn JobOrder custom fields if the stage set is position-specific, or to Bullhorn's Opportunity pipeline configuration if the customer uses Bullhorn Opportunity tracking alongside JobOrder. Stage names, order, and any associated custom fields are preserved. Bullhorn's pipeline model is simpler than PCRecruiter's per-position stage configuration, so we document any complex stage logic for the customer to review post-migration.

PCRecruiter Tags on People, Companies, and Positions migrate to Bullhorn Candidate Tags and ClientContact Tags. Tags are stored as a flat taxonomy in PCRecruiter and must be re-created in Bullhorn. We extract the full tag vocabulary during scoping, generate a tag creation script for Bullhorn, and apply tags to migrated records during the import phase. Tags used for segmentation in PCRecruiter map to Bullhorn's List or segment model depending on the customer's intended usage.

PCRecruiter custom fields on Person, Company, Position, and Placement migrate to Bullhorn custom properties (Candidate, ClientCorporation, JobOrder, Placement) or to Bullhorn Custom Objects depending on complexity. Simple text, number, date, and picklist fields map to Bullhorn's native custom property types. Complex relational or multi-value fields may require a Bullhorn Custom Object, which is subject to the destination edition's limit (Bullhorn ATS: 2, Front Office Growth/Enterprise: 10). We confirm the edition with the customer before committing to a custom object migration plan.

PCRecruiter User accounts map to Bullhorn User records. We resolve by email match against the Bullhorn destination User table. Any PCRecruiter User without a matching Bullhorn User goes to a reconciliation queue for the customer's Bullhorn admin to provision before record import resumes. Record ownership assignments migrate by mapping the PCRecruiter userID to the Bullhorn ownerID via the User mapping table.

PCRecruiter accounts running multiple independent databases require an explicit consolidation strategy before migration begins. We either merge all databases into a single Bullhorn account (deduplicating overlapping records by email and company name) or migrate each database as a separate Bullhorn account or workspace. The customer confirms the strategy during scoping. Databases with different schema configurations (custom fields, pipelines) require separate field mapping documents. This is one of the highest-impact decisions on migration timeline and is resolved before any data extraction begins.