There are some cases where a migration might fail to create some resources, but otherwise the migration succeeded.

One scenario we're currently aware of is migrating from a DevSandbox instance to your own OpenShift cluster as a non-admin. In this scenario you will be able to read some resources that can only be created as a cluster admin, such as limitranges.

As a namespace admin on both clusters you will be able to read and export the limitrange, but unable to create it on the destination.

This doesn't affect the application from migrating or running, but at present will cause the pipeline to fail.

In MTC we had the notion of a success with warnings, which would have covered the case where some resources could not be recreated.