Connecting...

W1siziisimnvbxbpbgvkx3rozw1lx2fzc2v0cy9odw50zxity2hhcmxlcy9qcgcvymfubmvylwrlzmf1bhquanbnil1d

Upgrading large Dynamics 365 CRM deployments to online

W1siziisijiwmtkvmdqvmduvmdgvntivmdevnte4l2r4bc01ntu0odctdw5zcgxhc2guanbnil0swyjwiiwidgh1bwiilci3mdb4nzawxhuwmdnjil1d

Posted by Alex Phillips about 2 months ago

When talking about its Dynamics 365 Customer Engagement, Microsoft’s focus is often the online version. However, you cannot ignore the significant number of businesses still using on-premises versions of Dynamics CRM or D365CE.

There are many different reasons why companies are yet to make the move from on-prem to online. For some, it’s to do with regulatory compliance. For others, they feel a system hosted in their own data centre is a more secure option than one hosted online. And then there are the customers who worry that upgrading their large complex implementations will be too complicated, take too much time, cost too much, and be too much of a risk.

However, none of these reasons should prevent a company upgrading their CRM on-prem system to an online version.

If you are looking to take the plunge, here are three things to remember.

1. Don’t be afraid to ask questions

However large the challenge you’re facing, someone else has been in the same situation. You can learn from their experiences – and their mistakes – and build up your knowledge base by asking the right questions. Those questions can range from the size of the database and location to GDPR considerations.

2. Look for alternatives to the R word (reports)

If you were to ask people the main reason for not upgrading to the cloud, many would say complex reports. Over the years, the reporting function has extended to include Power BI. When you dig deeper into reports and their business function, the reporting issue can be solved in other ways – anything from modular apps for specific user groups to PDF exports. The key is understanding what it is the business really needs and solving the problem at its root. Often you’ll find a report is not actually needed.

3. Overcome the challenge of integration

Another key reason cited for not moving to the cloud is the number of integrations required to do so. However, on closer inspection this is not as big a challenge as first imagined. When you start considering things like throttling limitations, you realise they can be quite steep (60,000 API calls every five minutes). However, making use of the Data Export Service and the Azure SQL database can create a faster, more efficient way to reduce the API.

 

At Hunter Charles we have CRM and DRP specialists who can support your move to the cloud and smooth the transformation process. Get in touch today.

Tweets from @hunter__charles