Healthcare Data Conversion - ValidateIQ

AI-Native Workday Migration for a Multi-Entity FQHC

How a nonprofit healthcare group with 7 legal entities migrated from Dynamics GP to Workday Financials - with 533 cost centers loaded, zero failures, and 100% of revenue in revenue lines validated before loading

533
Cost Centers, 0 Failures
70K+→164
Legacy Accounts Consolidated
98.3%
Dollars Auto-Reconciled
7
Entities, One Pipeline

The Client

A nonprofit healthcare group operating 7 legal entities - clinics, pharmacies, and supporting organizations - migrating from Microsoft Dynamics GP to Workday Financials. Like most multi-entity finance teams, they carried years of segmented GL history and an idiosyncratic chart that had grown to over 70,000 account combinations across the group.

The Challenge

The legacy general ledger had to become a clean Workday Foundation Data Model: a unified chart of accounts, cost centers, spend and revenue categories, and the worktag design to tag every transaction - then load it all into Workday. Done the traditional way, this is months of consultant-led mapping in spreadsheets and EIB templates, with reconciliation discovered late, in the tenant. For a lean nonprofit finance team, that cost and timeline were painful.

As a healthcare organization handling PHI, the traditional approach also meant the most sensitive data would flow through the widest exposure surface - spreadsheets, email, and consultant laptops with identities in the clear.

The AssistNow Approach: Derive, Validate, Load

AssistNow applied ValidateIQ - its AI-native migration platform - to derive, migrate transaction data, validate, and load directly into Workday:

  • Derived the chart from the data. Assessed 70,560 segmented GL rows to distill a unified 164-account chart - the accounts the group actually uses, not its full historical tail.
  • Designed worktags from behavior, validated against the financials. Proposed revenue and spend categories from how each account is actually used, then reconciled them to the client's own board income statement - closing gaps the legacy data left open (including the group's single largest revenue account which had no category in the legacy data).
  • Reconciled cost centers automatically. Matched 189 legacy GL cost-center segments to the organization's HR-system departments, covering 98.3% of journal dollars, with the rest flagged for quick human review.
  • Migrated transaction history. Converted journal postings, GL balances, and open AP/AR/PO data into Workday-ready formats, reconciled against source totals, and loaded alongside the foundation data.
  • Loaded directly into Workday. Posted companies, cost centers, the chart, the revenue-category hierarchy, and transaction data straight into the Workday tenant over its web services - no EIB round-trips - with humans approving each proposal.

Results

  • 533 cost centers loaded into the Workday tenant - zero failures.
  • 164-account unified chart loaded as a dedicated account set, verified by reading it back from Workday.
  • 11 revenue categories + a 4-node hierarchy mapped to the client's board financial statement, loaded and verified.
  • 100% of revenue in revenue journal lines automatically tagged with the correct category and cost-center worktags - validated before loading, with zero untagged.
  • One pipeline reused across all 7 entities - built once, repeatable.

Trust Architecture

Design never sees PHI
Chart and worktag design derived from de-identified account structure.
Irreversible PII masking
Employee names masked with non-reversible tokens before any human review.
Hash-attested sign-off
Approver ≠ submitter. Attested to a cryptographic hash. Tamper-evident.
Machine-to-machine load
Direct to Workday over TLS. No workbooks emailed. Smaller surface.

Honest Scope

This engagement automated the data conversion and FDM design. Remaining go-live steps - submitting the legal entities, loading spend categories via Workday's EIB, and granting the integration user journal-posting permission plus fiscal/ledger setup - are standard Workday configuration handled as part of delivery. AssistNow is a Workday partner; this method makes the migration faster and lower-risk, it doesn't skip the expert work.

Planning a Multi-Entity Workday Migration?

Give us one of your legal entities. We'll derive its chart and worktags, validate them against your financials, and show you the result - before you commit.