Gaps Between Salesforce Classic and Lightning Experience

Data Access and Views

• Supported Objects: These Salesforce objects are available in Lightning Experience. Standard objects not listed here aren’t supported.
  • Account
  • Activities
  • Asset
  • Asset Relationships
  • Calendar
  • Campaign
  • Campaign Members
  • Case
  • Chatter
  • Contact
  • Contact Versions
  • Contracts
  • Dashboards
  • Duplicate Record Items
  • Duplicate Record Sets
  • Email Messages
  • Event
  • Group
  • Home
  • Knowledge
  • Lead
  • Notes
  • Opportunities
  • Opportunity Products
  • Order
  • Order Products
  • Price Books
  • Price Book Entries
  • Products
  • Quotes (Creating quotes from the Quotes home page isn’t supported.)
  • Reports
  • Social Personas
  • Social Posts
  • Tasks
  • Users
  • Work Orders
  • Work Order Line Items
  • Custom objects
  • External objects
• Fields on Unsupported Objects: They appear in Lightning Experience, but they’re read-only and don’t include links to associated records.
• Related Lists for Unsupported Objects: They don’t appear in the interface, even if they’re included on an object’s page layout.
• Object Home Pages: These features aren’t available.
  • Access to object-specific reports on the object home page
  • Any of the tools in the Tools section on the object home page
  • Summary report tool on the object home page

  To get similar functionality in Lightning Experience, create a custom object home with Visualforce.

• List Views: These features aren’t available.
  • Feeds
  • Following records directly from a list
  • Drag-and-drop scheduling for account, contact, and lead list views. (You can create events from contacts, leads, accounts, and person account list views by downloading Schedule from List Views in Lightning Experience from AppExchange.)
  • Alphabet shortcuts for lists. (You can use the list view search box to search for records in a list view.)
  • Recently Created and Recently Modified lists
• Working with Data:
  • For existing Salesforce to Salesforce customers, records shared by connections are available in Lightning Experience if their object type is also supported in Lightning Experience. However, the Created By and Modified By fields aren't displayed.
  • The Salesforce sidebar that appears on the left side of most pages in Salesforce Classic isn’t replicated in Lightning Experience. Items from the sidebar aren’t included either, including:
    • the Tags link and Recent Tags dropdown list
    • the Create New dropdown list (use the New button on the navigation bar and object home pages)
    • the Calendar shortcut (access the Calendar from the navigation bar)
    • the Recent Items list (see recent items on the Home page or on object home pages)
    • messages and alerts
    • custom links

    Most sidebar items can be re-created using the Lightning Experience utility bar.

• Accessibility Mode: Not needed in Lightning Experience because the interface is designed according to the latest accessibility standards. Screen readers are supported natively.

Sales Features

• Accounts: These features aren’t available.
  • Contact roles on accounts. (Use contacts to multiple accounts instead.)
  • Copy Billing Address to Shipping Address link. (Instead, manually copy Billing Address and paste it into Shipping Address.)
• Campaigns: Campaign Influence 1.0 isn’t available. Use Campaign Influence instead.
• Divisions: This feature isn’t available. To complete related tasks, including creating and editing divisions, changing your working division, and applying Division filters to list views and reports, switch to Salesforce Classic.
• Leads: The Campaign lookup field isn’t available. Use the Campaign History related list on lead pages.
• Opportunities: These features aren’t available.
  • Similar opportunities
  • Competitor tracking
• Products and Price Books: Archiving products and price books isn’t available. As an alternative, you can deactivate products and price books. After they’re deactivated, all the records related to them are preserved.
• Console for Sales: See Console Features in this topic for details.

Productivity Features

• Events and Calendars: In Lightning Experience, you can’t create an event for another calendar application using the Export Event (formerly Add to Outlook) button. However, if you're set up to sync events using Einstein Activity Capture or Lightning Sync, events you create and edit from Lightning Experience or any of the Salesforce mobile apps sync to Microsoft® calendars or Google Calendar™ automatically.
• Tasks: Users can't create recurring tasks with the “every weekday” frequency. We don’t recommend using Lightning Experience to edit tasks that were created in Salesforce Classic and repeat every weekday. If you do, the edit page doesn't show the latest recurrence details. Instead, create tasks in Lightning Experience that repeat every Monday, Tuesday, Wednesday, Thursday, and Friday.
• Integrated Email:
  • This feature isn’t available for custom objects.
  • The Person account record type doesn’t offer Contact merge fields. (From records for those objects, you can send email to contacts, leads, and users maintained in Salesforce and valid external email addresses.)
  • The Mail Merge button on Salesforce records that allows users to generate Microsoft® Word documents with merged fields from Salesforce isn’t available. In addition, hyperlink formula fields aren’t supported as merge fields. (To take advantage of merge fields while contacting their customers, users can send individual emails from Lightning Experience that include merge fields from Salesforce records. Or search AppExchange for comparable functionality.)
