{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":33548,"path":"it-service-management/service-level-management/c_GetStartedWithSLAs.md","title":"Service Level Agreement \\(Legacy\\) engines","bundle":null,"doc_type":null,"release":"australia","body":"\n# Service Level Agreement \\(Legacy\\) engines\n\nIf you are on an earlier version of the SLA engine, you can upgrade to the 2011 engine to make use of the complete service level management functionality.\n\nThe SLA engine has three versions:\n\n<table id=\"table_fjl_jhc_cs\"><thead><tr><th>\n\nSLA engine version\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nEscalation engine \\(pre-2010\\)\n\n</td><td>\n\nTracks only one SLA per task.\n\n</td></tr><tr><td>\n\nThe 2010 engine \\(the Service level management plugin\\)\n\n</td><td>\n\nSupports multiple SLAs per task. Business rules handle the processing of these SLAs while workflows handle notifications. The majority of logic is in a single large business rule called Process SLAs.\n\n</td></tr><tr><td>\n\nThe 2011 engine \\(also part of the Service level management plugin\\)\n\n</td><td>\n\nThe 2010 SLA engine functionality is concentrated into a number of script includes.Provides retroactive pause calculations and enables the customization of SLA condition processing through the use of condition rules.\n\n</td></tr></tbody>\n</table>-   **[Legacy SLA fields](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/service-level-management/c_LegacySLAFields.md)**  \nPreviously, only a single SLA could be attached to a task via the Escalation engine. The information for the SLA was stored in the task table using the **SLA Due**, **Made SLA**, and **Escalation** fields.\n-   **[Upgrade SLA to 2011 engine](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/service-level-management/t_MoveFromThe2010ToThe2011Engine.md)**  \nYou can upgrade SLA processing to use the 2011 Engine.\n-   **[Organize the migration process](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/service-level-management/t_OrganizeTheConversionProcess.md)**  \nThere are several ways to convert the old SLAs to the new Task SLAs.\n-   **[Convert an SLA to an SLA Definition](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/service-level-management/t_ConvertAnSLAToATaskSLA.md)**  \nYou must replicate the default SLA record as a new SLA definition.\n-   **[Reactivate escalation engine](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/service-level-management/t_ReactivateAnOldSLAEngine.md)**  \nEscalation engine is replaced with 2011 SLA Engine.\n\n**Parent Topic:**[Service Level Management reference](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/service-level-management/service-level-management-reference.md)\n\n"}}