anchor.diff:  +
   Even if the pods are in a *Running* state, a high restart count might indicate underlying problems.
   
  -* [ ] You have deleted old images by running the following command:
  -+
  -[source,terminal]
  -----
  -$ oc adm prune images
  -----
  -
  +* [ ] You have removed old builds, deployments, and images from each namespace to be migrated by xref:../applications/pruning-objects.adoc#pruning-objects[pruning].
   * [ ] The internal registry uses a link:https://docs.openshift.com/container-platform/3.11/scaling_performance/optimizing_storage.html#registry[supported storage type].
   * [ ] Direct image migration only: The internal registry is link:https://docs.openshift.com/container-platform/3.11/install_config/registry/securing_and_exposing_registry.html#exposing-the-registry[exposed] to external traffic.
   * [ ] You can read and write images to the registry.
  
positive.code: If an application uses an internal image in the `openshift` namespace that is not supported by {product-title} {product-version}, you can manually update the xref:../migrating_from_ocp_3_to_4/troubleshooting-3-4.adoc#migration-updating-deprecated-internal-images_troubleshooting-3-4[{product-title} 3 image stream tag] with `podman`.
  * [ ] The target cluster and the replication repository have sufficient storage space.
  * [ ] The xref:../authentication/understanding-identity-provider.adoc#supported-identity-providers[identity provider] is working.
  * [ ] Set the value of the `annotation.openshift.io/host.generated` parameter to `true` for each {product-title} route to update its host name for the target cluster. Otherwise, the migrated routes retain the source cluster host name.
  
  [id="performance-checklist_{context}"]
  == Performance checklist
  
  * [ ] The migration network has a minimum throughput of 10 Gbps.
  * [ ] The clusters have sufficient resources for migration.
  
negative.code: 
  Before you migrate your application workloads with the {mtc-full} ({mtc-short}), review the following checklists.
  
  [id="resources_{context}"]
  == Resources
  
  * [ ] If your application uses an internal service network or an external route for communicating with services, the relevant route exists.
  * [ ] If your application uses cluster-level resources, you have re-created them on the target cluster.
  * [ ] You have xref:../migrating_from_ocp_3_to_4/advanced-migration-options-3-4.adoc#migration-excluding-resources_advanced-migration-options-3-4[excluded] persistent volumes (PVs), image streams, and other resources that you do not want to migrate.
  * [ ] PV data has been backed up in case an application displays unexpected behavior after migration and corrupts the data.
  
  [id="source-cluster_{context}"]
  == Source cluster
  
  * [ ] The cluster meets the link:https://docs.openshift.com/container-platform/3.11/install/prerequisites.html#hardware[minimum hardware requirements].
  * [ ] You have installed the correct legacy {mtc-full} Operator version:
  ** `operator-3.7.yml` on {product-title} version 3.7.
  ** `operator.yml` on {product-title} versions 3.9 to 4.5.
  * [ ] The {mtc-short} version is the same on all clusters.
  * [ ] All nodes have an active {product-title} subscription.
  * [ ] You have performed all the link:https://docs.openshift.com/container-platform/3.11/day_two_guide/run_once_tasks.html#day-two-guide-default-storage-class[run-once tasks].
  * [ ] You have performed all the link:https://docs.openshift.com/container-platform/3.11/day_two_guide/environment_health_checks.html[environment health checks].
  * [ ] You have checked for PVs with abnormal configurations  stuck in a *Terminating* state by running the following command:
  +
  [source,terminal]
  ----
  