---
title: "Creating a Back to Standard Project"
slug: "how-to-create-a-back-to-standard-project"
updated: 2022-01-03T09:21:38Z
published: 2022-01-03T09:21:38Z
canonical: "success.panaya.com/how-to-create-a-back-to-standard-project"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://success.panaya.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Creating a Back to Standard Project

When planning an upgrade to SAP S/4 HANA, you may be required to review your system, validate existing extensions and modifications, cleanse your code and go back to standard. Your Back to Standard project can be a dedicated-focused or ongoing project.  **Panaya's Back to Standard project will allow you to** - 

- Review your ERP system and validate existing extensions and modifications
- Maximize code cleansing in preparation for going back to standard
  - Remove unused code objects - regardless of how deep they are
  - Remove unnecessary roles - simplifying ERP authorization
- Return clone programs back to standard
- Generate a focused project plan, including all the required activities

---

**To create a new Back to Standard Project -**

1. [Log in to Panaya](/v1/docs/how-to-log-in-to-panaya)
2. [Create a New Project](/v1/docs/how-to-create-a-new-project-1)
3. From the **list of Project Types**, select the **Back to Standard** option
4. If you have access to more than one Panaya Account, **select the relevant Account**from the list  
The selected account will define which set of users you will be able to connect to this project
5. Then, **select the relevant ERP system**  
The selected ERP will define which set of Roles will be available for the project users
6. Now, **set a meaningful name** for the project. This can be changed at a later time.
7. Select the **Project Manager**from the list of users. The user selected here will be granted the **Project Manager Role**, with all relevant permissions defined in the Roles and Permissions console.
8. Now, define the project **Start Date**. Defining the **End Date** for the project is optional.
9. It is recommended to add a **short description** of the purpose and objectives of this project
10. Define the **Farthest last used date**to determine what period should elapse since a program was last used for an Object to be considered an **Unused Object**. SAP recommends 36 months. Industry-standard is 18 months.