This presentation discusses the transition from Salesforce Classic to Lightning Experience. It provides a 4 step strategy: 1) Assess readiness, 2) Plan deployment approach, 3) Build and test in sandbox, 4) Train users and deploy to production. Tips are given for each step, such as using tools to convert notes/attachments and custom buttons. While the transition impacts the UI and analytics most, data and business logic are not affected. Proper planning and testing is key to a successful transition.
Transition to the Lightning Experience: Pro Tips, Tools and a Transition Strategy
1. Transition to Lightning Experience:
Pro Tips, Tools, and a Transition
Strategy
Shell Black, President
@Shell_Black
2. This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if any of the assumptions
proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward-looking statements we make. All statements other
than statements of historical fact could be deemed forward-looking, including any projections of product or service availability, subscriber growth, earnings, revenues, or other
financial items and any statements regarding strategies or plans of management for future operations, statements of belief, any statements concerning new, planned, or upgraded
services or technology developments and customer contracts or use of our services.
The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for our service, new products and
services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth, interruptions or delays in our Web hosting, breach of
our security measures, the outcome of any litigation, risks associated with completed and any possible mergers and acquisitions, the immature market in which we operate, our
relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new releases of our service and successful customer
deployment, our limited history reselling non-salesforce.com products, and utilization and selling to larger enterprise customers. Further information on potential factors that
could affect the financial results of salesforce.com, inc. is included in our annual report on Form 10-K for the most recent fiscal year and in our quarterly report on Form 10-Q for
the most recent fiscal quarter. These documents and others containing important disclosures are available on the SEC Filings section of the Investor Information section of our
Web site.
Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may not be delivered on time or
at all. Customers who purchase our services should make the purchase decisions based upon features that are currently available. Salesforce.com, inc. assumes no obligation and
does not intend to update these forward-looking statements.
Statement under the Private Securities Litigation Reform Act of 1995
Forward-Looking Statement
5. Classic is Dead
May 2, 2018 – Email sent to customers stating:
”All new Salesforce releases and feature development happens only in Lightning Experience”
August 10, 2018 – Lightning Experience Auto Transitioning begins
Customers that were notified have 21 days to prepare, or request a delay (not opt out)
The clock is ticking on your transition…
6. Making the Business Case to Migrate
Forrester June 2018: The Total Economic Impact™ Of Salesforce Lightning
• Cost for 2400 Users = $443,655 (Consulting Partner $232,955)
• Cost to migrate and support over 3 years = $319 per user
• ROI of 341% (n=7 customers)
You are missing out on innovation 3X a year (but paying for it!)
What LEX features would make a business impact?
Salesforce Lightning Pitch Deck & Demo Scripts
• https://admin.salesforce.com/lightninginabox
Yes, there are real costs when moving to Lighting
7. What’s Not Impacted
Data
• Nothing to migrate!
Objects, Fields, and Business Processes
• Custom fields, Custom Objects, Lead qualification process, etc.
Business Logic
• Validation Rules, Automation, Approval Processes, etc.
Security
• Role Hierarchy, OWDs, Sharing Rules, etc.
Yep, it’s all still there!
8. What is Impacted
User Interface - With the Lightning Experience, would you do it differently?
• 3 Column Layouts, 25 Tabs, Dynamic Lightning Pages
• Paths, Components, Actions, Highlights Panel, etc.
Analytics
• New Dashboards & Lightning Report Builder
Custom Code / Technical Debt
AppExchange Apps
User Training
Time to reimagine working in Salesforce!
9. Four Steps to Success
Assess
Plan
Build & Test
Train & Deploy
Your path to the Lightning Experience
Assess Plan Build &
Test
Train &
Deploy
10. Step 1: Assess
Lightning Experience Readiness Report (25+ feature checks)
Lightning Experience Visualforce Check
Optimizer Report (45+ signals)
AppExchange Apps
Technical Debt
Review your company roadmap for Salesforce
Take an inventory
Assess Plan Build &
Test
Train &
Deploy
11. Upgrade your AppExchange Apps to LEX versions (and remove old Apps) in a Sandbox before running the
Lightning Assessment Report
This will provide a more accurate assessment of your ”Technical Debt”
For org stability and resilience use as few Apps as possible
Reduce the “False Positives” that you have code issues
Step 1: Assess – Pro Tip!
12. Step 2: Plan
Bespoke Page Layout (Complex) vs standard LEX Layout
“Green Light” by Profile or functional group
• Features
• Apps
• Custom Code
Deployment Strategy (i.e. Big Bang or by Profile)
• WBS – Work Breakdown Structure
Determine the Who, How, and When
Assess Plan Build &
Test
Train &
Deploy
13. Step 2: Plan – Pro Tip!
Create Planning Discussion Documents
14. Step 3: Build & Test
Build Sprints (big bang or functional groups)
Page Layouts (complex / non-complex)
Analytics & Communication Templates
AppExchange Apps
Attachments and Notes
Custom Code (Native, Refactor or Lightning Component)
Sandbox UAT
Now the hard work begins…
Assess Plan
Build &
Test
Train &
Deploy
15. Step 3: Build & Test – New Tools!
Magic Mover (July 2017)
• Convert Classic Notes and Attachments to Lightning ready Enhanced Notes & Files
• Free App on the AppExchange
• Adheres to Salesforce limits - move 200K Attachments in a 24-hour period
• Does not migrate Documents
Lightning Experience Configuration Converter (June 2018)
• Convert JavaScript Buttons, URL hacks to Lightning Quick Actions, Component Actions, or custom buttons and
links
• Test in sandbox first!
• Run the same update in production or deploy them to production with a change set.
Reduce the workload
16. Step 4: Train & Deploy
User Training
Change Sets & Production Changes
“Smoke Test”
Go-Live Support
• Chatter Group
• Office Hours
Time to Go-live!
Assess Plan Build &
Test
Train &
Deploy
17. Step 4: Train & Deploy
You are not training:
• Salesforce concepts
• What’s the difference between a Lead and an Opportunity?
• How to do their job
• When do I convert a Lead or submit a record for approval?
You are training:
• What is different in the new UI
• Where did it go and why does it behave this way?
• New features
• Path, Kanban, Actions, enhanced Dashboards, etc.
You must train your users if you want adoption
18. Step 4: Train & Deploy – New Tools!
Replaced AppExchange App
Usage by Month, Day, by Profile
Who is switching back to Classic by Profile or User
Lightning Usage App (Summer 18)
19. How long will it take?
Dell - 18 month journey to pilot a group of sales users
• High technical debt to address
Professional Edition for a single group of users
• As quick as a month
Well, that depends…
20. Biggest Hurdle?
10 Releases focused on LEX (Winter 16)
5,119 Pages of Release Notes
Days worth of Webinars and Release Readiness Videos
Trailhead
• Lightning Experience Specialist Super Badge
• Lightning Experience Rollout Specialist
• Lightning Now! Community Group
Admin Knowledge!