Workday to Databricks

fa source inspect workday
fa source plan workday --variant workday_hcm
fa source plan workday --variant workday_reports --json

Airlift inventories Workday business objects, custom reports and RaaS, EIB integrations, effective-dated history, security domains, calculated fields, and downstream consumers. The ingestion adapter uses approved reports, APIs, or managed routes and returns pagination, watermark, correction, deletion, restart, and freshness evidence.

Developer acceptance path

• Map business-object identifiers, references, effective dates, and security-filter behavior to target contracts.
• Register custom reports, calculated fields, Studio integrations, attachments, and effective-dated correction behavior as explicit objects or residue.
• Validate object counts, history completeness, reference integrity, access-filter behavior, and accepted HR or finance totals independently.
• Mint certificates only from admitted provider runs; cut over reports and consumers in a frozen, approved wave.
• Build governed workforce data products, Delta history, Unity Catalog policies, Lakeflow jobs, and Databricks SQL models as a separate modernization release.

The pack is cataloged. Credentials remain in the connector platform; Airlift stores only an opaque reference.

Complete developer command sequence

Generate this exact recipe from the installed CLI so the guide and executable surface stay in sync:

fa source recipe workday
fa source recipe workday --variant workday_hcm --json > .airlift/workday-recipe.json

The App is engagement-aware. Workday appears under Active sources only after the source estate is added to an active engagement. The menu is derived from governed engagement scope; installing Airlift does not expose unrelated source pages.

Every remote mutation below requires --host, --org, authenticated workspace identity, and a stable --idempotency-key. JSON request files contain identifiers, artifact references, and opaque credential references—never passwords, tokens, or connection strings. Run fa <resource> <operation> --help for the current schema and exit semantics.

0. Inspect the source contract

fa source inspect workday --json > .airlift/workday-profile.json
fa source plan workday --variant workday_hcm --json > .airlift/workday-capability-plan.json

Expected artifacts:

• .airlift/workday-profile.json
• .airlift/workday-capability-plan.json

Open Engagements → active engagement in the App. This stage is visible at /engagements after replacing the placeholder ID with the governed engagement ID.

1. Create governed scope and connection references

fa engagement create --file engagement.json --idempotency-key migration-create-v1
fa estate register --file workday-estate.json --idempotency-key workday-estate-v1
fa connection register --file workday-connection.json --idempotency-key workday-connection-v1
fa engagement update --file workday-scope.json --idempotency-key workday-scope-v1
fa engagement preflight <engagement-id>

Expected artifacts:

• Governed engagement
• Source estate
• Opaque connection binding

Open Engagements → active engagement in the App. This stage is visible at /engagements/<engagement-id> after replacing the placeholder ID with the governed engagement ID.

2. Assess and accept inventory

fa assessment start --file workday-assessment-start.json --idempotency-key workday-assessment-start-v1
fa assessment status <assessment-id> --json
fa assessment record --file workday-assessment-record.json --idempotency-key workday-assessment-record-v1
fa assessment accept --file workday-assessment-accept.json --idempotency-key workday-assessment-accept-v1
fa inventory list --estate-id <estate-id> --json

Expected artifacts:

• Assessment report reference
• Normalized inventory
• Dependency graph

Open Engagements → active engagement in the App. This stage is visible at /engagements/<engagement-id>/sources/workday after replacing the placeholder ID with the governed engagement ID.

3. Implement the admitted source adapter

No source-specific executable compiler exists in this release. Continue with assessment, governed work, and an admitted adapter; Airlift does not invent executable output.

Expected artifacts:

• Capability plan and adapter requirements only

Open Engagements → active engagement in the App. This stage is visible at /engagements/<engagement-id>/artifacts after replacing the placeholder ID with the governed engagement ID.

This source is cataloged or assessable but has no source-specific executable compiler in the installed Airlift generation.

4. Convert, move, and remediate

fa plan generate --file workday-migration-plan.json --idempotency-key workday-plan-v1
fa conversion batch create --file workday-batch.json --idempotency-key workday-batch-v1
fa conversion batch start --file conversion-batch-start.json --idempotency-key conversion-start-v1
fa residue list --engagement-id <engagement-id>
fa transfer plan --file workday-transfer.json --idempotency-key workday-transfer-v1
fa transfer run <transfer-id> --idempotency-key transfer-run-v1
fa transfer reconcile <transfer-id> --idempotency-key transfer-reconcile-v1

Expected artifacts:

• Target artifacts
• Residue cases
• Transfer checkpoints
• Reconciliation evidence

Open Engagements → active engagement in the App. This stage is visible at /engagements/<engagement-id>/runs after replacing the placeholder ID with the governed engagement ID.

5. Validate independently and inspect discrepancies

fa validation run --file workday-validation.json --idempotency-key workday-validation-v1
fa validation status <validation-execution-id> --json
fa discrepancy list --engagement-id <engagement-id>
fa artifact list --engagement-id <engagement-id>

Expected artifacts:

• Provider run references
• Readiness evidence
• Discrepancies

Open Engagements → active engagement in the App. This stage is visible at /engagements/<engagement-id>/runs after replacing the placeholder ID with the governed engagement ID.

6. Certify, cut over, and export evidence

fa certificate list --object-id <object-id>
fa cutover status <wave-id> --json
fa evidence list --engagement-id <engagement-id>
fa evidence export --file workday-evidence-export.json --idempotency-key workday-evidence-export-v1

Expected artifacts:

• Migration certificates
• Cutover evidence
• Content-digested evidence export

Open Engagements → active engagement in the App. This stage is visible at /assurance after replacing the placeholder ID with the governed engagement ID.

Runway executes releases; Experiments owns validation verdicts; Airlift owns migration readiness and cutover policy.

What developers see in the App

The contextual source workspace shows the accepted estate and the factory stages for this engagement. Artifacts displays immutable references, content digests, media types, and provider lineage. Runs displays assessment, conversion, transfer, validation, and deployment executions without treating a provider's success as an Airlift verdict.

View full size

These are automated captures from public synthetic engagements. The source workspace is specific to Workday; no unrelated source is presented as its migration journey. For sources without an evidence-backed journey, the image demonstrates setup, navigation, and developer entry points only—not a live connection, converted output, or certified migration. No client data, credentials, workspace hostnames, or internal deployment identifiers are embedded in the images.