Migrating GL History into Workday: Journals vs. Summary Balances

Every Workday Financials implementation faces this strategic decision: how much general ledger history should move into the new system? The answer is not purely technical -- it shapes reporting capabilities, audit readiness, and migration complexity for years after go-live. The two primary approaches are migrating detailed journal entries (every individual posting) or migrating summary balances (period-end totals by account). Most organizations need a hybrid, but understanding the trade-offs is essential before choosing.

---

The Core Trade-Off

Detailed journals give you full drill-down capability in Workday. An auditor or analyst can trace any balance back to its constituent transactions without switching to the legacy system. The cost: volume (potentially millions of rows), complexity (every journal must map correctly to the new chart of accounts), and risk (more data means more potential errors).

Summary balances give you period-end totals that support trend reporting and year-over-year comparisons without the volume burden. The cost: no drill-down capability within Workday for historical periods, continued dependence on the legacy system for transaction-level detail, and potential audit friction when auditors need to trace historical transactions.

---

What Workday Expects

Workday's journal import mechanism accepts both approaches but treats them differently:

For detailed journals: Each journal entry must balance (debits equal credits within the entry), reference a valid accounting date within a Workday fiscal period, map to valid ledger accounts in the target chart of accounts, and include required worktag references. Workday processes journals through its full accounting engine, meaning they appear in all standard reports and support complete drill-down.

For summary balances: Workday accepts balance loads as beginning balance journal entries. These are special journal entries posted to the first day of the first open period that set account balances without individual transaction detail. They appear in balance reports but do not support transaction-level drill-down.

For both: The opening trial balance must reconcile with the legacy system's closing trial balance as of the cutover date. This reconciliation is the single most scrutinized deliverable in any financial migration.

---

When Detailed Journals Are Necessary

• Audit requirements: If auditors need transaction-level detail for open audit periods (typically the current year plus two prior years), those periods must migrate as detailed journals
• Grant reporting: Grant-funded organizations (FQHCs, nonprofits, government contractors) often need transaction detail for the full grant period, which may span five or more years
• Legal and regulatory holds: Litigation holds or regulatory investigations may require preserving transaction detail for specific periods
• Operational reporting: If business users need to analyze historical spending patterns at the transaction level within Workday (rather than switching to a legacy system or data warehouse)
• Legacy system decommission: If the organization plans to decommission the legacy ERP immediately after go-live, all required history must live in Workday

---

When Summary Balances Are Sufficient

• Old history: Periods older than three years where audit risk is minimal and operational reporting needs are served by trend data rather than transaction detail
• High-volume legacy systems: When the legacy system contains decades of history with hundreds of millions of journal lines, migrating everything is neither practical nor valuable
• Data warehouse strategy: If the organization maintains a data warehouse or analytics platform that retains historical detail, Workday does not need to duplicate it
• Clean-start philosophy: Some organizations view the Workday implementation as an opportunity to start fresh, with historical detail available in an archive system on demand

---

The Hybrid Approach (Most Common)

Most organizations adopt a hybrid strategy:

• Current year + 2 prior years: Detailed journals (satisfies standard audit requirements)
• Years 3-5: Summary balances by period (supports trend reporting without volume burden)
• Years 5+: Opening balance only (a single balance entry that establishes the starting point)

This hybrid reduces volume by 70-80% compared to migrating all detail while preserving drill-down capability for the periods most likely to be audited or analyzed.

In our engagement with a multi-entity healthcare organization, we migrated 1.9 million journal rows covering three years of detailed history across seven legal entities, with summary balances for the two prior years. This hybrid approach provided full audit coverage while keeping the migration within a twelve-week timeline.

---

Validation Requirements at Scale

Regardless of approach, the reconciliation must prove that Workday's balances match the legacy system's balances as of the cutover date. For detailed journals, this means:

Entry-level validation: Every journal entry must balance internally (debits equal credits). This sounds trivial but at 1.9 million rows, even a 0.01% error rate means 190 unbalanced entries to investigate.

Period-level validation: The sum of all journals within each fiscal period must produce the same period-end balance as the legacy system. This catches mapping errors where transactions land in the wrong period.

Account-level validation: Each account's running balance in Workday must match the legacy system at every period boundary. This catches mapping errors where transactions land in the wrong account.

Entity-level validation: Each legal entity's total assets must equal total liabilities plus equity. Intercompany eliminations must net to zero at the consolidated level.

Cross-period continuity: The closing balance of period N must equal the opening balance of period N+1. This catches gaps or overlaps in the migration.

AssistNow's ValidateIQ platform performs all five levels of validation simultaneously during migration, achieving 98.3% auto-reconciliation with all revenue validated before any data enters the production tenant.

---

Period Mapping Challenges

One of the most common sources of reconciliation errors is period mapping. Legacy systems often use different fiscal calendars, period structures, or cutoff conventions than Workday. Common issues include:

• 13-period legacy calendars mapping to Workday's 12-period structure
• Adjustment periods in the legacy system that have no direct equivalent in Workday
• Different month-end conventions (last calendar day vs. last business day)
• Fiscal year changes during the history window (the legacy system changed its fiscal year in 2023, creating a short period)

AI-assisted migration handles period mapping by analyzing the actual posting dates and period assignments in the source data, then applying temporal rules that account for calendar differences. This eliminates the manual mapping table that traditionally requires weeks of analyst time to build and validate.

---

Frequently Asked Questions

Can we change our minds after go-live and migrate more history later?
Yes, but it is significantly more complex. Post-go-live journal loads must not disrupt the live accounting. Most organizations that change their minds wish they had migrated more detail upfront.

How do summary balances affect Workday reporting?
Summary balances appear in balance sheet and income statement reports as period totals. They support trend analysis and year-over-year comparisons. They do not appear in transaction detail reports or support drill-down from balances to individual postings.

What about sub-ledger detail (AP, AR, fixed assets)?
Sub-ledger detail (open invoices, outstanding receivables, asset registers) typically migrates as transactional data regardless of the GL history strategy. The GL history decision applies to the summarized journal entries, not the operational sub-ledger records.

How long should we keep the legacy system accessible after go-live?
Industry standard is 18-24 months of read-only access to the legacy system after go-live. Organizations that migrate detailed history for all audit periods can shorten this; organizations that migrate only summary balances should plan for longer access.

---

Key Takeaways

• The journals vs. balances decision is strategic, not technical -- it determines reporting capability and legacy system dependency for years.
• Most organizations use a hybrid: detailed journals for 2-3 years, summary balances for older periods.
• Validation at scale requires five levels of reconciliation (entry, period, account, entity, cross-period continuity).
• Period mapping differences between legacy and Workday calendars are the most common source of reconciliation errors.
• AI-assisted validation achieves 98.3% auto-reconciliation even at 1.9 million rows across multiple entities.

---

AssistNow's ValidateIQ platform handles both detailed journal and summary balance migrations with automated multi-level reconciliation. Contact us to discuss your GL history migration strategy.