Home » FAQs » Should I include Adeaca PBA in the first phase of my Dynamics 365 implementation or wait until later phases?
Implementation Integrations Product

Should I include Adeaca PBA in the first phase of my Dynamics 365 implementation or wait until later phases?

Adeaca Project Business Automation should always be included in the first phase of a Dynamics 365 Finance implementation.

If you are a project-based company your bottom line is directly determined by how efficiently you plan, deliver and manage projects. As such, Adeaca Project Business Automation should always be included in the first phase of a Dynamics 365 Finance implementation.

While implementing Adeaca PBA can be done in later phases, it is not advisable because some level of reimplementation of the Dynamics platform is involved and it is more disruptive to the users. It is better to make the switch all at once and train everyone on the new platform at the same time.

For some companies, the transition from a highly manual and siloed environment to a completely integrated and automated PBA environment may seem daunting and a phased approach to initiating the use of Adeaca PBA may be a good option. For instance, while the entire PBA application is available, you could begin using the financial controls to start and the operational controls in later phases or vice versa. We will help advise you as to the best approach.

About the author

Henrik Lerkenfeld

Henrik is Adeaca's Head of Product Development. Henrik has deep roots in Microsoft Dynamics, having been part of the original Axapta ecosystem and Microsoft’s team after it was acquired. His knowledge of project industries and his systematic process design approach is a crucial component of Adeaca’s customers' success.