Migrate from Roubler to Crelate

Roubler employee records in the recruiting and hiring pipeline map to Crelate Contact records (for candidate profile) and Candidate records (for ATS pipeline tracking). We extract name, email, phone, address, position applied for, employment type, and start date from Roubler's employee object. The candidate's current onboarding state from Roubler becomes a Crelate Activity or Note. Active employees who are already past onboarding do not map to Crelate's candidate model; they are flagged as outside ATS scope and documented as requiring a separate HRMS destination.

Roubler position definitions (role title, FTE value, assigned tasks) map to Crelate Job Order records. The position title becomes the Job Order name; the FTE allocation and task list do not map directly to Crelate fields. We carry the position title as a text field and document the FTE as a note or custom field. Positions with no associated recruiting activity are documented in the migration inventory as workforce management data with no Crelate equivalent.

Roubler onboarding records include task completion status, document collection steps, and employee setup progress. We extract the current state of each onboarding workflow as a Crelate Activity entry or Note on the candidate record. In-progress tasks and provisional assignments do not transfer meaningfully as active workflow steps because Crelate has no onboarding workflow object. We deliver a written log of each onboarding task and its completion state for the customer's admin to rebuild in Crelate or another onboarding tool.

Roubler custom fields on employee records export as flat key-value pairs. Crelate supports a maximum of 20 custom fields per entity (Contact, Company, Opportunity). If the Roubler employee record exceeds 20 custom fields, we prioritize the 20 most-used fields for import and archive the remainder as structured Notes on the Contact record. Categorical fields that exceed the limit can alternatively be converted to Crelate Tags, which do not count against the 20-field limit. The customer selects the strategy during scoping.

Employee documents (contracts, certifications, IDs, onboarding paperwork) uploaded to Roubler are not accessible via the documented public API. Binary file attachments cannot be migrated automatically. We alert customers during discovery so they can export documents manually via screen capture or bulk download before the migration window closes. Crelate does not provide a document repository with the same access patterns; documents must be re-attached manually in Crelate or stored in a separate document management system.

Roubler roster and shift data (time, location, assigned employee, demand-based scheduling linked to POS) has no equivalent object in Crelate's ATS data model. Crelate is purpose-built for candidate tracking and recruitment pipeline management, not workforce scheduling. Roster history is flagged as outside Crelate scope and documented in the migration inventory for the customer to assess against a separate scheduling or workforce management tool.

Roubler leave entitlements, accrual history, and current balances export from the API, but Crelate's ATS schema has no leave balance object. Leave data does not map to any Crelate entity. We export the leave balance snapshot as a structured CSV for the customer's records and note it as workforce management data requiring a separate HRMS destination.

Roubler timesheet records (clock-in/out events, hours worked, pay period links) do not map to Crelate. Crelate has no timesheet or attendance object. We flag timesheet data as outside Crelate scope and deliver a CSV export of the most recent pay period for the customer's records. Timesheets linked to locked payroll runs in Roubler are write-locked in the source and flagged during discovery.

Roubler payroll runs (gross/net amounts, pay period summaries, Xero/MYOB journal exports) do not map to Crelate's ATS. Crelate is a recruitment and candidate management platform and does not handle payroll processing. Payroll run summaries are excluded from the Crelate migration scope and documented in the migration inventory for the customer's finance team to retain in a separate payroll archive.

Roubler integrations with Xero, MYOB, QuickBooks Online, and POS systems are configured via OAuth credentials and webhook URLs not exportable through the API. Integration configuration cannot be migrated automatically. We document the integration list (which integrations are active, which credentials are used, which webhook endpoints are configured) in the migration inventory. The customer reconfigures integrations in Crelate or a separate middleware using the documented configuration parameters.

Crelate connects to sourcing platforms including Indeed, LinkedIn, Glassdoor, and HireEZ through its integrations marketplace. Active sourcing integrations in Roubler are documented in the migration inventory. The customer reconfigures candidate sourcing integrations in Crelate during the setup phase after migration cutover.

Candidate-related events recorded in Roubler (interview schedules, assessment submissions, offer communications) map to Crelate Activity records on the relevant Contact or Job Submission. We preserve event type, timestamp, and related candidate. General HR communications tied to onboarding or employment management do not map to Crelate's activity model and are documented in the migration inventory.