Yes, It's Time to Migrate to Lightning Experience

A retronym is a new name for something old that becomes necessary for distinction when something new comes along. For hundreds of years, there were guitars, but when Les Paul invented the electric guitar, all the others got the retronym acoustic guitar. So it is with Salesforce: when Salesforce modernized the platform and user interface, they called it Lightning Experience and pronounced the previous interface Salesforce Classic.

Classic implies some kind of noble nostalgia, but the reality is that all of Salesforce's focus and development investment remain focused on the future, and that future is Lightning Experience.
"Figure out what's going to happen and make that your plan." 
 I don't know who originated that quote, but that's really easy to embrace in this Salesforce context. There's no uncertainty about what is going to happen. Lightning Experience is not just the future, it's the present. So if you haven't migrated from Classic, now is the time to begin.

The really good news is that Lightning Experience is a significant improvement over Classic. At the end user level, the pages incorporate a modern design aesthetic and powerful Javascript capabilities that provide your users with a more responsive and modern application, especially in the mobile context.

For admins and declarative developers, building Lightning apps is drag-n-drop easy, and Lightning Process Builder provides an intuitive graphical environment for creating process flows that can replace the most common Apex triggers. (Don't worry, all of your existing triggers still work in Lightning.)

Each new release brings dramatic improvements to Lightning; Salesforce seems focused on replicating all the Classic features you've come to rely on, while adding capabilities that Classic just can't handle. There's also a clear imperative to move more and more capability from programmatic (Apex) to declarative – as demonstrated by Lightning Process Builder and the Flow Designer.

Of special note, one of the features released in Winter '18 is the ability to have your VisualForce pages adapt to the Lightning Design css with only a single line of additional markup. This one new feature should clear the last hurdle for orgs that have been resisting migration because they have a lot of custom VisualForce in place.

Start Now
Migration is a process that will involve planning, configuration, and user training and socialization. But don't let that complexity stop you from starting the planning process. In Classic, go to Setup. At the top, just below the Quick Find, click that Get Started button.


That brings up the Lightning Experience Migration Assistant, a wizard that walks you through learning, checking your readiness, and customizing your specific org and training your users. It's clear that Salesforce is invested in everyone succeeding in this migration process!



If you need additional help with your migration to Lightning Experience – or you're ready for some custom Lightning apps – contact me.

Comments

Popular posts from this blog

Hacking Your Dreamforce ROI

3 Ways to Increase Your Salesforce ROI

3-Step Security Tuneup