Clarified steps for blocked migrations

Author: tknippenberg

content/en/docs/developerportal/general/team-server/migrate-to-git.md

@@ -41,11 +41,9 @@ In addition to the hard criteria mentioned above, a check is performed to determ
 
 ### Eligibility Check Outcomes
 
-#### Not Eligible for Migration
-
-If your app is not eligible for migration the reason(s) will be listed on the page. to continue with the migration, resolve these reasons and try again.
+#### Eligible for Migrating With History
 
-In case there are reasons you cannot address, please reach out to Support or your Customer Success Manager to discuss the options.
+If your repository is eligible for migrating with full history, you can choose whether to retain your history when migrating or not. For the smoothest experience post-migration we advise you to migrate without history.
 
 #### Eligible for Migrating Without History
 
@@ -57,9 +55,19 @@ You will receive a full backup of your SVN repository after completing the migra
 
 {{% /alert %}}
 
-#### Eligible for Migrating With History
+#### Not Eligible for Migration
 
-If your repository is eligible for migrating with full history, you can choose whether to retain your history when migrating or not. For the smoothest experience post-migration we advise you to migrate without history.
+If your app is not eligible for migration the reason(s) will be listed on the page. to continue with the migration, resolve these reasons and try again.
+
+##### MPR File Size
+
+When the size of the *mpr* file exceeds the threshold, migration is blocked to prevent rapid repository growth after migrating to Git. To get your app whitelisted for migration, you will have to agree on the following steps with Support or your Customer Success Manager.
+
+1. [Migrate without history](#without-history). This requires converging all branches which you want to retain.
+2. Update your app to Studio Pro version 10.18 or above, and convert to [MPRv2](/refguide/troubleshoot-repository-size/#mprv2).
+3. Execute a [Git cleanup](/refguide/troubleshoot-repository-size/#cleanup-tool).
+
+The first two steps need to be executed within a short timeframe. The last step is technically optional, but is strongly recommended for the best experience going forward.
 
 ## How Migration Works