Migrate from StaffingSoft to Crelate

StaffingSoft Candidate records map to Crelate Contact. We preserve contact details, employment history, skills, and status as Crelate standard fields. StaffingSoft's custom candidate properties migrate to Crelate custom fields on Contact. Email serves as the primary dedupe key. Resume files export as document attachments and re-attach to the corresponding Crelate Contact record. StaffingSoft's candidate status pipeline stages map to Crelate's candidate workflow stages.

StaffingSoft Job Order records map to Crelate Job Order. We preserve requirements, qualifications, opening dates, and pipeline stage assignments. StaffingSoft's pipeline stages transfer to Crelate's job pipeline stages, but any custom stage-specific automation must be rebuilt in Crelate's workflow builder. Job Order owner maps to the corresponding Crelate User by email match.

StaffingSoft Assignment is the core entity linking a Candidate to a Job Order with bill rate, pay rate, start date, and end date. Crelate uses a Placement record type to represent the same concept. We preserve bill_rate and pay_rate as typed Crelate fields on the Placement, map the assignment start/end dates, and resolve the StaffingSoft Candidate-to-Crelate Contact and Job-Order-to-Job-Order lookup at migration time. Placement status (active, completed, terminated) migrates as the Crelate Placement status.

StaffingSoft Client records map to Crelate Company. We preserve company name, contact information, address, and billing preferences. In StaffingSoft's HR edition, the Client object functions as the employing organization; we map this to the Crelate Company that represents the hiring client for each Job Order. Company serves as the parent record for Job Orders in Crelate's data model.

Resume files stored in StaffingSoft's document management module export as binary files and re-attach to the corresponding Crelate Contact record. File naming conventions vary by export method; we standardize to a [CandidateID]_[DocumentType].[ext] format. StaffingSoft supports multiple document types per candidate; each migrates as a separate Crelate document attachment.

StaffingSoft User accounts including recruiter assignments, team structures, and permission roles export cleanly. We map owner IDs to corresponding Crelate Users by email match. Any StaffingSoft User without a matching Crelate User goes to a reconciliation queue for the customer to provision before record import completes. Team structures and role hierarchies migrate as Crelate team configurations.

StaffingSoft pipeline stages are configurable per job order or globally. Stage names and order transfer to Crelate's job pipeline configuration. Custom stage-specific automation, if any, must be rebuilt in Crelate's workflow builder. Stage-specific custom fields require field-level mapping during migration scoping.

StaffingSoft custom fields on Candidates, Job Orders, and Assignments require field-level mapping. Field types (text, dropdown, date, numeric) are preserved and mapped to equivalent Crelate custom field types. StaffingSoft ID references embedded in custom field values must be resolved to corresponding Crelate record IDs during transformation. Custom field configurations are documented in the field mapping deliverable.

StaffingSoft interview feedback, scorecards, and scheduling notes store as activities against the Candidate record. We extract the content and attach it as Crelate Activity records linked to the corresponding Contact. Rating scores migrate as custom numeric fields on the Activity. Interview scheduling details (date, time, interviewer name) preserve on the Activity.

Cross-posting configuration to external job boards stores as site associations on the StaffingSoft Job Order. We export the posting URLs and posting dates as Crelate Job Distribution records. Active posting credentials (Indeed, Dice, CareerBuilder, Monster) must be re-entered in Crelate's job distribution settings post-migration because credentials do not export from StaffingSoft. Posting history is informational in Crelate.

StaffingSoft onboarding task checklists and document collection status transfer as Crelate Contact custom fields and task lists. Any e-signature or I-9 integration configurations must be reconfigured in Crelate. Onboarding status (documents received, background check pending, etc.) migrates as a Contact property with a status dropdown.

StaffingSoft custom report definitions and saved filters are not exportable as portable artifacts. We recommend exporting report data as CSV before migration and rebuilding reports in Crelate's Advanced Reports and Analytics module (available on Business plan). Report rebuilding is outside standard migration scope; we deliver a written list of source reports requiring rebuild.