Migrate from World Manager to Recruit CRM & ATS

World Manager Employee records map to Recruit CRM Candidate records. We map first name, last name, email, phone, address, and hire date directly. The World Manager employment_status field becomes a custom Candidate field. Active World Manager employees who are current job seekers migrate as active Candidates; employees who have left migrate as inactive Candidates or archived records at customer discretion. A World Manager hire date of 2023-01-15 becomes a custom date field original_hire_date__c on the Candidate for compliance and tenure reporting.

World Manager's Location hierarchy (restaurant, hotel, or retail location) does not have a direct Recruit CRM equivalent. We create tagging structures or organizational groupings in Recruit CRM that capture the original Location name. The location_id from World Manager becomes a text tag or custom field on the Candidate record. Teams that need to preserve location-based reporting in Recruit CRM should plan to use Candidate tags as a filter in Recruit CRM's reporting rather than as a native hierarchical structure.

World Manager Department records map to Candidate tags in Recruit CRM. Department names become tag values (for example, 'Front of House', 'Kitchen', 'Housekeeping') that can be applied to Candidate records for segmentation and reporting. Department assignments that originally controlled training module access in World Manager may require manual rebuild as Workflow Automation triggers in Recruit CRM Business or Enterprise tiers.

World Manager Role records map to Candidate tags or a custom availability field in Recruit CRM. Roles (for example, 'Shift Manager', 'Server', 'Bartender') become tag values for filtering and reporting. The mapping preserves the role-to-training-module relationship as a reference note that documents which training modules were assigned to each role for manual rebuild in Recruit CRM Workflow Automation.

World Manager training completion records map to Candidate Activity entries in Recruit CRM. The training module name, completion date, and score (if applicable) transfer to activity records attached to the Candidate. We map module_name to activity_title and completion_date to activity_date. World Manager's training module structure may use custom field names that require field-level mapping during the migration scope definition. Incomplete training assignments do not migrate as pending items; they are documented in the automation handoff inventory for rebuild in Recruit CRM Workflow Automation.

World Manager compliance documents attached to employee records migrate as document attachments on the Recruit CRM Candidate. We extract the original file, verify format compatibility (PDF, DOCX, image formats are supported), and attach to the Candidate record. Document naming conventions from World Manager are preserved in the attachment filename for traceability. Compliance documents that represent certifications (food handler permits, alcohol service licenses, safety certifications) are flagged as certification-type documents in Recruit CRM with a custom document type field.

World Manager certification records (certification type, issuing authority, expiration date, certification number) map to a combination of custom Candidate fields and document attachments in Recruit CRM. The certification name and expiration date become custom date and text fields on the Candidate record; the actual certification document (PDF or image) attaches as a Candidate document. Expired certifications are flagged with a custom expired flag field for recruiter awareness. Recruit CRM does not have a native certification management module; this is a structured mapping using available custom fields and document attachments.

World Manager shift eligibility data (available days, available hours, shift preferences) does not have a direct Recruit CRM standard field. We map these values to Candidate availability fields or custom text fields during migration. Teams that rely on World Manager's shift scheduling features for operational workforce management should note that Recruit CRM is a recruitment ATS, not a workforce scheduling tool; scheduling capabilities are out of scope for this migration and would require a separate scheduling platform if shift coordination is a business requirement.

World Manager custom fields on Employee records (for example, certification_type, shift_pattern, compliance_status, manager_id) map to Recruit CRM custom fields on the Candidate object. We create the equivalent custom fields in Recruit CRM before migration using the same field label and appropriate data type (text, date, picklist, checkbox). Any World Manager custom fields that do not have a direct Recruit CRM equivalent are documented with the proposed mapping approach and presented to the customer for approval before migration begins.

World Manager training assignment workflows that automatically assign training modules based on Role, Location, or Department do not migrate as automation code to Recruit CRM. Recruit CRM Workflow Automation (available on Business and Enterprise tiers) uses a different trigger and action model from World Manager's training assignment rules. We deliver a written inventory of every active World Manager training workflow with its trigger conditions, assigned modules, due date logic, and notification settings, mapped to a recommended Recruit CRM Workflow Automation configuration. The customer's admin rebuilds each workflow in Recruit CRM using this inventory as the specification document.