The kronos workforce central time, attendance, schedules, workforce history migration covers all four WFC operational domains: Workforce Timekeeper, Workforce Absence + Accruals, Workforce Scheduler, multi-year archive. Audit-signed chain preserved end-to-end for FLSA, state wage and union audit.
WFC's footprint is bigger than 'a time clock system.' Time, Attendance, Schedules and Workforce History each have their own data shape, retention obligation and audit chain.
Workforce Timekeeper is the flagship WFC module — punches, signed timecards, edits, approvals, comments, and the Pay Rule engine that drives FLSA overtime, shift differential, holiday premium and meal-break deduction. Workforce Absence Manager + Workforce Accruals together cover the Attendance domain: FMLA, ADA and state PFL case continuity, intermittent leave fragments, certification documents, accrual plans for PTO/sick/vacation/comp time with carryover, cap and eligibility-tier semantics. Workforce Scheduler handles published + unpublished schedules, shift templates, open shifts, swap requests, coverage gaps and fatigue-rule compliance under predictive-scheduling laws.
Workforce History — the multi-year archive — is the fourth domain and the largest by data volume. Hundreds of millions of punch rows for multi-thousand-employee deployments with 7+ years of FLSA + state wage retention. Signed timecard archive. Year-end accrual snapshots. Closed FMLA cases. Historical published schedules. Pay rule firing history for union grievance evidence. The history domain doesn't migrate to Fusion Time Card (which holds only current + recent periods) — it lands in the long-term Kronos archive on object storage with tiered hot/warm/cold storage and a query layer for downstream historical reporting.
The kronos workforce central time, attendance, schedules, workforce history migration handles all four domains in a single coherent programme with sequenced load order, per-domain reconciliation depth, sign-off-gated progress and audit-signed chain preservation. Each domain has its own crosswalk, its own reconciliation engine, its own sign-off owner. The platform orchestrates all four against the WFC API rate-limit budget and the Fusion HCM data-dependency order — workers before time cards, absence plans before balances, balances before active cases — with no domain shortchanged in the rush to cutover.
Each of the four operational domains has its own migration challenges, crosswalk patterns and reconciliation precision.
WFC Pay Rule outcomes don't simply replicate. Recalculated in Fusion's Time Repository rule engine via field-level crosswalk. Forward-going pay calculation handed to Fusion. Source punch-id preserved.
Per-worker, per-code, per-pay-group accrual balances reconciled to hundredth-of-an-hour. Dollar value (balance × rate) reconciled to the cent for SOX accrual liability sign-off.
Every active FMLA + ADA + state PFL case migrated with case-id preserved, eligibility-clock state preserved, intermittent fragments preserved, certifications referenced. Zero clock restarts.
Predictive-scheduling-law compliance preserved (Oregon Fair Workweek, NYC Fair Workweek, Seattle Secure Scheduling, SF Formula Retail, Chicago Fair Workweek). Fatigue rules carried.
Hundreds of millions of punch rows for FLSA + state wage retention. Parquet on object storage with tiered hot/warm/cold. Query layer for historical reporting. Hash-signed chain.
Every Fusion payroll line ties back to original WFC punch via preserved external reference. Pay Rule firing history preserved. Union grievance evidence defensible end-to-end.
Sequenced for Fusion HCM data dependencies — no domain shortchanged in the rush to cutover.
Workers (HDL Worker.dat), Pay Groups, Positions, Labor Account hierarchy loaded. Three-layer reconciliation per pay group. Master data sign-off before any other domain can begin loading.
Accrual Plan setup in Fusion Absence Management. Per-worker balances loaded via HDL Absence Plan Balance — reconciled to hundredth-of-an-hour. SOX accrual liability dollar value to the cent.
Historical punch archive, signed timecard archive, accrual snapshot history, leave case history loaded to long-term Kronos archive. Hash-signed Parquet partitioned by fiscal year × pay group. Query layer enabled.
Current-period punches + signed timecards loaded to Fusion Time Card via FBDI. Pay Rule outcomes recalculated in Fusion. Source punch-id preserved as Fusion external reference. Parallel-run pay cycles begin.
Active FMLA + ADA + state PFL cases migrated via HDL Absence Case with case-state preserved. Eligibility-clock high-water-mark carried. Intermittent fragments preserved. Certifications referenced. Zero clock restarts.
Published schedules forward-loaded to Fusion Workforce Scheduling (or coexistence with WFC). Predictive-scheduling compliance preserved. Final reconciliation across all four domains. Cutover sign-off.
One platform. Four domains. Sequenced load order. Per-domain reconciliation. Audit chain preserved end-to-end.
Workers before time cards, absence plans before balances, balances before active cases, archive before current period. Fusion HCM data dependencies respected.
Time at row + sum + hash, Attendance at hundredth-of-an-hour and to the cent, Schedules at shift integrity + predictive-scheduling compliance, History at hash-signed partition.
Every Fusion payroll line ties back to original WFC punch via preserved external reference. Pay Rule firing history, edit history, approvals all carried through to Fusion or archive.
Zero clock restarts for workers mid-leave. Every case migrated with state preserved. HR sign-off gate enforced before cutover.
Workforce History domain lands in tiered Parquet archive with query layer. FLSA + state wage retention chain preserved for 7+ years post-cutover.
All four domains complete with reconciliation sign-off before Kronos Private Cloud Dec 2025 or on-prem Mar 2027 EOL deadline. 4–6 weeks slack reserved pre-EOL.
The kronos workforce central time, attendance, schedules, workforce history migration covers the four WFC operational domains that together represent the bulk of any Kronos-to-Fusion migration: Time (punches via TIMESHEETITEM, signed timecards, edits, approvals, comments, pay rule outcomes); Attendance (absence tracking, occurrences, attendance points, FMLA + ADA + state PFL case continuity, accrual balances and YTD earn/take); Schedules (published + unpublished schedules, shift templates, open shifts, swap requests, coverage gaps, fatigue rules, predictive-scheduling-law compliance); Workforce History (multi-year punch archive, signed timecard archive, accrual snapshot history, leave case history, schedule history) — all migrated with audit-signed chain preserved end-to-end. Each domain has its own extraction surface, crosswalk to Fusion HCM target, reconciliation depth and sign-off owner.
Time-domain migration handles punches (TIMESHEETITEM), signed timecards, edits, approvals, comments and the Pay Rule outcomes that drove FLSA overtime, shift differential, holiday premium and meal-break deductions. Current-period punches stream via WFC REST API into Fusion Time Card via FBDI Time Card Import. Historical punch archive (multi-year, multi-million-row volumes) lands in the long-term Kronos archive for FLSA + state wage retention. Pay Rule outcomes are not simply replicated — they are recalculated in Fusion's Time Repository rule engine using the field-level crosswalk so the new system can take over forward-going pay calculation. Source punch-id is preserved as a Fusion external reference for audit chain continuity.
Attendance covers accrual balances (PTO, sick, vacation, comp time, jury, bereavement) plus FMLA, ADA and state PFL leave cases plus attendance points and occurrences. Accrual balances migrate via HDL Absence Plan Balance with per-worker, per-code, per-pay-group reconciliation to the hundredth-of-an-hour. Leave cases migrate via HDL Absence Case with case-id preserved as external reference, eligibility-clock state preserved, used/remaining hours preserved, intermittent fragments preserved, certifications referenced. The Attendance migration is one of the highest-sensitivity domains — a worker mid-FMLA-clock cannot have the clock restart; a worker with $5K of accrued PTO cannot lose a single hour. Reconciliation precision: hundredth-of-an-hour, to the cent dollar value.
Schedule-domain migration handles published + unpublished schedules, shift templates, open shifts, swap requests, coverage gaps and fatigue rules. Two target destinations depending on scope: (1) If Fusion Workforce Scheduling is in scope, published schedules forward-load to Fusion Workforce Scheduling via REST API + bulk loader. (2) If Workforce Scheduling stays on WFC during coexistence (common in retail and healthcare where the WFC shift-bidding UI is operationally critical), schedules remain in WFC and a coexistence integration feeds schedule context to Fusion HCM. Either path preserves shift-template integrity, fatigue-rule compliance (Oregon Fair Workweek, NYC Fair Workweek, Seattle Secure Scheduling, San Francisco Formula Retail, Chicago Fair Workweek), and union shift-assignment evidence.
Workforce History covers the multi-year historical archive that must be preserved for FLSA + state wage law retention: punch history (TIMESHEETITEM archive, hundreds of millions of rows for multi-thousand-employee deployments), signed timecard archive, accrual snapshot history (year-end balances per worker per code), leave case history (closed FMLA, ADA, PFL cases with full documentation chain), schedule history (historical published schedules), pay rule firing history (which rule fired against which punch with what outcome). All of this lands in the long-term Kronos archive — Parquet on object storage with tiered hot/warm/cold storage — and the kronos workforce central time, attendance, schedules, workforce history migration preserves the auditable chain from any future Fusion payroll line back to the original WFC punch in archive.
FLSA requires 3-year retention of payroll records and 2-year retention of supporting timecard data. State wage laws extend retention up to 7 years (California, New York), and predictive-scheduling laws add additional schedule-retention requirements (Oregon Fair Workweek, NYC Fair Workweek, Seattle Secure Scheduling, San Francisco Formula Retail, Chicago Fair Workweek). The kronos workforce central time, attendance, schedules, workforce history migration preserves the chain end-to-end: every Fusion Time Card row references its source WFC TIMESHEETITEM punch-id, every accrual balance ties to its source WFC accrual code with reconciliation hash, every leave case carries its source WFC case-id as external reference, every schedule shift carries its source schedule-id. The signed evidence pack is the chain DOL Wage & Hour investigators follow without reconstruction.
Union grievance defense requires a trail back to the original Pay Rule + Work Rule that drove a worker's pay calculation, with the comments and approval signatures preserved. The kronos workforce central time, attendance, schedules, workforce history migration preserves every Pay Rule firing event as audit metadata attached to the corresponding Fusion Time Card row: which Pay Rule fired, which Work Rule applied, what FLSA category was assigned, what shift differential was paid, what union-CBA reference was active. Edit history is preserved with original/edited/edit-actor/edit-timestamp attributes. Comments and approvals carry through. Sample union-grievance evidence packs are produced as part of migration sign-off, per CBA, for representative workers.
Typically yes, but the sequencing matters. Standard kronos workforce central time, attendance, schedules, workforce history migration order: (1) Master data and Pay Group setup; (2) Accrual plans and balances (Attendance accrual base); (3) Historical Workforce History archive (long-term archive landing); (4) Current-period Time data (FBDI Time Card Import for active pay period); (5) FMLA + ADA + state PFL leave cases with case-state preserved; (6) Schedules (forward-load to Fusion Workforce Scheduling or keep in WFC for coexistence). Sequencing respects Fusion HCM data dependencies — workers before time cards, absence plans before balances, balances before active cases — and parallel-run reconciliation gates apply between each step.
Book a 30-minute discovery call. We'll review your WFC operational footprint across all four domains — Timekeeper, Absence + Accruals, Scheduler, multi-year archive — and confirm a concrete domain-sequenced migration plan before the call ends.