• WDC: Management tools for sales and service aren’t available. Lightning Experience users can give thanks badges from a user’s profile, a record, or a group in Lightning Experience. Users can also see skills endorsements that they’ve received in the feed.

Customer Service Features

• Unsupported Service Cloud Features:
  • Answers (use Chatter Questions instead)
  • Chatter Answers (use Chatter Questions instead)
  • Ideas (use Experience Cloud sites instead)
  • Self-Service portals (use Experience Cloud sites instead)
  • Solutions (use Chatter Questions instead)
  • SOS
• Cases: These features aren’t available.
  • Case experts
  • Case layout—Close Case layout. (You can add closed statuses to case edit pages. From the Support Settings page in Setup, select Show Closed Statuses in Case Status Field.)
  • Case—New Contact. New associated contacts don’t default to the account that they’re created on.
• Console for Service: See Console Features in this topic for details.
• Entitlement Management: These features aren’t available.
  • Contacts related list on Entitlements
  • Entitlements related list on Contacts
  • Entitlement Templates related list on Products
  • Milestone Status Icon field on Cases
  • Status Icon field on Service Contracts
• Field Service: The Skill object isn’t available. Although skills can only be created in Salesforce Classic, resource skills can be assigned and managed in both Salesforce Classic and Lightning Experience.
• Lightning Knowledge: Knowledge in Lightning Experience works differently than Knowledge in Salesforce Classic, and requires a careful migration plan. Compare Lightning Knowledge to Classic Knowledge and review the Lightning Knowledge limitations. Then create a migration plan.
• Chat: This feature is available in Lightning Experience as a component in the Service Console app. You must route chats with Omni-Channel to chat in Lightning Experience. Make sure that you have Omni-Channel ready for Lightning Experience and have set up your chat button or Embedded Chat window to route with Omni-Channel. Considerations for Omni-Channel routing apply. See Compare Live Agent and Omni-Channel Routing for Chats in Salesforce Help.

  These chat features aren’t available.

  • List view—Recently Viewed Pages
  • File transfer—file preview. (File previewing isn’t used with File Transfer in Lightning Experience. Instead, files are downloaded to the rep’s computer.)
• Macros: Attaching a knowledge article in a macro isn’t available.
• Milestones: The Business Hours field isn’t available on the Case Milestones Case related list.
• Omni-Channel: This feature is available in Lightning Experience as a utility in the Service Console app.
  • Omni Supervisor—hover in the agent timeline isn’t available.
  • Objects that aren’t supported in Lightning Experience can’t be routed using the Omni-Channel utility. For example, SOS isn’t supported in Lightning Experience, so you can’t route SOS sessions using Omni-Channel.
• Open CTI and Call Centers:
  • There are separate Open CTI APIs for Salesforce Classic and Lightning Experience. You can’t swap the two Open CTI APIs in custom JavaScript code because they behave and function differently. For detailed information about the two APIs, including differences in functionality, see the Open CTI Developer Guide.
  • These methods aren’t available: getDirectoryNumbers(), isInConsole(), searchAndGetScreenPopUrl(). (To re-create searchAndGetScreenPopUrl() functionality, use searchAndScreenPop in Open CTI for Lightning Experience.)

Reports and Dashboards

• Reports: These features aren’t available.
  • Opportunities with Contact Roles and Products report type
  • Language selector in the Report Builder
  • Reports printable view
  • Specify precision for a measure in a report
  • Accessibility mode for the Report Builder
  • Follow reports. (Instead, users can favorite reports in Lightning Experience.)
  • Report notifications. (Instead, users can subscribe to reports in Lightning Experience.)
  • Schedule report refreshes. (Instead, users can subscribe to reports in Lightning Experience.)
  • Error messages for reports with invalid metadata. If a report has invalid metadata, the Lightning report builder doesn’t give an error message, but doesn’t let you edit the report. In Salesforce Classic, the report builder gives a descriptive error message saying why you can’t edit the report.
• Dashboards:
  • After saving a dashboard in Lightning Experience, you can’t edit it in Salesforce Classic. Instead of editing a Salesforce Classic dashboard in Lightning Experience, consider cloning the dashboard and editing the clone. That way, you can still edit the original dashboard in Salesforce Classic.
  • These features aren’t available.
    • Link from a dashboard component to an email address
    • Change report chart size or location
    • Schedule dashboard refreshes. Scheduled dashboard refreshes from Salesforce Classic continue to work in Lightning Experience, however. (In Lightning Experience, instead of scheduling dashboard refreshes, subscribe to dashboards.)
    • Visualforce components on dashboards. (In Lightning Experience, create a custom tab and use that as a dashboard for your custom lightning components.)
    • Follow dashboards. In Lightning Experience, users only see dashboard feed activity (like posts) in their Lightning Experience feed.
