Switching over to a new system can be a daunting task. Especially when you’re feeling settled with your current process and way of doing things. Fortunately, transiting from Salesforce Classic to Lightning isn’t too difficult if you follow a step-by-step guide such as this.
Firstly, why do you need to upgrade to Salesforce Lightning? You don’t have to transition over to the new system but it’s certainly in your best interest to do so as eventually technical support for the classic version will end, and most the new features are now only available in the Lightning version so you’d be selling yourself short.
Step 1 – Outline goals:
Before you begin to move any processes over to the new system, you need to decide why you want/need to transition. All businesses can benefit from the upgrade to the Lightning version of Salesforce but some companies simply don’t need the functionality enough yet to make the shift. The best thing you can do is create a clear list of goals for the Lightning migration and why you need it more than the classic version. Try and align these with your business goals and highlight how specific new features on the lightning version will help you achieve them.
Step 2 – Prepare teams:
Moving over to the Lightning version has the potential to cause disruptions in workflows as internal processes will also be making a shift as well. It’s an old saying that failing to prepare is preparing to fail, so make sure to train all the affected teams to discuss any concerns before moving onto the development stage. You’ll need to remember to include all teams as every function will use Salesforce differently so a new system will impact them in unusual ways.
Step 3 – Create a battle plan:
The next step is to develop a clear guide for the development team to use during the transition period as it will help to avoid disruptions. By prioritising what features you’d like, scheduling time scales and providing resources for developers to be able to collaborate you can keep bumps in the road to a minimum. This is the point where you need to look at the wider picture to visualise how you might integrate Lightning with outside systems and how this will change the workflow of your teams.
Step 4 – Squash the Bugs:
There’s not much worse than completing a project only to find that it breaks down as soon as its operational. To prevent this, you’re best off running a Lightning Readiness check to pick up on any potential or unforeseen bugs and incompatibilities. Once this is finished, you should use a sandbox to isolate and test changes before an official launch. This allows key stakeholders and Super Users to try the functionality and provide feedback so that updates can be made.
Step 5 – Ensure alignment:
Remember those goals you set out in step 1? Now is the time to check with your stakeholders that the system will accomplish them. If not, you need to go back and change a few things to make sure they’re set to be achieved. Once they’re met then it’s time to launch the program. Start with all changes to Power Users only, as doing this means that each user account can test the new functionality individually. This helps to ensure that each feature lines up with what each user group needs. Be sure to implement their feedback at this stage before releasing it to the whole organisation as it prevents the issues impacting on the rest of the business.
Step 6 – Documentation:
Having a fully functional program is important, but it’s not much good if people don’t know how to use it in the right way. That’s why you need to create a detailed document which outlines workflows and processes so that developers can edit the Lightning system as the business adapts in the future. You can then use this document to train the users on the Lightning functionality before going live to the rest of the company.
Step 7 – System Launch:
The final step is where you can take the system live, but this comes once everyone is fully trained on how to fully utilise it. It’s best to keep a few developers close by following the launch to help with any potential issues that inevitably occur, but after a few weeks, it’s time to let the system administrators take over.
Thinking of switching over to Salesforce Lightning?
System migration and integration can be tricky without professional guidance. That’s why many clients find our help extremely useful in these situations. At Zon Projects, we offer long term solutions that require complex process planning and architecture design. Get in touch today!
How Can We Help You
We would be happy to have an informal chat with you about your requirements and to offer advice or see if we can be of assistance to you. Please complete our simple form and we will contact you as soon as possible.
Help & Advice
Project recovery
Support & Training
Integration to a 3rd party system
Get in touch
The post How to Switch Over to Salesforce Lightning: A Seven Step Guide appeared first on Zon Projects.
The Post How to Switch Over to Salesforce Lightning: A Seven Step Guide was first published here: https://ift.tt/2QfOmD9
No comments:
Post a Comment