Migrating Visualforce Page to Lightning Made Easy with lightningStylesheets in Salesforce

Before exhausting your resource on VF page to Lightning Component conversion, try adding lightningStylesheets attribute to <apex:page> tag in your VF page first!

Starting Winter '20 release, Salesforce will enable Lightning Experience?for all orgs that haven't already done so. What does this mean to the orgs that have a lot of VF pages? Shall all VF pages get converted into Lightning Components? And what's the Return on Investment (ROI) of this conversion project? Since it can be costly (budget, resource, schedule, design, development & QA), I suggest all Salesforce Admin should evaluate the lightningStylesheets attribute first before going down the conversion path, especially for the reasons below...

1. Visualforce is a standard component to choose from within Lightning App Builder.
2. Getting a VF page ready for the component selection is to simply have the "Available for Lightning Experience, Lightning Communities, and the mobile app" checkbox checked.
3. Adding the lightningStylesheets attribute to <apex:page> tag styles the VF page with the look of Lightning Experience.

It makes a lot of sense to me that I shall evaluate the three steps above before building custom lightning components & controllers to replace my VF pages.

Below is a video of running the same VF page in Lightning Experience and Salesforce Classic, a side by side comparison of the look and feel and action execution, and Yes, you can run the same VF page in both environments simultaneously in your org.

I hope the video above gives you a taste of how your VF page can style like Lightning Experience without losing its functionalities, and having lightningStylesheets set to "{!IF($User.UIThemeDisplayed == 'Theme4d',true,false)}" will keep your VF page working in the existing environments (Classic, Community and Mobile), in case your users still need to switch the UI environment back and forth.

Finally, I think the best part of using lightningStylesheets is this, it is maintained by Salesforce! And Salesforce will keep it up-to-date in your org. In another word, the VF components in your VF page will never be out of style. How great is that?