# Customize migration plan for WebSphere traditional workloads

> [!IMPORTANT]
> **Important:** The `websphere-traditional` plugin is now deprecated. For existing customers, this plugin is still supported till December 2023, after which it will no longer be available. If you're new to WebSphere workload modernization, then use the `websphere-container` plugin with the Migrate to Containers CLI instead.

## Before you begin

This topic assumes that you've already
[created a migration](https://docs.cloud.google.com/migrate/containers/docs/m2c-cli/create-a-migration-plan.md.txt)
and have the migration plan file.

## Edit the migration plan

After you have copied the file system and analyzed it, you can find the
migration plan in the new directory that is created in the specified output
path: <var translate="no">ANALYSIS_OUTPUT_PATH</var>/`config.yaml`.

Edit the migration plan as necessary and save the changes.

Review your migration plan's details and guiding comments to add information as
needed.

Specifically, consider edits around the following sections.

## Select applications

On the migration plan, the application field represents the applications to migrate.
If you do not want to migrate all applications, you can remove them.

    applications:
    - appName: hello-world-servlet-ear
      httpEndpoints:
      - httpPort: 9080
        httpsPort: 9443
        id: defaulthttpendpoint
      image:
        name: hello-world-servlet-ear
      path: /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/config/cells/m4a-twas-ndNode01Cell/applications/Hello-World-Servlet.ear
    ...
    - appName: commons-ejb-ear-provided-ear
      httpEndpoints:
      - httpPort: 9080
        httpsPort: 9443
        id: defaulthttpendpoint
      image:
        name: commons-ejb-ear-provided-ear
      path: /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/config/cells/m4a-twas-ndNode01Cell/applications/commons-ejb-ear-provided.ear
      sharedLibraries:
      - /opt/IBM/WebSphere/AppServer/sharedJars/commons-io-2.8.0.jar

## Set the scanner options

In the migration plan, the `scannerOptions` field represents the argument to pass
to the [IBM WebSphere Application Server Migration Toolkit for Application Binaries](https://www.ibm.com/support/pages/migration-toolkit-application-binaries).
You can edit the arguments.

    scannerOptions:
      # Setting 'includeSensitiveData: true' will upload sensitive data, if exists, such as private keys, to the artifacts repository
      includeSensitiveData: false
      sourceAppServer: was90

> [!NOTE]
> **Note:** In order to collect sensitive data, in the migration plan, under `scannerOptions`, modify the value of `includeSensitiveData:` to be `true`. Notice that `set includeSensitiveData: true` will cause uploading sensitive artifacts into the user repository. On `liberty` and `openliberty`, the sensitive data will be stored in a secret file artifact that is used when building app container.

## What's next

- Learn how to [execute the migration](https://docs.cloud.google.com/migrate/containers/docs/m2c-cli/execute-the-migration-plan.md.txt).