Azure SQL Data Migration Assistant is Stuck on "Migrate Data"
A Microsoft Engineer examined the logs you shared with us and found the following error:


  Dma.exe Information: 0 : 'Exception type: System.IO.IOException
      Message: 
          There is not enough space on the disk.


It seems like the workstation that DMA is running on doesn’t have enough disk space to do schema extract.

The following is the explanation the Microsoft engineer shared with us about why DMA requires disk space:


  The Extract service connects to a database, reads all of its objects
  and their properties, and then creates an in-memory model of the
  database. Similar to how the Build service validates the defined
  objects, the Extract service also checks for consistency and
  containment. The validation done here will also result in failures if
  you have a view that refers to a non-existent table same as with
  T-SQL! Additionally, unsupported or uncontained objects are blocked
  because these objects are not yet allowed in SQL Azure or the DAC
  in-memory model. Finally, once the in-memory model is complete and
  validated, a DACPAC is written to disk. Looking at the stack it’s a
  well-known Windows exception on not enough disk space.