The essence of every CRM is a system of records, and the essence of that is a Database.   With modern PowerApps, the underlying SQL is named Dataverse. As a SaaS solution database it makes it a real breeze to not routinely index your tables, optimizing query executions and other duties to keep your database healthy, as Microsoft does all that.    However, all the automated administrative database duties of the past cannot amend a database that is not properly designed or structured.

Many D365 and SFDC that we are looking at are often polluted with unused tables, columns, relationships, views etc., so we take this opportunity to rethink about those element and begin by reevaluating the database layer for upcoming schema optimization. We are especially attenuated when clients express their own thoughts and skepticism about their existing solution.

While we don’t have a schema-resolution-bible-per-se we could outline our approach as such:

1. Gather and evaluate existing database schema
   1. Consider which data elements to refract
   2. Consider which data elements to consolidate
   3. Consider which data elements might benefit from type-replacement
2. Share our design option(s) for the future-target CRM in PowerApps
3. Draft a business agreement for the proposed design and features of the future CRM
4. Put together the new system and showcase it once or twice per week until everything is ready
5. Prepare your target environments for the Upgrade
6. Map and run the data migration package

Our simplistic/analytical approach to each project covers all the necessary “bases” to complete a smooth transition every time, while factoring necessary database restructuring.  As business environments change and companies grow so should their CRM.  Let’s talk and position you on our projects queue before your next license renewals with Microsoft or SFDC.   With future savings on licensing costs our transition plans normally pay for themselves in under a year and have we mentioned we build better CRM solutions?