To our experience we can migrate most SFDC to PowerApps in 2 to 4 months.

A much larger enterprise solution with multiple/complex modules and customizations may naturally take us longer (5 to 6 months).  Of course each implementation is unique, however after a quick review of your environment we should be able to provide an accurate estimate and a number of game plans for you to consider.

As a Senior Executive once told us over the phone – “Fellas I am only in this to pay a 1/5 in annual license costs so no need to enhance anything. I simply want a “lift & shift” and retain the same use cases we currently have. Most important thing is not having my employees complaining to me later”.

Our response was that in the case of a “lift & shift” we can cut our quote-estimates by half, flat out.   We would simply evaluate their configurations and repository for all existing logic, and export their schema and security roles for investigation, capture their use cases from the Business Analysts and build the exact same house on the other side of the street.

Our typical approach to manage an SFDC to PowerApps migration involves 3 steps.  This approach may change by client, system at hand or the agents involved, but generally it goes like this:

Step 1- expected duration of 2 weeks

1. Exchanging NDAs
2. Scheduling an introductory session to receive a 30-minutes demonstration of your current SFDC. Can be done from a lower “Development” environment
3. The Wizards assemble internally to speculate about the client’s best two option going forward
   1. Quote 1 – Modernizing but with less reworks, mainly aimed licensing cost savings
   2. Quote 2 – Broader degree of rethinking & change to build your best CRM ever
4. We share the above design proposals as CRM goals, durations & prices
5. Our legal documents are written in a clear, easy and non-interpretive fashion to make anyone comfortable enough to proceed with us

Step 2 – expected duration X weeks/months

1. We conclude the design for the target system with the client (think “Waterfall” but instead we call it “Wonderful”)
2. We bring forward the skeletal design of the PowerApps to the the client for initial sanity review (so partial forms to see the database schema/relationships etc)
3. The bulk of the Migration Project is when Client and us begin a set of two recurring showcase/demo meetings per week to track progress and collect feedback
4. Everything that’s being brought up during showcase/demos usually always gets completed before the next showcase/demo so bring your best focus and thought. Showcasing sessions are when the pedal hits the metal
5. Working in our own “hyper-Agile” fashion allows us to solve gaps and factor the client feedbacks immediately as everyone’s eyes are on the ball

Step 3 – expected duration of 3-5 weeks dependent on data migration size and client’s QA involvement

1. By this point we have reformed SFDC as a new PowerApps environment. We’d begin to involve “Change Champions” from the organization to get them familiar with the new system and help drafting out basic usability guides
2. With most of our quality assurance done by this point we don’t anticipate major bugs or being blindsided. We work with testers/users from the client side to bless our new PowerApps
3. Our in-house Data Migration Wizard would be working with SSIS/Kingsway adapters to build a custom migration package on lower/Dev environments and perfect it for the upcoming production run:
   • The SSIS package would standardize certain formats for Dates, URLs, Phones/Emails, Zip/Postal etc.
   • Annotations/Attachments/Emails would require special care.
   • Certain Text fields may be mapped/casted onto new picklists, numbers or other “formatted” fields in PowerApps
   • Client would evaluate the data and pick a Go-Live date
   • We export your users to Microsoft Entra ID if needed
4. Welcome to PowerApps! The Dynamics Wizards team can kick back and provide our free support for your first year should you tackle any Bugs
5. We send you our invoice for the entire project in line with our original estimates

Step 3.1 – Project Handoff

1. Visio ERD for your new PowerApps’ database schema
2. Batch of Excels listing all tables/fields/relationship keys
3. Server-side & client-side source codes
4. High level design document describing your new system
5. Developers’ Notes providing any meaningful notes for future customizers (although our code/logic is best at being “self explanatory”)

Hypothetically we could take the comfy and familiar path as any other Partner and make you feel secure by saying: “Agile Agile take a free Scrum master on the house” but that’s not our style.

We’re not undermining any SFDC migration to D365 or PowerApps, it’s a fair-sized project by all means, especially for larger environments, and yet we’re estimating most of these projects at 3 to 5 months.

Had we done this with an Onshore/Offshore model of Developers, Architects, Business and Systems Analysts, Scrum masters (where most of which haven’t collaborated on previous projects) then the same project would be estimated at about a year, and in effect run 50% longer, and you would think the “end product” would be something to brag about.

We see it happening all the time. It must be the way of the world, but we’ve decided to be the change we wanted to see in the world and that’s where YOU step in!  Reach out to us 4-7 months before your next planned SFDC annual licenses renewals to see if we could take you out of there. Our capacity is limited considering our team size and the applied focus we give each project so secure your spot on our queue!