Migrate your Sunrise HR Case Management data
HR service-desk platform built on Infor OS for managing employee cases, queries, and requests with SLA tracking and workflow automation across mid-market and public sector organisations.
In its favor
Why people choose Sunrise HR Case Management
The signal that keeps Sunrise HR Case Management on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Centralised case management consolidating HR interactions — reviews highlight the platform's ability to centralise employee queries, requests, and cases under one searchable system with full audit trails.
Over 20 built-in HR functions with SLA management and automatic escalations, making it suitable for shared-service HR desks managing high query volumes without custom code.
Cloud-based delivery on Infor OS with Power BI dashboards for real-time reporting, attracting organisations already invested in the Infor ecosystem.
Listed on the UK Government G-Cloud framework, making it a procurement-ready choice for public-sector HR teams requiring pre-approved supplier status.
Per-seat pricing with no modular add-ons or hidden fees, offering cost predictability compared to platforms that charge extra for SLA or analytics modules.
Limited integration ecosystem outside Infor OS — organisations not already on Infor HCM struggle to justify the lock-in when lighter HR helpdesk tools cover the same use cases at lower cost.
Custom workflow complexity escalates over time; customers report that heavily customised process rules become brittle during version upgrades and difficult to migrate.
Licensing and setup costs cited as barriers for small-to-mid organisations, with ITQlick noting Sunrise HR Case is priced higher than comparable platforms like Zenefits People Operations for similar headcounts.
Reasons to switch
Why people leave Sunrise HR Case Management
The recurring reasons buyers give for replacing Sunrise HR Case Management. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Sunrise HR Case Management 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
Sunrise HR Case Management pricing overview
Sunrise HR Case Management is priced per user per month with published estimates ranging from approximately $9 to $29/user/month depending on contract length and edition. The product is marketed as all-inclusive with no modular add-ons or hidden fees, though actual pricing is customised and requires a sales inquiry. UK public sector organisations procure via the G-Cloud framework.
Per Seat
Tier 1 of 1
$9–$29/user/month (estimates; confirm with vendor)
What's included
Need help selecting your Helpdesk?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Sunrise HR Case Management's schedule — see our quote-based pricing →
What gets migrated
Sunrise HR Case Management object support
Object-by-object support for Sunrise HR Case Management migrations. Per-pair details surface during scoping.
HR Cases
Fully supportedCases are the primary object in Sunrise HR Case Management. We map the full case record including status, priority, category, assignee, created/updated timestamps, and linked employee. Case audit history is exported as a related child table and replayed as activity log entries in the destination.
HR Queries
Fully supportedQueries are lightweight request objects tracked alongside Cases. We extract query text, submitter, assigned handler, and resolution status, and map them to equivalent request or sub-case objects in the target system.
HR Requests
Fully supportedRequests represent structured HR service requests (e.g., absence approvals, equipment requests). We map request type, custom fields, approval chain, and current stage to the destination's request or workflow object.
Employees
Mapping requiredEmployees are referenced from the integrated HRIS (Infor HCM or connected HRIS) and linked to cases as the subject. We preserve the employee identifier and core fields but flag any Infor-specific employment fields that may require re-mapping to the destination HRIS.
Agents / HR Handlers
Mapping requiredAgents are the HR staff who own and resolve cases. We map agent name, role, team assignment, and workload flags. Team structures may differ between Sunrise and the destination, requiring manual team mapping during scoping.
SLA Definitions
Mapping requiredSLAs are defined per case category and include target resolution time and breach actions. We export SLA rules as metadata and note that re-creation in the destination requires category-to-SLA mapping, as most platforms store SLAs differently.
Escalation Rules
Mapping requiredAutomatic escalation rules trigger alerts or reassignments based on SLA breach or case inactivity. We flag these as workflow automation objects that require reimplementation in the destination, as escalation logic does not export as data.
Attachments
Fully supportedDocuments attached to cases (policies, evidence, correspondence) are extracted as binary blobs. We download and re-attach them to the corresponding migrated records, preserving filenames and original upload dates.
Dashboards / Reports
Not in this platformPower BI dashboards are linked to the Infor OS reporting layer and are not exported as portable objects. We provide a data extract of the underlying metrics so the customer can rebuild reports in the destination BI tool.
Workflow Automations
Mapping requiredAutomated task assignments, notifications, and routing rules live in the Sunrise workflow engine. These require manual reconfiguration in the target system; we document the current rule logic and advise customers to engage their implementation partner to rebuild automations post-migration.
Tags / Categories
Mapping requiredCase categories and tags are exported as flat label lists. We map them to the destination's taxonomy, merging where duplicate categories exist and flagging unresolvable conflicts.
SLA Breach Records
Fully supportedHistorical SLA breach events are stored as audit entries on the case. We export breach timestamps, breached SLA name, and resolution delta as read-only data fields to preserve compliance reporting continuity.
| Object | Support | Notes |
|---|---|---|
| HR Cases | Fully supported | Cases are the primary object in Sunrise HR Case Management. We map the full case record including status, priority, category, assignee, created/updated timestamps, and linked employee. Case audit history is exported as a related child table and replayed as activity log entries in the destination. |
| HR Queries | Fully supported | Queries are lightweight request objects tracked alongside Cases. We extract query text, submitter, assigned handler, and resolution status, and map them to equivalent request or sub-case objects in the target system. |
| HR Requests | Fully supported | Requests represent structured HR service requests (e.g., absence approvals, equipment requests). We map request type, custom fields, approval chain, and current stage to the destination's request or workflow object. |
| Employees | Mapping required | Employees are referenced from the integrated HRIS (Infor HCM or connected HRIS) and linked to cases as the subject. We preserve the employee identifier and core fields but flag any Infor-specific employment fields that may require re-mapping to the destination HRIS. |
| Agents / HR Handlers | Mapping required | Agents are the HR staff who own and resolve cases. We map agent name, role, team assignment, and workload flags. Team structures may differ between Sunrise and the destination, requiring manual team mapping during scoping. |
| SLA Definitions | Mapping required | SLAs are defined per case category and include target resolution time and breach actions. We export SLA rules as metadata and note that re-creation in the destination requires category-to-SLA mapping, as most platforms store SLAs differently. |
| Escalation Rules | Mapping required | Automatic escalation rules trigger alerts or reassignments based on SLA breach or case inactivity. We flag these as workflow automation objects that require reimplementation in the destination, as escalation logic does not export as data. |
| Attachments | Fully supported | Documents attached to cases (policies, evidence, correspondence) are extracted as binary blobs. We download and re-attach them to the corresponding migrated records, preserving filenames and original upload dates. |
| Dashboards / Reports | Not in this platform | Power BI dashboards are linked to the Infor OS reporting layer and are not exported as portable objects. We provide a data extract of the underlying metrics so the customer can rebuild reports in the destination BI tool. |
| Workflow Automations | Mapping required | Automated task assignments, notifications, and routing rules live in the Sunrise workflow engine. These require manual reconfiguration in the target system; we document the current rule logic and advise customers to engage their implementation partner to rebuild automations post-migration. |
| Tags / Categories | Mapping required | Case categories and tags are exported as flat label lists. We map them to the destination's taxonomy, merging where duplicate categories exist and flagging unresolvable conflicts. |
| SLA Breach Records | Fully supported | Historical SLA breach events are stored as audit entries on the case. We export breach timestamps, breached SLA name, and resolution delta as read-only data fields to preserve compliance reporting continuity. |
Gotchas
What to watch for in Sunrise HR Case Management migrations
Issues we've hit on past Sunrise HR Case Management migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Escalation rules do not export as data
SLA metadata requires manual reconstruction
Integration dependency on Infor HRIS
UK G-Cloud procurement may restrict data residency
| Severity | Issue |
|---|---|
| High | Escalation rules do not export as data |
| Medium | SLA metadata requires manual reconstruction |
| Medium | Integration dependency on Infor HRIS |
| Low | UK G-Cloud procurement may restrict data residency |
Leaving Sunrise HR Case Management?
Where Sunrise HR Case Management customers move next
7 destinations Sunrise HR Case Management can migrate to.
How a Sunrise HR Case Management migration works
Four steps, Sunrise HR Case Management-specific
Connect
Not publicly documented in detail — Sunrise HRCM exposes both SOAP and REST APIs deployed as web services. Credentials and full reference are issued to subscribers, with sandbox access available in the test environment. into Sunrise HR Case Management. Scopes limited to read-only on the data we move.
Map
We translate Sunrise HR Case Management-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Sunrise HR Case Management quirks before production.
Migrate
Full migration with Sunrise HR Case Management rate-limit handling. Rollback available throughout.
FAQ
Sunrise HR Case Management migration FAQ
Answers to the questions buyers ask most during Sunrise HR Case Management migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Sunrise HR Case Management migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther helpdesks we support
Ready when you are
Migrate Sunrise HR Case Management.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Sunrise HR Case Management setup and destination — written quote back within a business day.