Classic/Visualforce to Lightning Migration

1. Analyze

Before we can make a recommendation we uncover the unique nature of your Salesforce organization by asking questions like:

• Where and how are you using Visualforce pages and components?
• What additional code structures, such as controllers and static resources, support your existing custom builds?
• What varieties of custom reporting do you depend on, and how does Lightning impact them?
• What future plans do you have that we need to take into account?
• What aspects of your organization need to be converted and optimized as soon as possible?
• What dependencies exist between your Visualforce applications?
• Are all of your managed packages compatible with Lightning?

2. Identify

Based on the outcomes of the analysis conversations, we identify key Visualforce pages and components that should be converted to Lightning (and in what order) based on the impact each page or flow will have on your business goals, the impact to users in training and productivity, and the level of effort to accomplish the conversion, as well as any dependencies that will arise.

3. Plan

Next, we develop a plan for how we want to handle the Lightning migration. This might mean converting Visualforce pages to Lightning components and embedding those components back into Visualforce pages. Or maybe it'll mean taking Visualforce pages and using them as Lightning components. We'll figure out what works best for you.

4. Convert

Based on our agreed-upon plan, we then start the conversion process. Depending on the scope of the migration and the conversion method needed, this can be a quick or lengthy process.

5. Integrate

After the conversion work is complete, we push updates from a development to a staging environment and test thoroughly with production data to ensure the updated apps will work well on your production organization.

6. Validate and Train

Once we the converted apps are integrated, we ensure that the result meets the agreed-upon requirements, and meets the expectations of users via user acceptance testing, quality assurance checks, and training.

7. Deploy

Once all stakeholders offer approval, we deploy the updated pages.