Migrating in
Import a database
Bring an existing database over from any VPS or webhost straight into a managed Lofenta database. You can connect directly to your old database and let Lofenta copy it, or upload a .sql export if you already have one. Available on the Developer and Team plans.
What it does
Database import takes the data from a database you already run somewhere else and loads it into a fresh managed database on Lofenta. Tables, rows, and structure come across. Once it is in, Lofenta runs and backs up that database for you, and you can browse it in Database Studio or connect your app to it.
Which databases
Lofenta imports into PostgreSQL and MariaDB. MySQL databases come in through the MariaDB path, which is the same wire format, so a MySQL export from a typical webhost loads fine. Pick the engine that matches where your data lives now.
Two ways to bring it in
Connect directly
Give Lofenta the address of your current database and it copies the data over for you. Best when your database is reachable from the internet, for example a database on a VPS you control.
Your source needs to allow remote connections. On a webhost that is the Remote MySQL setting.
Upload a .sql file
Already have an export? Upload the .sql file and Lofenta loads it. Best when your database is not reachable from outside, which is the common case on shared hosting.
Export from phpMyAdmin or with pg_dump, then drop the file in. Large files upload in chunks, so a big dump is fine.
What the direct connection needs
When you connect directly, Lofenta needs the same details a database client would use to open a connection. Each one has a reason:
Host and port
Where the database is reachable. An IP or hostname, plus the port it listens on. PostgreSQL is 5432 by default and MariaDB or MySQL is 3306. This is the address Lofenta connects to.
Username and password
A database user that is allowed to read the data. Lofenta signs in with these to pull the tables across. A read-only user is enough. The password is used only for the import and is not stored afterwards.
Database name
Which database on that server to copy. One server can hold several, so this tells Lofenta exactly which one you mean.
From a VPS or from a webhost
The import asks where your data is coming from and sets sensible defaults. Coming from a VPS, it assumes PostgreSQL and leads with a direct connection, since you usually control the network. Coming from a webhost, it assumes MariaDB or MySQL and leads with a .sql upload, since shared hosts often block outside connections. You can override either choice.
Security
- Credentials are used once. The database password you enter is used only to run the import and is not kept afterwards.
- Uploads are checked. Every
.sqlfile is validated before it runs, so a broken or unsafe dump is caught rather than loaded blindly. - Read only at the source. A read-only user on your old database is all Lofenta needs, so nothing on the source is changed.