• Folders: These features aren’t available.
  • Standard folders containing default reports and dashboards that come packaged with Salesforce. (To get started on some default reports and dashboards, go to AppExchange and download the Reports & Dashboards Starter App.)
  • Pin folders. (Instead, add folders as favorites in Lightning Experience.)
  • Legacy folder sharing. (Instead, use enhanced folder sharing, which improves on the features of legacy folder sharing.)
• Charts and Dashboard Components: Pie charts from Salesforce Classic display as donut charts in Lightning Experience.

Files and Content

• Salesforce Files: These features aren’t available.
  • Subscriptions
  • Content tags
  • Content Deliveries. (This feature is exposed in the API, so you could create a custom component to provide this functionality in Lightning Experience.)
  • Content Detail page, including information about content tags, content rating, content archiving, usernames who downloaded content, and subscriptions to content, authors, or tags
  • Content tab, including information about search facets, searching within the library, and mass download of files
  • The Files tab and Files Detail page don’t include the options to filter by all files, unshare from all locations via the Make Private action, and share a file with the company.
  • Notes and Attachments related list roll up to display on the record of a parent object. (In Lightning Experience, you can share your Salesforce Files with multiple records. A file posted on an opportunity can also be shared to the parent account. As long as the file isn’t private, then you can view the file from the account. You can create a trigger on ContentDocumentLink to do this sharing automatically.)
  • Receive email notifications when content subscriptions are updated. (A workaround is to create a trigger to notify users of changes to the content.)
• Documents: This feature isn’t available. To use documents in Lightning Experience, export them in your weekly export or using Data Loader. Then upload them into Lightning Experience as Salesforce Files.

Chatter

• Chatter Feeds: These features aren’t available.
  • Chatter messages
  • Tags
  • Highlighted search results. (In Lightning Experience, when a user runs a search on a feed, search terms aren’t highlighted in the results.)
• People and Profiles: These features aren’t available.
  • All User list
  • Chatter Influence
  • Limiting visibility of Contact and About fields to employees, external users, or public (guest) users
  • Add new actions (admin)
  • Edit external personal profile pages for Chatter External licensees
• Groups: These features aren’t available.
  • Recently Talked About topics
  • Access Chatter-wide notification settings from the group notification settings
  • Add Record action when a customer group includes external members. You can’t add records even when an admin includes the action in the group publisher.
  • Use Invite People to invite customers to join groups using their email addresses. (Instead, you must create users for these customers. Then use the Add Member action to add them to the group.)
• Recommendations: Recommendations appear only on the Chatter home page. Files and records don’t get recommendations in Lightning Experience.

Experience Cloud Sites

These features aren’t available.

• Global header. (To switch between your org and Experience Cloud sites when using Lightning Experience, use the App Launcher.)
• Cloning or creating email templates as a Partner Community or Customer Community Plus user
• Enabling WDC Thanks to use Mission Badges in Experience Builder sites

Console Features

• General Functionality and Customization: These features aren’t available.
  • Resizeable split view
  • Keyboard shortcut overrides
  • Interaction logs
  • Dynamic list updates via push notifications
  • Dynamic record updates via push notifications
  • Tab preview on hover
  • Forget open tabs. (As a workaround, use a background utility item to control your tabs.)
• Utility Functionality: Support for multiple lines of text isn’t available.
• Component Functionality: These features aren’t available.
  • Collapsible regions
  • Pinned region in custom templates
  • Multi-monitor components—pop-out workspaces
  • Visualforce overrides—the delete action
  • Region presentation—size. In Salesforce Classic, you can adjust the size of a component. In Lightning Experience, the page template for your record page determines the size of the component region. For example, the three column page template provides a main column width of 50%, and the side columns widths are each 25%. You can’t collapse or adjust region size. To view the available page templates, create a page in Lightning App Builder.

See What Features Are Available in Lightning Console Apps? in Salesforce Help for more information.

Navigation and Actions

• Record Field Navigation: The top-down tab-key order, which allows users viewing a record detail page to move through a column of fields from top to bottom before moving focus to the top of the next column of fields, isn’t supported in Lightning Experience. Even if a page layout is configured for a top-down tab-key order, tabbing moves from left-to-right through field columns in Lightning Experience.
• Actions and Buttons: These features aren’t available.
  • Some mass actions on object home pages and list views, including modifying or deleting multiple items in a list at the same time
  • Mass Delete. (Use Lightning component actions instead.)
  • Custom buttons with a content source of OnClick JavaScript. (Use quick actions and Lightning component actions instead.)
  • Custom buttons with a content source of URL that pass parameters to standard pages in Salesforce Classic, such as prepopulating fields when creating a record. (Use quick actions and predefined values instead).

