What changed?
Salesforce retired the Classic Mobile app on all supported platforms and devices on December 1, 2017. You should transition your users to the Salesforce1 downloadable mobile app or deploy custom mobile apps to address their existing and future mobile needs.
What happened after the End of Life date?
The Salesforce Classic Mobile app was removed from Google Play and the App Store on December 1, 2017. The retirement removed all user access to existing installed instances of the iOS and Android mobile app. Users were be logged out of the mobile app with no ability to log back in.
NOTE: In addition, iOS 10 and Android 7.0 (Nougat) was the final mobile OS versions tested for compatibility with Salesforce Classic Mobile. Issues with any mobile OS versions newer than iOS 10 and Android 7.0 will not be addressed.
Was I be able to access my data after the retirement date? What happened with data that remained in the Salesforce Mobile Classic app?
Data entered within the Salesforce Classic Mobile app is synchronized periodically to the user’s Salesforce org. If data entered into the mobile app has not yet synchronized to the user’s Salesforce org before the mobile app retirement, this data will remain within the mobile app, and it will not be accessible by admins or users. The majority of data in the mobile app is a mirror of existing records in a user’s Salesforce org. Users should ensure that all data entered into the mobile app is reflected in their org well before the retirement date on December 1, 2017.
What action did customers need to take? What would happen if the action wasn't taken?
Customers should begin evaluating mobile app alternatives as soon as possible and transition their users to the Salesforce Mobile App (formerly Salesforce1) downloadable apps or deploy custom mobile apps to address their existing and future mobile needs.
If no action is taken before the retirement date, users will lose all access to their data in the Salesforce Classic mobile app, and they will be logged out of the app with no ability to log back in.
What was the replacement, and what was the difference between the legacy product and the replacement?
The Salesforce Mobile App (formerly Salesforce1) downloadable apps or custom mobile apps are alternatives for the Salesforce Classic Mobile app.
When comparing the Salesforce Classic Mobile app to the Salesforce Mobile App (formerly Salesforce1), the key difference is the nature of offline support functionality.
Salesforce Classic uses a briefcase model for determining offline data sets and has full record type and page layout support for offline create and/or edit, which gives admins the ability to define which objects and/or records are available to offline devices.
Salesforce1 uses an intelligent, predictive model, based on recently viewed records and upcoming activities to determine offline data sets. Admins aren’t able to define offline data sets as they can for the Salesforce Classic mobile app.
Use the following table, which outlines the key feature differences between Salesforce Classic and Salesforce Mobile App (formerly Salesforce1), to help you evaluate which replacement option will meet your existing and future business needs.
Salesforce Classic vs. Salesforce1 Feature Differences
|
Feature |
Salesforce Classic |
Salesforce Mobile App (formerly Salesforce1) |
|
Offline Records |
Available – Admins define mobile configurations which specify the objects and records that are available and maintained on mobile devices. |
Available – For improved performance and a better user experience, we are more intelligent about what we cache, based on what users are currently using. The app automatically caches recent tasks and dashboards and the 30 most recent records for the 5 most frequently used objects listed under “Recent” in the Salesforce1 navigation menu. |
|
Create and Edit Records Offline |
Available | |
|
Page Layouts |
Available – Control which parts of the object layout appear to the mobile app via mobile configuration. |
Available – Standard layouts only, without the ability to create layouts specifically for mobile. |
|
Mobile Permissions |
Available – Ability to restrict create, edit, and delete permissions per object just for mobile via the Classic Mobile config without applying these same restrictions upstream to the Salesforce web application. |
Available – Shares the same level of control as defined for the Salesforce web application via profile and permission set permissions for create, edit, and delete, with no ability to customize just for mobile. |
|
Custom List Views |
Available – Ability to create object list views specifically for mobile. |
Available – Displays the Salesforce web application’s object list views. |
Is there a cost for Salesforce1?
There is no cost for Salesforce Mobile App (formerly Salesforce1).
Why was this product retired?
Salesforce focused its development efforts on Salesforce Mobile App (formerly Salesforce1) to improve the overall mobile user, developer, and deployment experience.
Was I be able to renew or add users to my Salesforce Mobile Classic subscription until the End of Life date?
Yes, existing Salesforce Mobile Classic customers will be able to renew or add users as needed until the End of Life date on December 1, 2017. Customers should contact their Salesforce account team with further questions.
What if I have a pre-paid subscription that extended beyond the End of Life date?
Pre-paid subscriptions will be credited for the portion that extends beyond the End of Life date on December 1, 2017. You should contact their Salesforce account team for more details.
Where can I find more information?
000383171

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.