Migrate from PCRecruiter to Recruit CRM & ATS

PCRecruiter Person records with a Candidate role designation map directly to Recruit CRM Candidate records. We extract standard fields (name, email, phone, address, source, status), skill tags, availability date, and current employer. The original PCRecruiter Person ID is preserved in a custom reference field for relationship traceability. For Person records that serve as both Candidate and Client (the PCRecruiter dual-role model), we create both a Candidate entry and a Client entry in Recruit CRM and link them via the preserved original_person_id.

PCRecruiter Person records with a Client role designation, or dual-role Person records with both Candidate and Client associations, map to Recruit CRM Client records. Each unique Person record generates one Client entry. The original PCRecruiter Person ID is preserved in a custom reference field on the Client record for cross-referencing any migrated Candidate records sharing the same Person origin.

PCRecruiter Company records map to Recruit CRM Organization records. Company name, address, industry, and website migrate directly. We use Company domain or name as the dedupe key during import to prevent duplicate Organizations. Company associations to Person records (as hiring contacts or client contacts) are resolved by matching the Person-to-Company linkage and recreating it as a Client-to-Candidate or Client-to-Organization relationship in Recruit CRM.

PCRecruiter Position records map to Recruit CRM Job records. Position title, description, requirements, status, and location fields migrate directly. Job status (Active, On Hold, Filled, Cancelled) maps from the PCRecruiter position status with a custom field capturing any extended status notes. Positions linked to Companies become Jobs linked to the corresponding Organization records.

PCRecruiter Placement records map directly to Recruit CRM Placement records. We preserve start date, end date (for contract placements), billing rate, fee amount, Candidate reference, Job reference, and Client reference. The placement's status (Active, Completed, Terminated) migrates as-is. Placements are imported after both Candidates and Jobs exist in Recruit CRM to satisfy the lookup dependencies.

PCRecruiter Activity records—emails, calls, meetings, notes, and tasks logged against People, Positions, or Companies—map to Recruit CRM Activity records. Each activity type uses the appropriate Recruit CRM activity subtype. We preserve the original timestamp, direction (for emails and calls), duration (for calls), and body content. Activities are imported after all parent records (Candidates, Clients, Jobs) are present to resolve the activity-to-record linkage.

Resume files and documents attached to People, Positions, or Companies in PCRecruiter migrate as Attachments to the corresponding Candidate, Job, or Client records in Recruit CRM. We use the PCRecruiter attachments API endpoint to download files, preserving the original filename and MIME type. File associations to parent records are recreated using Recruit CRM's attachment API with the resolved parent record ID.

PCRecruiter pipeline stages defined per Position or as shared templates are extracted with their step names, order, probability percentages, and any stage-specific notes. We create a corresponding pipeline structure in Recruit CRM with the same stage names and ordering, then link Jobs to the appropriate pipeline. Stage-level automation triggers (if any were configured in PCRecruiter) are documented but not recreated; see the automation inventory deliverable.

PCRecruiter custom fields on Person, Company, Position, and Placement records are extracted with their field types (text, dropdown, date, numeric, checkbox). We map dropdown values by comparing picklist options in PCRecruiter against available values in Recruit CRM, flagging any options without a direct equivalent for customer confirmation. Multi-select dropdown values in PCRecruiter map to multi-select fields in Recruit CRM. Custom fields are pre-created in Recruit CRM before any data import begins.

Tags and labels applied to People, Companies, and Positions in PCRecruiter migrate as Tags in Recruit CRM. We extract the full tag taxonomy, deduplicate across all record types, and recreate tags as a flat taxonomy that can be applied to Candidates, Clients, Jobs, and Placements. Tag application history (which records had which tags) is preserved during import.

PCRecruiter workflow automations triggering emails, status changes, and field updates based on pipeline events are extracted as a written inventory rather than migrated as executable code. We document each automation's trigger event, conditions, actions, and recommended Recruit CRM equivalent. The customer's admin rebuilds automations post-migration using Recruit CRM's workflow automation builder. This is standard scope for all FlitStack AI migrations.

PCRecruiter accounts commonly run multiple independent databases for separate business units, geographic regions, or archival purposes. We either consolidate all databases into a single Recruit CRM workspace (People, Companies, Positions, and Placements merged by dedupe key) or migrate each database as a separate Recruit CRM workspace depending on the customer's preference. The customer confirms the consolidation strategy during scoping before any field mapping begins.