anchor.diff:  ** Solutions
   ** Ideas
   ** https://developer.salesforce.com/docs/atlas.en-us.noversion.service_sdk_android.meta/service_sdk_android/android_sos_overview.htm[SOS]
  -** Knowledge (can be used, bot lots of functionallity is unavaliable at this moment)
  +** Knowledge (can be used, but lots of functionality is unavailable at this moment)
   
   If your business is OK to switch to Salesforce Classic to continue to use those features - then you'll be fine to proceed with customization changes
   
  
positive.code: :hp-image: https://c1.sfdcstatic.com/content/dam/blogs/us/August2015/Home%20Screen.png
  :hp-tags: Development, Lightning, Aura
  
  Almost two and a half years has passed since Salesforce announced their new and sexy Lightning Experience (a.k.a. LEX) - I found this amazing, but lots of organizations are still using Salesforce Classic UI! It's true, that some features are still unavailable for Lightning Experience, and some of the classics users still should postpone their migration to modern LEX, but it seems, that not only unreleased features is a problem with migration, but also some massive coding concepts have changed since then. This article will cover both - what's still not released in LEX, and what changed developer needs to apply to existing customization so this migration won't be unsuccessful for business.
  
  == Chapter I: Pre-Development Considerations
  
  Prior to development, you need to check, if it's possible to migrate to LEX - by Salesforce features which are already in the organization. Salesforce development team are doing their best to deliver most of the functionality to LEX, so, it only means that you can plan your migration pretty soon.
  Below are the list of the features, which are *not* available in LEX:
  
  * General Platform
  ** *Javascript buttons*
  ** Mass Actions On A Records List View
  ** Mass Inline Editing for List View
  ** *Recylcle Bin*
  ** Printable View
  ** *Manual Sharing*
  * Sales Cloud
  
negative.code:         var caseObject = component.get("v.record");
  
          if (caseObject.Type != "Social") {
              component.set("v.recordError", "error message for non-social case");
          } else {
              caseObject.Type = "Social Plus"
              component.set("v.record", caseObject);
              component.find("recordLoader").saveRecord(
                  $A.getCallback(
                      function(saveResult) {
                          //You can add error handling here
                      }
                  )
              );
          }
      }
  })
  ----
  
  A Final step will be simple - create action with this component for Case sObject and add it to the layout! No Apex/3rd-party library required.
  
  === Visualforce Pages
  
  Every scenario here is pretty unique, however, few common page types can be separated: Reports pages, PDF-rendered pages, and new/edit/view papes. For the PDF we'll keep it as it is - as no changes and no ability to render lightning components as a pdf. But for the report-like and new/edit/view pages we have to change it to the lightning UI;
  
  ==== 1. Set the lightning styles
  
  