---
title: "How do I migrate a Workday Extend app from WCPISU to…"
description: "Replace legacy WCPISU with simplified ISU in App Manager, the SMD, and orchestration credentials before you copy or redeploy."
url: https://kiweely.com/guides/workday-migrate-wcpisu-to-simplified-isu
---

# How do I migrate a Workday Extend app from WCPISU to simplified ISU?

Workday treats WCPISU as legacy. New Extend apps after October 4, 2024 must use simplified ISU. Migrate by assigning the ISU in App Manager, declaring scheme ISU in the SMD, updating PMD authType values, and creating fresh orchestration credentials. You cannot reuse the old WCPISU API client.

-   **Checked** against Workday on November 17
-   Applies to **Workday Extend**
-   3 min read
-   Published November 17
-   By Kiweely

`WCPISU` is the legacy Integration System User authentication type for Workday Extend. Workday recommends the simplified `ISU` type instead. Existing apps may keep `WCPISU`, but new apps must use simplified `ISU`. Extend apps created after October 4, 2024, including apps created from a copy, must use simplified ISU. Orchestration Builder ISU credentials already use the simplified scheme.

## What changes between WCPISU and simplified ISU

| Area | Legacy WCPISU | Simplified ISU |
| --- | --- | --- |
| SMD scheme | `WCPISU` with `appId`, `tokenHolder`, optional `checkEnvironment` | `ISU` with `username` matching App Manager |
| API client | Existing WCPISU client | New client created when you assign the ISU in App Manager |
| Reuse | — | You cannot configure simplified ISU with the old WCPISU API client |
| New apps after 2024-10-04 | Not allowed for new presentation-component apps | Required |
| ISU to app mapping | Legacy association | Multiple ISUs per app; each ISU belongs to only one app |

## Migration steps

Workday points migrators at Configure ISU Authentication in Presentation Components and Create Orchestration Credentials. The practical sequence is:

1.  Create or confirm the Integration System User with Create Integration System User. Keep Session Timeout Minutes at zero. Put the ISU in an Integration System Security Group (Unconstrained) and grant the View/Modify and Get/Put domains the app needs. Activate Pending Security Policy Changes.
2.  In App Manager, assign the ISU to the app so Workday creates the API client for that ISU. You need the WCP Integration System User Security domain for the Add Integration System User button, and Company Administrator consent on the Developer Site for non-Development tenants.
3.  Open the Site Metadata (SMD) in Code mode. Replace or add an `authTypes` entry with `scheme` set to `ISU` (case-sensitive) and `username` set to the System User name from App Manager:

```
"siteAuth": {
  "authTypes": [
    {
      "id": "isuAuth",
      "scheme": "ISU",
      "username": "Default_ISU"
    }
  ]
}
```

1.  On every PMD endpoint that used the old WCPISU auth id, set `authType` to the new `id` (`isuAuth` in the sample). Deploy the app.
2.  For orchestrations, create ISU credentials in Orchestration Settings rather than leaving a legacy WCPISU path. Workday’s Create Orchestration Credentials page lists ISU as its own type, with the ISU name in the Username expression.
3.  Do not point simplified ISU at the old WCPISU API client. Workday says that combination is not supported. Delete unused API clients only after the ISU association is removed in App Manager or the app is deleted.

## Promote and refresh after the cutover

Promoting a simplified-ISU app past Development requires the same ISU assignment and API client setup on the non-Development tenant, plus Company Administrator consent that lists those tenants on the API client. After a Production refresh into Implementation or Sandbox, those tenants associate with the Production API client. Add consent for Implementation and Sandbox on that Production client in the Console. With simplified ISU, Workday says you no longer need to worry about Implementation or Sandbox using Production credentials after refresh the way legacy WCPISU required.

Studio integrations should not borrow the simplified ISU API client. Create a separate API client and use Client Credentials for Studio.

## Failure modes

-   New app still declares `scheme: "WCPISU"`. After October 4, 2024 that is not valid for new presentation-component apps. Switch to `ISU`.
-   SMD says `ISU` but App Manager never assigned the username. The `username` must match the System User configured in App Manager.
-   You reused the WCPISU API client. Create the client through App Manager assignment instead.
-   Orchestration still authenticates with a credential that expects the old scheme. Recreate the ISU credential after the App Manager assignment.
-   Non-Development promote fails consent. Company Administrator must authorize the tenant list on the API client.

