Magento 2 Migration - 1.9.3.10 to 2.3.5-p1 : Migration Tool URL Rewrite Step Fail

[loginid]

I am having the following issue when running the migration tool:

[2020-08-14 06:11:38][INFO][mode: data][stage: volume check][step: Url Rewrite Step]: Error occurred. Rollback.
[2020-08-14 06:11:38][INFO][mode: data][stage: volume check][step: Url Rewrite Step]: Url Rewrite Step: rollback
[2020-08-14 06:11:38][INFO][mode: data][stage: volume check][step: Url Rewrite Step]: Please fix errors and run Migration Tool again[2020-08-14 06:11:38][WARNING]: Volume Check failed

I've not been able to find any definitive solutions for this.

Could anyone help me please?

Thank you.

[annie_steward]

The error might be caused by a duplicate in source table cms_page.
More specific cms_page.identifier no-route exists two times for different languages but only one CMS_Page was migrated.

[loginid]

Thanks for your reply.

I did see this as a solution from a different website.

So I have gone into my CMS_PAGE table and deleted all entries for no_route apart from the first one.

Then I reran the migration tool, but I'm still getting the error:

[2020-08-31 06:13:13][INFO][mode: data][stage: volume check][step: Url Rewrite Step]: Error occurred. Rollback.
[2020-08-31 06:13:13][INFO][mode: data][stage: volume check][step: Url Rewrite Step]: Url Rewrite Step: rollback
[2020-08-31 06:13:13][INFO][mode: data][stage: volume check][step: Url Rewrite Step]: Please fix errors and run Migration Tool again
[2020-08-31 06:13:13][WARNING]: Volume Check failed

Was there something else I needed to do with the CMS_PAGE table?

Thank you.

[anantprajapati]

Hello @loginid 

Can you please go to url_rewrite table and check is there any duplicate entries ???

if yes then please remove it. and again run 

bin/magento migrate:data {<path to config.xml>}

If my answer is useful, please Accept as Solution & give Kudos 

[loginid]

Thanks for getting back to me.

So I should check the url_rewrite table in the source database?

Thank you.

[anantprajapati]

Hello @loginid 

Yes you should check in source database.

If my answer is useful, please Accept as Solution & give Kudos