# Migration Our script includes a built-in migration tool that helps you transfer data from the phone system previously used on your server. Due to structural differences between various phone scripts, not all data types can be migrated from every resource. The table below shows which data can be successfully transferred from each supported phone script:

DATA	LB-Phone	High-Phone	QS-Phone-Pro	YSeries	QB-Phone
Phone Numbers	✅	✅	✅	✅	✅
Settings	✅	✅	✅	✅	❌
Contacts	✅	✅	✅	✅	✅
Gallery	✅	✅	✅	✅	✅
SMS	✅	✅	✅	✅	✅
Voice Recordings	✅	❌	❌	❌	❌
Recent Calls	✅	✅	✅	✅	❌
Qwuaker	✅	✅	✅	❌	❌
Notes	✅	✅	✅	✅	❌
Mail	✅	✅	✅	❌	❌
DarkChat	✅	❌	✅	❌	❌
Peargram	✅	❌	✅	❌	❌
Alarms	✅	❌	✅	✅	❌
Map Waypoints	✅	❌	✅	✅	❌
Swiply	❌	❌	✅	❌	❌

{% hint style="danger" %} **Why can’t we migrate all data?** We have made every effort to migrate as much data as technically possible. However, in several cases a full migration is not feasible due to structural differences between systems. #### High-Phone Most applications in High-Phone do not support user account creation, while our system requires each app to operate under a user account. Because of this fundamental difference, applications without an account system cannot be migrated. #### QS-Phone-Pro We successfully migrate the majority of QS-Phone-Pro data. \ However, certain individual phones may not be transferred. This is due to the way Quasar stores its data: many values are saved inside the item’s metadata. Phones stored inside gloveboxes, vehicles, stashes, or any container other than the player’s inventory may not be detected by the migration script, and therefore cannot be processed. #### YSeries YSeries contains a critical issue that prevents us from transferring passwords. \ There is a flaw in the password-encryption mechanism where a single encrypted value corresponds to multiple valid password combinations. \ For example: if you create an account with the password VWZt1234, you can also log into the same account with: VWtt1234, VWZZ1234, or VWtZ1234. \ Because of this behavior, securely migrating passwords without compromising account integrity is not possible. {% endhint %} ## How to run the migration? {% stepper %} {% step %} ### Create a backup of your database Please do not skip this step. The migration performs many operations on your database, and if any error occurs, you may need to restore your backup. {% endstep %} {% step %} ### Start Migrate In your server console, use the command `migrate` and provide the name of your previous phone script as the first argument. Supported options: \- lb-phone \- high-phone \- qs-smartphone-pro \- qb-phone \- yseries-phone Example: `migrate lb-phone` or `migrate high-phone` This command will begin migrating data from lb-phone into 17mov\_Phone. {% endstep %} {% step %} ### Confirm Migrate This action is irreversible. For safety, the system requires a second confirmation step. To confirm the migration, run: `migrateconfirm` After confirmation, the console will show detailed logs of the entire process. When the migration is complete, all transferred data will be available inside 17mov\_Phone. {% endstep %} {% step %} ### Restart the 17mov\_Phone Run `ensure 17mov_Phone` in your server console. {% endstep %} {% endstepper %}