Migrate from World Manager to Crelate

World Manager employee records map to Crelate Contact. We extract first name, last name, email address, hire date, employment status, and World Manager employee ID. The World Manager employee ID is stored in a custom field wm_employee_id__c on the Crelate Contact for audit traceability and for resolving training assignment lookups. If a World Manager employee has no email address on record, we use the location code plus a generated unique identifier to construct a lookup-safe placeholder and flag the record for admin verification before Crelate goes live.

World Manager locations (physical sites, stores, restaurants, or regional offices) map to Crelate Company records. The World Manager location name becomes the Company Name field, and the location address is mapped to the appropriate street, city, state, and postal code fields. Location code from World Manager is stored in a custom field wm_location_code__c on the Company. The Company object is created before any Contact import so that the CompanyId lookup on Contact can be resolved at insert time.

World Manager's Department records have no direct Crelate standard object equivalent. We map departments to Crelate Tags on the Contact record, with one tag per department assignment per employee. If an employee is assigned to multiple departments, we create one tag per department. We also populate a custom multi-select picklist field wm_departments__c to preserve the full department list in a single field for reporting. The department-to-tag mapping is configured during scoping and validated against a department list export from World Manager.

World Manager Role assignments map to a custom text field wm_role__c on the Crelate Contact. The current active role becomes the primary value, and historical role assignments are appended as comma-separated values in a secondary field wm_role_history__c. Role-based tags (e.g., management, frontline, safety-certified) are also created in Crelate to enable list segmentation by job function. Role is resolved at migration time using World Manager's employee-department-role join table.

World Manager training module definitions map to a Crelate custom object named WM_Training_Module__c. We extract the module name, description, module type (video, quiz, policy acknowledgment, safety certification), and duration. The custom object is created in Crelate before any training assignment records are imported. Module IDs from World Manager are preserved as wm_module_id__c on the custom object for join resolution with the training assignment data.

World Manager training completion records map to a custom object WM_Training_Completion__c with a lookup to the Contact record (the employee) and a lookup to WM_Training_Module__c (the training module). We extract completion date, score if applicable, pass/fail status, expiration date for time-limited certifications, and the instructor or manager who signed off. Each completion record is linked via Crelate's custom object relationship to the correct Contact using the wm_employee_id__c cross-reference resolved during the Contact import phase.

Certifications tracked in World Manager (food handler permits, alcohol service licenses, safety certifications, manager credentials) map to a custom object WM_Certification__c on the Crelate Contact. Fields include certification name, issuing authority, issue date, expiry date, and a status formula field flagging expired or expiring-within-30-days records. Certification document files (PDFs, images) are stored locally and attached to the WM_Certification__c record via Crelate's ContentDocumentLink mechanism after the custom object records are inserted.

World Manager compliance documents (signed policies, regulatory filings, audit records, background check results) attach to the corresponding employee Contact record via ContentDocumentLink in Crelate. We extract documents from World Manager's document storage, map the file type and upload date, and attach each document to the Contact whose employee record the document belongs to. Documents with no resolvable employee (orphaned attachments) are listed in a reconciliation report for the customer to resolve before cutover.

World Manager tracks employment status (active, on-leave, terminated, seasonal-inactive) which does not map to Crelate's standard Contact status field (which tracks recruiting pipeline stage). We store the World Manager employment status in a custom picklist field wm_employment_status__c on Contact. Active employees migrate with their status preserved; terminated employees are migrated as Inactive Contacts unless the customer requests they be excluded from the migration scope entirely.

World Manager tracks shift eligibility (day shifts, night shifts, weekend availability, split shifts) per employee per location. Crelate does not have a native scheduling or shift availability model. We store shift eligibility as a custom multi-select picklist field wm_shift_eligibility__c on the Contact record, with one entry per eligible shift type. Shift eligibility tied to specific locations uses the wm_location_code__c on the related Company record to provide context.

World Manager managers and supervisors are employee records in their own right. We map them to Crelate Contact records using the same extraction logic as standard employees. The manager-employee relationship is preserved by populating a custom lookup field wm_manager__c on the employee Contact pointing to the manager's Contact record. If a manager does not have an email in World Manager, the cross-reference falls back to the World Manager employee ID stored in wm_employee_id__c.

World Manager records interactions including onboarding signoffs, manager check-ins, and compliance approval events as structured records. These are mapped to Crelate Task records with TaskSubtype set to standard (for administrative tasks) and a custom field wm_interaction_type__c indicating the original World Manager interaction category (onboarding, compliance, performance check-in). The activity date is preserved as ActivityDate on the Task. Long-form comments are stored as Note records attached to the Contact. We exclude system-generated audit log entries that do not represent meaningful human-readable activity.