Hi, I'm an Admin of a highly-customized "Classic" org that likely will never switch to Lightning as it will probably be retired. However, in the near term, there is a business need to enable a component that is only available in Lightning.
My question is regarding those who have transitioned to Lightning piece by piece while converting apex, visualforce, javascript, etc., over time. Did you note any impact on Classic functionality, while the few people who were Lightning-enabled prepared components for the switch?
In other words, the goal for us would be to only enable Admins for Lightning, turn on Lightning for the org and have the one user (me) use the one component in Lightning while the rest of the user base remained on Classic (Lightning user experience not enabled on profiles) with no changes or impact to Classic operations until the org sunsets. Any gotchas?
I have helped many clients in the transition and I found this process very smooth unless they have less use of javascript. You can use LEX even with your existing classic customization as Salesforce has provided many alternatives to use the same Visualforce pages.
