During Xporter migration with JCMA, it's important to check if the templates already exist to enable future migrations

During the initial migration, Xporter successfully transfers all templates from the Server/Data Center instance to the Cloud instance.

However, subsequent migrations do not transfer newly created templates. The current implementation does not verify whether a template already exists in the destination instance. Instead, after the first migration, it assumes all templates have already been migrated and skips importing template data, including any newly created templates.

Additionally, we have observed cases where the migration is marked as failed at 100%, even though the data has actually been migrated successfully. This occurs when Xporter detects that templates already exist in the target Cloud site and skips re-importing them. As a result, the migration reports a false negative, incorrectly indicating a failure even though it completed successfully.