# Backend Migration To migrate from version 1.0 to version 2.0 you will need to replace all the files. No data from the database will be lost in the process but any changes you made on our previous code will be replaced. If those codes are necessary please keep a **backup** of it before replacing the files. To migrate follow the following steps: * Open the control panel * navigate to file manager * open the public\_html folder * From the downloaded zip file look for the zip file named 'digital-hr-file-admin-v2'. Upload this zip file to the public\_html file * Unzip the file and make sure you replace it Note: This zip file is the same as the main file, it just has the .env and .htacces file removed from it so while replacing this files on your public\_html folder, your .env and .htaccess files that you had previously set will remain unchanged. You can upload the other zip file as well but you will need to take backup of .htaccess as well as .env file and later re upload them. Instead of doing such we have made it easier for you by creating a new zip file that does not have these files so while replacing the files, these two files will remain unchanged. Once you have successfully replaced the files, go back to your cpanel and * Open Terminal and enter the following commands * cd public\_html * composer update * php artisan migrate * php artisan db:seed --class=RoleTableSeeder * php artisan db:seed --class=PermissionSeeder * php artisan db:seed --class=AppSettingSeeder * php artisan db:seed --class=GeneralSettingSeeder * php artisan optimize:clear You're all done. Enjoy all our new features. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://cyclone-nepal.gitbook.io/digitalhr/migrate-from-older-version/v1.2-to-v2.0/backend-migration.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.