Hi @aaedla
The article is walking through how to move the data from the Access Database to Dataverse with the ability to continue to leverage he Access Forms on top of Dataverse along with Dataverse forms, views, etc. and creating a model-driven application.
Overall this is a pretty good guide to accomplish moving the data to Dataverse. Most of the time for me though, I usually am re-architecting the tables during migration and changing some fields to Choice fields where it makes sense, and other application structure changes that are better supported in Dataverse. Normally I export the data to Excel and utilize that to help me build the data that I import into Dataverse. This is just what works for me and I have had to do this in a number of projects. Most flexibility and easy to accomplish...
Now, the documents... If you are moving to Power Apps you will want to look at moving the files from the nextwork share to SharePoint and utilize the standard integration with SharePoint out of Dataverse. https://learn.microsoft.com/en-us/power-platform/admin/set-up-sharepoint-integration
Int this model you will be able to create the relationship with the table / entity in Dataverse and a specific Document library. Once you do this you will be able to see documents related to your record in the model-driven power app.
Note, it will take time and effort to basically upload the file for each record in your tables from your repository into the application but will also provide the benefits of having multiple documents related to the same record.
