UKG Pro Back Office to UKG Pro Web Payroll Migration
Back Office payroll is being retired, which puts earnings codes, deduction codes, tax setup, and year-to-date accumulators in scope on a vendor-set timeline. Settle maps them into UKG Pro Web and reconciles every balance before the first live pay run.
Working with enterprise teams on active migration programs
Days
to production-ready mappings
Roughly half
the cost of consulting-led delivery
Every row
validated before go-live
Enterprise migrations routinely run months behind schedule. Yours doesn't have to.
This guide is for VPs of IT, data architects, and migration leads at companies moving data from UKG Pro Back Office to UKG Pro Web — whether you're scoping, planning, or mid-program.
UKG Pro Back Office holds payroll configuration in its own structure: earnings and deduction codes scoped by pay group and company, tax setup, general ledger mappings, and the year-to-date accumulators behind every W-2. UKG Pro Web organizes the same payroll domain differently. Settle reads the Back Office configuration as it actually exists, maps it into UKG Pro Web, and reconciles the resulting balances to the penny.
Based on the founding team's enterprise migration experience
Last updated July 2026
How Settle automates your UKG Pro Back Office to UKG Pro Web migration
Settle profiles Back Office payroll configuration against actual payroll history, so the earnings codes, deduction codes, and pay groups genuinely in use are the ones mapped into UKG Pro Web, and dormant configuration is identified rather than inherited.
Year-to-date earnings, tax, and deduction accumulators are migrated with penny-level reconciliation against Back Office totals at the employee level, so a mid-year cutover does not put W-2 accuracy at risk.
Tax setup and per-employee elections are mapped with jurisdiction associations checked, so withholding is verified before the first live run rather than discovered in it.
General ledger mappings and pay group structure are inventoried up front, and Settle produces the evidence finance needs to confirm payroll posts to the same accounts after the move.
Get your UKG Pro Back Office to UKG Pro Web mapping analysis — see results in under an hour
Migration timeline: manual vs. Settle
Traditional approach
Timeline
3–6 months
Estimated cost
$75K–$250K
Team size
3–6 consultants
Typically requires
×Manual field mapping in spreadsheets
×Custom ABAP/SQL extraction scripts
×3–5 mock migration cycles
×Dedicated source system consultants
×Manual reconciliation testing
With Settle
Enterprise benchmarksTimeline
Days
Estimated cost
A fraction of consulting cost
Team size
1–2 internal resources
Included
✓Schema profiling & analysis
✓AI-generated field mappings
✓Transformation SQL
✓Validation & readiness reports
✓Production-ready load files
Common challenges migrating from UKG Pro Back Office to UKG Pro Web
Earnings and deduction code mapping
Back Office earnings and deduction codes are scoped by pay group and company, and most installations carry codes that are no longer used alongside the ones that are. Every active code has to map into UKG Pro Web with its calculation behavior intact. Settle profiles which codes actually appear in payroll history, so dead configuration is not carried forward by default.
Explore related migrations →Year-to-date accumulators
If cutover happens mid-year, year-to-date earnings, taxes, and deductions have to transfer exactly, because W-2 accuracy depends on them. These are the balances most often reconciled by hand, and the least tolerant of a rounding difference.
Explore related migrations →Tax setup
Federal, state, and local tax configuration, along with per-employee elections, has to arrive intact and correctly associated. A tax code attached to the wrong jurisdiction produces a correct-looking paycheck with the wrong withholding, which is rarely caught before a filing deadline.
Explore related migrations →General ledger mappings
GL mappings determine where payroll lands in the financial statements. They are usually owned by finance rather than by payroll, which is why they get discovered late. Settle inventories them as part of the initial profile rather than at the end.
Explore related migrations →Pay group structure
Pay groups drive calendars, cutoffs, and which configuration applies to whom. Restructuring them during a forced migration is tempting, and it is the most common way a bounded project turns into a long one.
Explore related migrations →UKG Pro Back Office to UKG Pro Web field mapping — what data moves
11 data objects typically migrated
| Source Object | → | Target Object |
|---|---|---|
| Earnings Code | → | Earnings Code |
| Deduction Code | → | Deduction Code |
| Tax Setup | → | Tax Setup |
| Employee Tax Election | → | Employee Tax Election |
| YTD Earnings Accumulator | → | YTD Earnings Balance |
| YTD Tax Accumulator | → | YTD Tax Balance |
| YTD Deduction Accumulator | → | YTD Deduction Balance |
| Employee Payroll Record | → | Employee Payroll Record |
| Pay Group | → | Pay Group |
| GL Mapping | → | GL Mapping |
| Payroll History | → | Payroll History |
Typical enterprise migrations include 500K–10M+ records across these objects. Settle handles profiling and mapping at enterprise scale.
The cost of manual UKG Pro Back Office to UKG Pro Web migration
The move from UKG Pro Back Office to UKG Pro Web is driven by the retirement of Back Office payroll, not by a decision to change platforms. That makes it a compliance-shaped project rather than a transformation one. The target is fixed, the timeline is set outside your organization, and the definition of success is that pay and tax come out identical on the other side.
Payroll migrations are unforgiving in a way most data migrations are not. An employee record that lands slightly wrong in a CRM is an inconvenience. An earnings code that maps wrong produces an incorrect paycheck and a corrected W-2. Earnings and deduction codes, tax setup, pay groups, general ledger mappings, and year-to-date accumulators all have to move together and tie out against the source before the first live run.
Most organizations run this through a UKG partner over three to six months. The bulk of that time is not configuration. It is parallel payroll runs, reconciling gross-to-net differences employee by employee until the two systems agree.
Consulting-led delivery for migrations in this class typically runs $75K–$250K. Settle prices it fixed and scoped — read the full cost breakdown. For HR and payroll paths specifically, see the UKG migration guide.
Frequently asked questions
Exceptions surface before the first load, not after the third.
Built by the team that ran Fortune 500 migrations by hand. Currently onboarding enterprise design partners on active migration programs.
Ready to migrate from UKG Pro Back Office to UKG Pro Web?
Tell us about your migration and we'll show you how Settle can help.
No commitment required. We'll review your migration scope and share a preliminary assessment within 48 hours.