Your migration to Microsoft Stream is blocked - MessageKey: videoviewcountmissing

[DSTestTenant]

We have a test tenant with 9 videos in Office Video. We tested out the migration to stream today. After about 3 hours, the migration failed with "your migration to Microsoft Stream is blocked. Open a support ticket." To open a support ticket, it's a bunch of hassle for us - we have to contact a third party, get permission, etc. We are testing as we're getting ready to do the same in our production tenant. It has a lot more videos. When you look at the videos in Office Video, there are video views that are associated with them. Can you help?

I looked at the issues in Excel and it is as follows: 

AccountId	EntityType	EntityId	ChildEntityId	IsBlocking	MessageKey	MessageValues	Priority
null	Video	cvid:820101:04c6f98f-4590-44ce-8410-2d002e44b067	null	TRUE	videoviewcountmissing	8	0
null	Video	cvid:820101:06f1063e-c26c-4f76-a747-2d717544e860	null	TRUE	videoviewcountmissing	Tire Test in Community Channel	0
null	Video	cvid:820101:74f76e2a-c5e3-4427-a4f2-58c1c181104a	null	TRUE	videoviewcountmissing	IMG_1376	0
null	Video	cvid:820101:8238b120-f852-4a19-b84e-d2709ade922c	null	TRUE	videoviewcountmissing	7	0
null	Video	cvid:820101:83cf1672-fe9f-4ee5-9908-345b0ead9631	null	TRUE	videoviewcountmissing	27.00R49 Pyrolysis Testing Alkant Pan	0
null	Video	cvid:820101:9ced7c13-93b0-4056-b3cb-61bd366e0f76	null	TRUE	videoviewcountmissing	Delve Test	0
null	Video	cvid:820101:c98d7930-c0e0-41ac-a01d-d03ecbe96f5a	null	TRUE	videoviewcountmissing	IMG_1377	0

[#2]

@DSTestTenant I am facing a similiar error. Unfortunately we are one stage ahead of you. 

The errors are growing more and more eveyday. The go live date was scheduled for 23rd, on that date I saw only 3 errors, now the error persist as above and more and more warnings are appearing. 

Support cases to Microsoft are still pending, waiting for realitisc answers. 

[#3]

I'm in the same boat... Despite sending clear screenshot attachments to support, the call back only consisted of asking me to try it on different browsers, asking if the PC was rebooted (took 2 days for a call back, so it was), and if it was tried on a different network. The second callback attempted to do the same process, claiming the ticket wasn't updated from the original call, and that they'll escalate it. Hopefully someone will have an answer soon.