> ## Knowledge Base Index > Fetch the complete knowledge base index at: https://help.hodi.host/sitemap.xml > Use this file to discover available pages before exploring further. > Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash). # How do I migrate my Odoo from Odoo.sh, Odoo Online or an on-premise server? Coming from Odoo.sh, Odoo Online or an Odoo installed on your own servers, and want to bring your database and documents into a Hodiploy instance? You have two paths: let us handle the migration, or do it yourself from the interface. Either way, it's **included**, with no migration fee. ## Option 1, we take care of it [Write to us](https://hodi.host/contact/) with the details of your current environment, and our team handles the transfer: retrieving the export, setting up the instance, checking it, then switching over. That's the more comfortable option when the migration has to happen on a specific date or with no noticeable downtime. ## Option 2, you do it yourself, from Hodiploy Hodiploy includes a self-service import tool. The principle: **you upload your export to your own server**, over SFTP, into a throwaway account created for the occasion, then you load it into the instance. ### 1. Get your export * **Odoo.sh**: from your project's "Backups" page, download a backup * **Odoo Online**: from odoo.com, request an export of your database * **On-premise**: a `pg_dump` of the database, plus an archive of your filestore ### 2. Create the destination instance Create a fresh Hodiploy instance, with **the same Odoo version** as the source, and the same edition (Community or Enterprise). No need to create a database in it: it will be replaced by the import. ### 3. Open an import session On the instance's page, open **"Import"**, then **"Open an import session"**. Hodiploy then shows you temporary **SFTP credentials**: server, port, user, password. They only serve this upload: they give access neither to a shell nor to the rest of the server. The drop is only open for the duration of the session, and closed the rest of the time. ### 4. Upload your files Send your export with the SFTP client of your choice. Your data goes **straight to your own server**, without passing through or resting on our machines. The **"Refresh"** button lists what has been uploaded, and Hodiploy recognises the nature of each file on its own: Odoo.sh / Odoo Online backup, PostgreSQL database in custom format, plain or compressed SQL, filestore archive or directory. A file it cannot read is flagged as such rather than imported at random. ### 5. Run the import Tick the files to import, then **"Import selection"**. It all happens in one pass, and the database is loaded before the filestore whatever order you ticked them in. > **The import REPLACES the instance's current data, with no way back.** No backup is taken automatically: if the instance already holds something that matters, make one from "Backups" before starting. The instance goes down for the load and **comes back up at the end**. You follow progress on screen, and the activity log keeps the record. A **locked** instance refuses the import: unlock it first. ### 6. Check, then close the session Log in to the instance, check your data, then go back to the import page and click **"Close and erase"**. The uploaded files are deleted and the SFTP drop is closed. ## After the migration, the useful reflexes * **Check email sending.** An imported database arrives with the outgoing mail servers of its previous host. Switch it to MailHog while you test, then configure your real SMTP * **Check the scheduled jobs** before putting the instance into production * **Connect your Git repository** if you have custom modules: the code does not come from the export, it comes from your repository * **Run a first backup** once everything is checked ## A question about your migration? [Contact us](https://hodi.host/contact/): even if you go for the self-service import, our team can assist you or take over at any point.