This page is a guide to transferring data between systems without doing a System Transfer, and usually should only be done if the source console you are transferring from is nonfunctional or you only have its SD.
If you do not have a specific reason to follow this guide (i.e. both consoles are usable), do a System Transfer instead.
This guide can potentially cause unexpected results if done wrong. Please ensure you read the steps carefully to prevent these unexpected results from happening.
Additionally, ensure you have read the following three warnings to have a full understanding of the potential risks of this guide.
Do NOT use a movable.sed from Bruteforce Movable as your system movable (in general, but especially not for this guide). Doing so may cause other issues with the system, and WILL result in a guaranteed brick if you uninstall CFW while using that movable. Always keep a backup of your original movable.sed if you do so.
If you have already done this guide at any time before the date 2024-08-11, then uninstalling CFW will brick your console, as FixupMovable (which is done by the script) is required to avoid crashing on stock firmware.
If this applies to you, you can fix stock firmware by booting into GodMode9, copying your movable.sed from 1:/private to the destination console's SD root, copying MovableMoveover.gm9 to the /gm9/scripts/ folder on the SD card, and then doing the instructions from Section II onward on the destination console only.
Any games/savedata/themes/DSiWare that was already on the destination console's SD card will become inaccessible once the guide is completed - you will only be able to use the data transferred over from the source console. To access the destination console's data again, you must undo the moveover.
The script extracts the original versions of those files so you are able to undo it if you need to - do not lose those files.
If the above warning will cause issues for you and you are willing to take extra steps to avoid it, you can instead use ninfs to merge the source console's encrypted files onto the destination console, then rebuild title.db to make any merged games/apps appear.
However, note that even this method will not bypass the issues of using a Bruteforce Movable movable.sed.
To download, right-click/long-press the page and select Save page as... or similar, then rename the downloaded file to MovableMoveover.gm9 if it is not already named that
Instructions
Section I - Prep Work
Follow these instructions on the destination console only.
Power off your console and insert your SD card into your computer
Copy GodMode9.firm from the GodMode9 .zip to the /luma/payloads/ folder on your SD card
Copy the gm9 folder from the GodMode9 .zip to the root of your SD card
Copy MovableMoveover.gm9 to the /gm9/scripts/ folder on your SD card
Create a folder named 3ds on the root of your SD card if it does not already exist
This folder stores homebrew applications and data; it is different from the Nintendo 3DS folder that the console automatically generates
Copy faketik.3dsx to the 3ds folder on the root of your SD card
Copy the source console'sessential.exefs to the root of your SD card and rename it to old-essential.exefs
If you have the source console's movable.sed already in raw form, you can copy that file to the root of the SD card instead
Copy the source console'sNintendo 3DS folder the the root of your SD card
Reinsert your SD card into your console
Section II - Setup Script
Hold Start, and while holding Start, power on your console
Your console will have booted into GodMode9
If you are prompted to create an essential files backup, press A to do so, then press A to continue once it has completed
If you are prompted to fix the RTC date&time, press A to do so, then set the date and time, then press A to continue
Press Home to bring up the action menu
Select “Scripts…”
Select “MovableMoveover”
Follow the prompts in the script, answering any questions that you are asked
Once the script completes your console will have rebooted
Your console may act like it has just been formatted - this does not mean your data has been lost. If it does this, proceed normally through initial setup and get to the HOME Menu
The destination console's original essential.exefs and movable.sed files will be in sd:/gm9/out/MMM_Backup on its SD card. It is highly recommended to back up these files to a safe location.
Section III - Reinstating Apps
Launch the Download Play application
Wait until you see the two buttons
Do not press either of the buttons
Press L+↓+SELECT at the same time to open the Rosalina menu
Select Miscellaneous options
Select Switch the hb. title to the current app.
Press B to continue
Press B to return to the Rosalina main menu
Press B to exit the Rosalina menu
Press HOME, then close Download Play
Relaunch the Download Play application
Your console should load the Homebrew Launcher
Launch faketik from the list of homebrew
Wait until the process is completed
Press START to exit
Reboot your console
The moveover is complete. Congratulations for performing a complex procedure.
