I want to migrate a database created in Access to Dataverse

山本 悦崇 20 Reputation points
2025-08-22T01:20:16.6733333+00:00

I want to migrate a database created in Microsoft Access to Dataverse while keeping the forms built in Access as they are.

Given that I already have a Dynamics 365 for Sales subscription, I would like to know whether an additional Power Apps license is required if I want to convert the entire Access database into custom entities.

Even if I have an Enterprise plan subscription, are there any restrictions—such as requiring an additional connector—when operating with only custom entities?

Microsoft 365 and Office | Access | For business | Windows
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Michelle-N 4,105 Reputation points Microsoft External Staff Moderator
    2025-08-22T04:03:01.0166667+00:00

    Hi @山本 悦崇

    Thank you for posting question to Microsoft Q&A.

    Based on your description, I understand that you want to migrate a database from Microsoft Access to Dataverse, while keeping your existing Access forms as the front-end. Your main questions are about whether you need an additional Power Apps license for this process and if there are any connector restrictions, given that you already have a Dynamics 365 for Sales subscription. 

    Based on the official Microsoft documentation I found, you can indeed migrate your Access database to Dataverse. The process allows you to continue using your Access desktop application with the tables now linked to Dataverse. However, it's important to note that not all data types in Access are directly supported in Dataverse. You may need to adjust or remap some fields during the migration process. 

    Regarding your licensing question: Dataverse use rights are already included with your Dynamics 365 for Sales license, so you do not need an additional Power Apps license to convert your Access database into custom entities within that environment. A separate Power Apps license would only be required if you plan to build and use advanced Power Apps features or standalone apps that are outside the scope of your Dynamics 365 application. 

    I found two official documents that should be very helpful for you: 

    Get started: Migrate Access data to Dataverse - Microsoft Support 

    Migrate Microsoft Access data to Microsoft Dataverse - Power Apps | Microsoft Learn 

    As a forum moderator, I can help guide you with documentation and troubleshooting steps, but I don't have access to your system or the specific tools and resources needed to investigate this issue directly. However, I will certainly do my best to help you find the right path to a solution. 

    If you require more in-depth, hands-on assistance during your migration or have complex questions about your specific license agreement, you can visit https://community.dynamics.com/so the specialist can assist you better than me. User's image


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".   

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.Image preview


  2. George Hepworth 21,900 Reputation points Volunteer Moderator
    2025-08-22T11:44:21.5433333+00:00

    While you can migrate your Access tables to Dataverse, as previously mentioned, I would caution you to be alert to the potential for decreased performance of Access forms and reports when linked to Dataverse tables.

    In Access, to do this, you must be signed into the M365 account where your Dataverse tables will be placed.

    The actual migration is here:
    User's image

    Many people have found that Dataverse tables are very slow when linked in Access. That's in addition to the potential need to reconfigure tables to use compatible datatypes.

    I would caution you to set up a realistic test project and see for yourself if performance will be acceptable before committing your organization to this path. You may have small enough datasets, and miminal processing needs, that it will be acceptable. That threshhold is not very low, unfortunately.

    Be sure it's a viable alternative for your needs in your organization with your data earlier rather than later.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.