Search

• Searchable Objects: These features aren’t available.
  • Searches for attachments and documents
  • Searches for Contract Line Item, Resource Absence, Return Order Line Item, Service Resource Skill, Service Territory Member, and Work Order Line Item. These objects can be viewed only as related lists on an object.
• Search Layouts: These features aren’t available.
  • Custom buttons on search results pages
  • Customizations to Event and Task search layouts. Activities are shown as separate events and tasks on the search results page. The Search Layouts for Events and Tasks can't be customized.
• Filtering and Sorting on the Search Results Page: These features aren’t available.
  • Filtering search results for any objects other than: accounts, cases, contacts, dashboards, files, Knowledge articles, leads, notes, opportunities, people, tasks, and custom objects
  • Sorting search results for Groups
  • “Exact phrase” and “limit to items I own” filter options
• Other Differences for Search Results: These features aren’t available.
  • Sidebar Search and Advanced Search. (In Lightning Experience, use the global search bar in the header, and refine results using filters on the search results page for each object.)
  • Search All. (In Lightning Experience, the Top Results page shows the most relevant records for the objects you’re most likely to need. Results are grouped by object. To see results for other objects, click object names on the left side of the page, under Search Results. If you don’t see an object listed under Search Results, select Show More to see all objects available to you, listed in alphabetical order.)
  • Pinning objects on the search results page. (In Lightning Experience, search results appear that are sorted by relevance. Top Results appear on the left side of the results page. Top Results are prioritized for your most frequently used objects and include objects commonly associated with the search term.)
• Lookup Search—user-defined lookup filter fields aren’t available. In Lightning Experience, because lookup search results use the same relevance rankings as global searches, users see the most relevant results first.
• Knowledge Search: These features aren’t available.
  • Attaching external documents to Cases in the Knowledge One Widget. Documents from external data sources, including Federated Search, can’t be attached to cases from the Knowledge sidebar.
  • Making spelling corrections for Knowledge articles optional. Spelling corrections for Knowledge articles can’t be disabled for Lightning Experience.

Duplicate Management

Merge Accounts associated with relationship groups aren’t available in Lightning Experience. Instead, after merging, relate records to accounts manually.

Point-and-Click Customization

• Org Customizations: These features aren’t available.
  • Apex sharing recalculations
  • Quick access menu. (The shortcuts, MRU list, and global action buttons that are in the Quick Access menu in Salesforce Classic are available in different areas of Lightning Experience. Lightning Experience navigation item dropdowns contain MRU lists and action buttons. Favorites contains global shortcuts to items that the user has bookmarked.)
  • Custom JavaScript buttons and links. Check out these resources for migrating your JavaScript custom button and link functionality to Lightning-friendly options.
    • Lightning Experience Configuration Converter—A declarative tool that scans your org for simple JavaScript buttons and links, converts them into point-and-click alternatives, and then deploys everything right into your org.
    • Lightning Alternatives to JavaScript Buttons—Developer-focused Trailhead module with a list of Lightning solutions for your JavaScript button use cases.
    • A bundle of sample Lightning components in GitHub that you can use as Lightning component actions to replace your JavaScript button functionality.
• Object-Specific Customizations: These features aren’t available.
  • Apex sharing rules
  • Apex sharing recalculations
  • These page layout elements: expanded lookups, mobile cards, S-controls, and tags
  • Using the enhanced page layout editor to customize the layout of record pages when viewed in Lightning Experience. (Instead, create a custom Lightning Experience record page with the Lightning App Builder, and assign different record pages to different Lightning apps, record types, and profiles.)
• Object Customizations Not Available in the Object Manager:
  • These triggers aren’t supported:
    • Case Comment Triggers
    • Email Message Triggers
    • FeedComment Triggers
    • FeedItem Triggers
    • Group Triggers
    • Group Member Triggers
    • Group Record Triggers
    • Topic Triggers
    • TopicAssignment Triggers
  • These layouts aren’t supported:
    • Feed Item Layouts
    • Group Layouts
    • Publisher Layouts

• Access these object customizations via the Quick Find box in Setup. For example, from Setup, enter Case Comment in the Quick Find box, then select Case Comment Triggers.

Programmatic Customization

• Visualforce: A common technique in JavaScript to navigate to a new page is to manipulate the window.location value. This technique isn’t possible in Lightning Experience. Use the sforce.one navigation methods instead.

  See Update Visualforce Markup for Lightning Experience in Salesforce Help for some additional considerations.

• S-Controls: This method of customizing the Salesforce user interface is obsolete. If your org depends on s-controls, you must replace them with Lightning components or Visualforce before you can move to Lightning Experience.