Migrate your Roubler data
All-in-one workforce management platform spanning recruiting, onboarding, rostering, time tracking, and payroll for mid-to-large teams. Most pre-configured for Australian employment law and integrates natively with Xero and MYOB.
In its favor
Why people choose Roubler
The signal that keeps Roubler on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Mid-market teams with complex rostering choose Roubler because it handles demand-based scheduling tied directly to POS sales data, automatically aligning shifts against trading volumes.
Organizations already using Xero or MYOB for accounting pick Roubler for its native, bidirectional payroll sync that eliminates duplicate data entry across both platforms.
Businesses migrating from paper-based or spreadsheet scheduling choose Roubler for its single-platform alternative to juggling separate HR, rostering, and payroll tools.
The platform's always-on compliance tooling appeals to operators in regulated markets who want built-in award interpretation and statutory entitlement calculations.
Companies with high casual or part-time worker ratios value Roubler's FTE-based position definition that handles headcount-to-hours conversions automatically.
Customer support scores poorly (2.8/5) with users reporting slow response times and difficulty reaching knowledgeable staff for complex payroll or compliance queries.
Pricing is opaque and negotiated per contract with no public tier structure, making it hard for teams to budget or compare value before committing.
The API is still being expanded and does not yet cover all object types, limiting automation options and making migration engineering dependent on undocumented endpoints.
Australian-centric pre-configurations frustrate teams operating in the UK, South Africa, or other markets who must override defaults that do not match local employment law.
Teams outgrow the platform when they need granular custom objects or workflow automation beyond Roubler's templated approach to HR processes.
Reasons to switch
Why people leave Roubler
The recurring reasons buyers give for replacing Roubler. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Roubler fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Roubler pricing overview
Roubler prices on a per-employee-per-month basis with adjustments for pay-run frequency. No public pricing tiers are published and no free trial is available. Historical invoices or direct sales quotes are required to establish a cost baseline. Setup, data migration, and training fees are negotiated separately and are not visible in base pricing.
Basic
Tier 1 of 3
Not publicly published — custom quote based on employee count and pay-run frequency
What's included
Need help selecting your HRMS?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Roubler's schedule — see our quote-based pricing →
What gets migrated
Roubler object support
Object-by-object support for Roubler migrations. Per-pair details surface during scoping.
Employees
Fully supportedEmployee records are the primary object in Roubler. Core fields (name, contact, employment type, start date, position assignment) are stable and exportable via the API. We map all active and terminated employee records and preserve employment type as a filterable attribute.
Positions
Fully supportedPositions define roles allocated a set of tasks and an FTE value. Export is straightforward. When migrating to a destination that does not have a separate Position object, we merge position data into the employee record as a custom property.
Rosters / Shifts
Mapping requiredRoster and shift data includes time, location, and assigned employee. We extract full roster history but flag open shifts and provisional assignments that may need review before import. Demand-based rostering data from POS integrations is mapped separately.
Leave Balances
Mapping requiredLeave entitlements, accrual history, and current balances are exportable. We preserve effective dates and accrual rates but note that leave rules vary by award or employment agreement, so destination systems may require rule reconfiguration.
Timesheets
Mapping requiredTimesheet data links to rostered shifts and may include clock-in/out events. We extract timesheet records and map hours worked against the relevant pay period. Timesheets linked to locked payroll runs are flagged as read-only.
Payroll Runs
Mapping requiredPayroll runs are tied to timesheets and leave approvals in a locked audit trail. We export run summaries and gross/net amounts but note that payroll data is sensitive and may require redaction or consent handling during migration.
Onboarding Records
Mapping requiredOnboarding records include tasks, document collection, and employee setup steps. We extract the current state of each onboarding workflow but note that in-progress tasks may not transfer meaningfully to a new system with different workflow engines.
Integrations
Mapping requiredRoubler connects to Xero, MYOB, QuickBooks Online, Workable, and POS systems. Integration configuration (webhook URLs, credentials, mapping rules) is not exportable via the API and must be reconfigured manually in the destination platform.
Custom Fields
Mapping requiredRoubler supports custom fields on employee and position objects. We export custom field names and values as flat key-value pairs. Destination mapping requires manual alignment of field names and data types.
Documents
Not in this platformEmployee documents (contracts, IDs, certifications) are stored as attachments in Roubler. The platform does not expose a document download endpoint via the public API, so we cannot guarantee migration of binary file assets. Documents must be exported manually or via a screen-scrape approach.
| Object | Support | Notes |
|---|---|---|
| Employees | Fully supported | Employee records are the primary object in Roubler. Core fields (name, contact, employment type, start date, position assignment) are stable and exportable via the API. We map all active and terminated employee records and preserve employment type as a filterable attribute. |
| Positions | Fully supported | Positions define roles allocated a set of tasks and an FTE value. Export is straightforward. When migrating to a destination that does not have a separate Position object, we merge position data into the employee record as a custom property. |
| Rosters / Shifts | Mapping required | Roster and shift data includes time, location, and assigned employee. We extract full roster history but flag open shifts and provisional assignments that may need review before import. Demand-based rostering data from POS integrations is mapped separately. |
| Leave Balances | Mapping required | Leave entitlements, accrual history, and current balances are exportable. We preserve effective dates and accrual rates but note that leave rules vary by award or employment agreement, so destination systems may require rule reconfiguration. |
| Timesheets | Mapping required | Timesheet data links to rostered shifts and may include clock-in/out events. We extract timesheet records and map hours worked against the relevant pay period. Timesheets linked to locked payroll runs are flagged as read-only. |
| Payroll Runs | Mapping required | Payroll runs are tied to timesheets and leave approvals in a locked audit trail. We export run summaries and gross/net amounts but note that payroll data is sensitive and may require redaction or consent handling during migration. |
| Onboarding Records | Mapping required | Onboarding records include tasks, document collection, and employee setup steps. We extract the current state of each onboarding workflow but note that in-progress tasks may not transfer meaningfully to a new system with different workflow engines. |
| Integrations | Mapping required | Roubler connects to Xero, MYOB, QuickBooks Online, Workable, and POS systems. Integration configuration (webhook URLs, credentials, mapping rules) is not exportable via the API and must be reconfigured manually in the destination platform. |
| Custom Fields | Mapping required | Roubler supports custom fields on employee and position objects. We export custom field names and values as flat key-value pairs. Destination mapping requires manual alignment of field names and data types. |
| Documents | Not in this platform | Employee documents (contracts, IDs, certifications) are stored as attachments in Roubler. The platform does not expose a document download endpoint via the public API, so we cannot guarantee migration of binary file assets. Documents must be exported manually or via a screen-scrape approach. |
Gotchas
What to watch for in Roubler migrations
Issues we've hit on past Roubler migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Roubler was acquired by MYOB — data residency and support continuity are migration-critical
No public pricing or free trial — migration budget must be negotiated blind
API is incomplete and expanding — endpoint availability varies by object
Australian-centric defaults may persist in international deployments
Document attachments are not accessible via the public API
| Severity | Issue |
|---|---|
| High | Roubler was acquired by MYOB — data residency and support continuity are migration-critical |
| Medium | No public pricing or free trial — migration budget must be negotiated blind |
| Medium | API is incomplete and expanding — endpoint availability varies by object |
| Low | Australian-centric defaults may persist in international deployments |
| High | Document attachments are not accessible via the public API |
Leaving Roubler?
Where Roubler customers move next
5 destinations Roubler can migrate to.
How a Roubler migration works
Four steps, Roubler-specific
Connect
OAuth 2.0 (Auth0) into Roubler. Scopes limited to read-only on the data we move.
Map
We translate Roubler-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Roubler quirks before production.
Migrate
Full migration with Roubler rate-limit handling. Rollback available throughout.
FAQ
Roubler migration FAQ
Answers to the questions buyers ask most during Roubler migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Roubler migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther HR systems we support
Ready when you are
Migrate Roubler.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Roubler setup and destination — written quote back within a business day.