Migrate from StaffingSoft to Recruit CRM & ATS

StaffingSoft Candidate records map directly to Recruit CRM Candidate profiles. We preserve all standard contact fields (name, email, phone, address) plus custom candidate properties. Skills, employment history, and certification fields map to Recruit CRM's Skills and Experience sections. We extract interview notes, ratings, and scorecard content as Notes attached to the Candidate record, preserving the original author and timestamp.

StaffingSoft Job Order records map to Recruit CRM Job records. The job title, requirements, qualifications, opening date, and status transfer directly. Pipeline stage assignments per job order map to Recruit CRM pipeline stages with stage probability values preserved. In StaffingSoft, job orders in Staffing Edition are linked to Clients; we resolve that Client reference during import and attach the Job to the corresponding Recruit CRM Client.

The Assignment is StaffingSoft's central staffing-mode entity linking a Candidate to a Job Order with bill rate, pay rate, start date, end date, and placement status. Recruit CRM does not have a standalone Assignment object; instead, placement details live as properties on the Application record or as custom fields on the Job when the candidate is placed. We re-parent assignment fields into Recruit CRM Application fields (markup, bill rate, pay rate, start/end dates) and set the Application status to Placed. This is the key structural transformation in staffing-mode migrations.

StaffingSoft Client/Company records map 1:1 to Recruit CRM Client profiles. We transfer contact information, billing address, and client-specific notes. In HR Edition deployments, the client object represents the employing organization; we map it identically to the Recruit CRM Client record. Client-to-job order relationships are preserved by resolving the Client ID at Job creation time.

Resume files stored in StaffingSoft's document management module are exported as binary files and re-attached to the corresponding Candidate record in Recruit CRM. File naming conventions vary by export method; we apply a consistent naming pattern of CandidateName_DocType_Date during import. If StaffingSoft stores resumes as linked external URLs rather than file binaries, we update the Candidate record with the original URL as a reference field.

StaffingSoft configurable pipeline stages (per job order or globally) map to Recruit CRM pipeline stages. Stage names and ordering transfer; stage-specific automation (such as email triggers or owner reassignments attached to a stage in StaffingSoft) does not migrate. We deliver a stage-by-stage inventory noting which StaffingSoft stages had automation attached so the customer can rebuild in Recruit CRM's Workflow Automation.

StaffingSoft user accounts including recruiter names, team structures, and permission roles map to Recruit CRM User records. We resolve owners by email address match. Any StaffingSoft user referenced on an assignment, job order, or candidate record without a matching Recruit CRM User goes to a reconciliation queue for the customer to provision before record import continues.

StaffingSoft custom fields on candidates, job orders, and assignments require field-level mapping with type preservation. Text fields map to text, dropdowns to picklists, dates to dates. Lookup dependencies that reference StaffingSoft internal IDs are resolved by looking up the corresponding target record (Candidate, Job, Client) and inserting the Recruit CRM record ID. Custom field definitions do not auto-create in Recruit CRM; we pre-create the destination fields before migration begins.

Interview feedback, scorecards, and scheduling notes stored as activities against the candidate record in StaffingSoft are extracted as structured content and attached as Notes to the corresponding Candidate record in Recruit CRM. Interview ratings and disposition values transfer as text in the Note body or as custom Candidate fields if the customer chooses to surface them as structured data. The original interview date is preserved in the Note timestamp.

StaffingSoft cross-posting configuration to external job boards stores the posting URLs and dates as associations on the job order. We export these as URL records and attach them as a custom text area or multi-select field on the Recruit CRM Job. Active posting credentials (Indeed API keys, LinkedIn credentials, Monster login tokens) do not transfer and must be re-entered in Recruit CRM's job board integration settings.