Description of problem:
When we try to migrate Custom Resources the CRD is migrated, but the CR is not.


Version-Release number of selected component (if applicable):
MTC 1.5.0

How reproducible:
Always
TARGET CLUSTER: AWS 4.7 
SOURCE CLUSTER: AWS 3.11
REPLICATION REPOSITORY: MCG

Steps to Reproduce:
1. Create a new namespace in source cluster

$ oc new-project bz-test-crd


2. Make sure that the new CRD does not exist in the target cluster 

$ oc delete crd deploycustoms.samplecontroller.k8s.io


2. Create a custom resource definition in source cluster

$ cat <<EOF | oc create -f -
apiVersion: apiextensions.k8s.io/v1beta1
kind: CustomResourceDefinition
metadata:
  name: deploycustoms.samplecontroller.k8s.io
spec:
  group: samplecontroller.k8s.io
  version: v1alpha1
  names:
    kind: DeployCustom
    plural: deploycustoms
  scope: Namespaced
EOF


3. Create a CR in using that CRD in your new namespace

$ cat <<EOF | oc create -f -
apiVersion: samplecontroller.k8s.io/v1alpha1
kind: DeployCustom
metadata:
  name: 'example-deployment'
  namespace: 'bz-test-crd'
spec:
  deploymentName: 'example-deployment'
  replicas: 1
  image: quay.io/thisisatest/openshift-nginx:latest
EOF

4. Migrate the namespace


Actual results:
The CRD will be migrated to the target cluster, but the CR will not be migrated.

Expected results:
Both, the CRD and the CR should be migrated to the target cluster.

Additional info: