A file transfer copies the selected files. It does not automatically export a separate database or update the application’s connection settings. A homepage may still load while account pages or stored content fail.
- Identify the application and ask its maintainer which database belongs to it. Confirm the source and destination services without posting database passwords in a ticket.
- Keep the source available. Arrange an authorised database export and import using the application’s supported migration procedure, including a plan for content created during the move.
- Have the maintainer update the destination connection settings and permissions. Do not import over an existing destination database until its contents and recovery copy have been checked.
Test stored content, login and a controlled write on the destination. Confirm that the intended database received the change before retiring the source. If records are missing, stop new edits and reconcile the migration with the maintainer.