## Frequently asked questions

### Can I keep WCPISU on an old app forever?

Existing apps can continue on WCPISU. Workday strongly recommends migrating. New apps and copies created after October 4, 2024 must use simplified ISU.

### Can one ISU serve two apps?

No. You can add multiple ISUs to one app, but an ISU can be associated with only a single app.

### Does simplified ISU remove the need for page security?

No. Workday says ISU access often does not match end-user tenant security. Prefer securing pages with security domains. If a page must use ISU authentication, add application checks against the current user’s roles and groups.

## Sources checked

-   [Concept: ISU Authentication](https://developer.workday.com/documentation/GUID-cb3e0fcd-bb97-4005-8d10-3a02e88dab71-enHYPHENus/ConceptISUAuthentication)
-   [Configure ISU Authentication in Presentation Components](https://developer.workday.com/documentation/GUID-f4c6727e-f363-4786-a90d-ecc30f062872/ConfigureISUAuthenticationinPresentationComponents)
-   [Steps: Set Up ISU Authentication for Apps](https://developer.workday.com/documentation/GUID-3277fec3-24c9-41da-9840-c61b41033f28-enHYPHENus/StepsSetUpISUAuthenticationforApps)
-   [Create Integration System Users for Apps](https://developer.workday.com/documentation/GUID-f8d46604-e156-492f-a324-62ed2f6496f7/CreateIntegrationSystemUsersforApps)
-   [Declare Authentication Types in the SMD](https://developer.workday.com/documentation/nyw1530545468565/DeclareAuthenticationTypesintheSMD)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### How do I set an Integration System Security Group for an Integration System User? An Integration System Security Group is the security group built for an ISU. Create constrained or unconstrained ISSG, add the ISU as the only member type allowed, assign domain and business process permissions, and activate pending security policy changes before you run the integration.](https://kiweely.com/guides/workday-issg-for-integration-system-users)
-   [### Security Domains for Your First Workday Extend App A security domain file does nothing until you deploy, create the domain security policy, grant a security group, and activate it. Page security should use unconstrained role-based groups. Developer Agent can write the file. It does not configure the tenant.](https://kiweely.com/guides/first-workday-extend-app-security-domains)

### More guides on Extend apps and pages

[All 97 guides](https://kiweely.com/guides#extend)

-   [What is known about a December 2026 Extend model components compiler upgrade?](https://kiweely.com/guides/workday-extend-model-compiler-upgrade-2026-12)
-   [Install Ready but model components missing: refresh the Extend cache](https://kiweely.com/guides/workday-extend-refresh-model-components-cache)
-   [When must I promote Extend model components before the Friday update?](https://kiweely.com/guides/workday-extend-model-component-promotion-deadlines)
-   [When should you not add Workday Extend model components?](https://kiweely.com/guides/when-not-to-add-workday-extend-model-components)
-   [Workday Extend Model Components and the Weekly Update](https://kiweely.com/guides/workday-extend-model-components-weekly-update)
-   [The Validate and Deploy Proof Ladder for Workday Extend](https://kiweely.com/guides/workday-extend-validate-deploy-proof-ladder)
-   [Promote a Workday Extend App Past Development](https://kiweely.com/guides/workday-extend-promote-past-development-beginners)
-   [Use the Workday Extend App Catalog as an AI Jump Start](https://kiweely.com/guides/workday-extend-app-catalog-ai-jump-start)

### From the blog on Extend apps and pages

[All posts](https://kiweely.com/blog)

-   [From Business Brief to Tested Workday Extend App: Why Zero Validation Errors Is Not Proof](https://kiweely.com/blog/why-workday-extend-validation-is-not-testing)
-   [Workday Extend Graph API and AppHub Promotion: Moving Apps From Development to Sandbox](https://kiweely.com/blog/workday-extend-graph-api-and-apphub-promotion)
-   [Desktop apps for Extend and Studio](https://kiweely.com/blog/desktop-app-for-workday-extend-and-studio-developers)

## Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.
