Transitioning from Aura to Lightning

Now that you know when an LWR could make more sense than an LWC, let’s tackle the elephant in the room: Aura is a dated standard and if you have a highly customized Aura site, you will need to plan its life cycle.

Salesforce prides itself on its relevance within the modern tech stack, and it tries to keep abreast of current technologies and functionalities. Consequently, it is slowly abandoning the Aura standard in favor of LWCs and LWRs. While it’s highly unlikely Salesforce will ever truly “shut off” Aura, especially considering it currently has sites built on it, it will slow down its support of legacy languages over time. It is therefore a best practice to transition to more modern languages where sensible. However, Tabs and Visualforce, a dated standard that was replaced over 10 years ago, is still available for use in Salesforce. So, when does it make sense to transition away from an otherwise stable component...