Migrate your empeon data

Employee profiles are the primary record in Empeon Workforce. Standard fields include name, contact info, employment status, job title, department, hire date, and pay rate. We migrate all standard fields 1:1. Custom Fields (Input and Checkbox) are appended as key-value metadata on each employee record.

Empeon supports two Custom Field types: free-text Input fields and yes/no Checkbox fields. We enumerate all active Custom Fields during scoping and map them to equivalent properties on the destination Employee object. Checkbox fields translate to Boolean or flag fields; Input fields become free-text strings.

Time entries, clock punches, and scheduling data (Employee View and Daily View) are stored within Empeon Workforce. We export attendance records by employee and date range. Advanced Scheduling assignments are treated as structured schedule-shift records.

Payroll registers, pay periods, gross/net pay amounts, and deduction line items are available via Live Report exports. We chunk exports by pay period to preserve historical context. Tax withholding amounts and deduction codes may require mapping to destination field names.

Bank account routing numbers and account numbers are stored per employee for direct deposit. We flag these as sensitive fields, encrypt them in transit during migration, and suppress them from any non-encrypted reporting outputs.

Benefit plans, carrier assignments, coverage tiers, and enrollment dates are stored per employee. We export enrollment records as structured objects. Plan names and carrier codes often differ between source and destination systems and require explicit mapping.

PTO, sick leave, and other accrual balances are tracked per employee with effective-dated change history. We preserve current balance, accrual rate, and carryover rules. Historical balance snapshots are included where available via accrual reports.

Documents attached to employee profiles (offer letters, performance reviews, certifications) may be stored in Empeon's document management system. We export file metadata and binary content where accessible via the ESS Hub or admin interface. File type and naming conventions vary across organizations.

Standard Reports are tied to specific features and can be configured for date ranges. We export report definitions and result sets. Row-level data is mapped to destination equivalents; report formatting and column layouts are not preserved.

Live Reports support grouping, static columns, and real-time export. We extract the data rows as structured output. Grouping hierarchy and custom column ordering are not transferred; only the underlying row data is migrated.

Organization-level configuration (departments, cost centers, job titles, pay grades, approval workflows) is stored in the Company tab. We export the current configuration state. Settings that reference employee IDs require re-linking post-migration.

Employee Self-Service Hub access is tied to the email address stored in the employee profile. If email addresses change during migration, employees must re-register their ESS accounts. We document this dependency in the pre-migration scope report.