Our Journey from Microsoft Dynamics GP to the Business Central Cloud Part 5: The ResultsWe hope you’ve enjoyed this series on our migration from Dynamics GP to Dynamics 365 Business Central. Also, we hope that our experience gives you confidence in your migration plans and helps to set your expectations on the process.

In our previous posts, we covered why we decided to make the change, the “state” of our systems pre-change and the actual implementation and go-live process. In this post, we are going to wrap up this series and look at the value of our move to cloud-first technologies.

Using Power Apps

Since January 1st, 2021, we have developed several new solutions using the Microsoft Power Platform. The Power Platform includes the following components:

  • Power BI: Reporting Tool
  • Power Apps: Low Code/No Code App Development Tool
  • Power Automate: Workflow Engine
  • Power Virtual Agents: Chatbot Engine

To date, we have:

  • Created over 30 Power BI reports (with a long list of additional reports to be created) to provide insight into:
    • Our customers and their subscriptions
    • Financial data
    • Product usage by our customers
  • Internal-use applications
  • Created 2 internal use Power Apps with several more in the works
  • Created over 20 separate “Flows” using Power Automate to connect systems and provide notifications of business activities

In addition, we are developing Power Platform solutions for our customers to use in their environments to augment our product functionality.

One of the first internal apps we created was to track the challenges our employees have in delivering exceptional customer service. These end up in our “Book of Solutions” application which are triaged and prioritized, then developed and delivered to the organization using the Power Platform. One example is a Power Automate flow was created to email our internal IT/IS team any time an employee was added or changed in Payroll NOW. This information is then used to ensure the employee gets setup with all their necessary licensing (including Office365, D365 Customer Engagement, Business Central, etc.) and that our Azure Active Directory stays in sync with changes in payroll.

Deploying D365 Customer Engagement has allowed us to integrate Microsoft Project Operations with Project for the web. Our Customer Success Team will now be utilizing this solution to improve the implementation process for our customers. Since the data for this is in Dataverse (along with our classic “CRM” data), we can connect this to our existing systems like our timesheet reporting solution and project invoicing in our billing solution. This also enables