Migrate from PCRecruiter to Crelate

PCRecruiter People records can function as candidates, client contacts, or both simultaneously due to the company-centric model. We analyze each People record's associations, tags, and placement history to determine whether it belongs in Crelate as a Contact record, a Contact with client flags, or a separate record type. The mapping preserves the original PCRecruiter People ID in a custom field pcr_people_id__c for audit and cross-reference. Standard fields (name, email, phone, address) map directly; custom fields translate per the field-type mapping document.

PCRecruiter Company records map directly to Crelate Company records. The Company record serves as the parent entity for both client relationships and candidate affiliations. We preserve the Company ID in crelate_company_id__c for reconciliation. Address, industry, and custom properties migrate as typed Crelate fields. Company records are imported before People records so that the Company lookup is satisfied at Contact insert time.

PCRecruiter Position records map to Crelate Job records. Job details including title, description, requirements, status, and owner assignment migrate directly. Position pipeline configuration (stage names, order, probabilities) maps to Crelate Job Stage definitions. Custom fields on Position translate to Crelate Job custom fields by type match.

PCRecruiter Placement records represent successful hires with billing information, start dates, employee details, and client associations. Crelate supports Placement as a custom object or through its native placement tracking depending on account configuration. We map placement start date, end date (if contract), billing rate, client company reference, and candidate reference. Placement history is preserved for reporting continuity.

PCRecruiter pipeline stages are extracted from Position configurations and shared templates. Each stage's name, order, and probability percentage migrates to Crelate Job Stage definitions. We create the stage structure in Crelate before Job records are imported so that stage references are valid at insert time. Stage automation triggers are documented separately for admin rebuild.

PCRecruiter Activity records include emails, calls, notes, meetings, and tasks logged against People or Positions. We map these to Crelate's native activity types preserving the original timestamp, body content, and association to the parent Contact or Job. Email attachments migrate as linked files. Activity ordering is preserved by setting the Crelate activity date to the original PCRecruiter timestamp.

Resume files, documents, and uploads associated with People, Companies, or Positions migrate via Crelate's file attachment API. We preserve file associations to their parent records (Contact, Company, or Job) and maintain original file names. Binary file content transfers directly; file metadata (upload date, file type) is preserved in Crelate's file record.

PCRecruiter custom fields on Person, Company, Position, and Placement records migrate to Crelate custom fields. We extract the full custom field schema including action type (text, dropdown, date, currency, email, phone) and translate to the equivalent Crelate field type. Dropdown custom fields require explicit value translation when picklist options differ between systems. Custom fields are pre-created in Crelate before any record data is imported.

PCRecruiter Tags label People, Companies, and Positions for segmentation and filtering. We migrate tags as a flat taxonomy and recreate them in Crelate as Tags on the respective record type. Tag category structure from PCRecruiter maps to Crelate tag groups if the account uses tag segmentation. The customer confirms tag strategy during scoping.

PCRecruiter User accounts include login credentials, roles, and ownership assignments on records. We map Users to Crelate User records by email match. Any PCRecruiter Owner without a matching Crelate User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Owner assignments on migrated records are resolved against the User mapping.

PCRecruiter accounts commonly run multiple independent databases for different business units, geographic regions, or archival purposes. Each database has its own schema configuration and pipeline settings. We treat each database as a distinct migration scope, either consolidating all records into a single Crelate account (with workspace partitioning if needed) or migrating each database as a separate Crelate workspace. The customer confirms the consolidation strategy during scoping before field mapping begins.

PCRecruiter workflow automations trigger emails, status changes, and field updates based on pipeline events or record conditions. These do not migrate as code to Crelate because the automation models differ structurally. We document each automation's trigger, conditions, actions, and recommended Crelate equivalent and deliver the inventory to the customer's admin for post-migration rebuild.