DBMS Conversion

DBMS Conversion allows you to convert a database schema from one supported database management system (DBMS) to another.

Instead of rebuilding your database manually, Qubase transforms your schema while adapting SQL syntax and database-specific features to the selected target system.

This feature is useful when migrating applications, evaluating different database platforms, or standardizing database technologies across projects.

Before you begin

Before converting a database schema, ensure that you have:

Created or imported a Database Schema
Validated the schema
Selected a supported source DBMS
Selected a supported target DBMS

[!NOTE] Some database-specific features may not have direct equivalents in another DBMS.

Supported conversions

Depending on your project configuration, Qubase may support conversions such as:

PostgreSQL → MySQL
MySQL → PostgreSQL
PostgreSQL → SQL Server
SQL Server → PostgreSQL
MySQL → SQL Server
SQL Server → MySQL

Support may expand as additional database systems are introduced.

Conversion workflow


Existing Database Schema
           │
           ▼
Validate Schema
           │
           ▼
Select Target DBMS
           │
           ▼
Convert Schema
           │
           ▼
Review Changes
           │
           ▼
Generate SQL

Start a conversion

To convert a database schema:

Open Database Engineering.
Select DBMS Conversion.
Choose the source database system.
Select the target database system.
Validate the schema.
Start the conversion.
Review the converted schema.
Generate SQL for the target database.

What is converted?

Qubase attempts to convert:

Object	Converted
Tables	✅
Columns	✅
Relationships	✅
Primary Keys	✅
Foreign Keys	✅
Constraints	✅
Indexes	✅
Data Types	✅ (when compatible)

Data type mapping

Different database systems use different data types.

Qubase automatically maps compatible data types whenever possible.

Example:

PostgreSQL	MySQL
UUID	CHAR(36) or compatible type
BOOLEAN	BOOLEAN / TINYINT(1)
SERIAL	AUTO_INCREMENT
TEXT	TEXT

Actual mappings depend on the selected target database.

Review converted schema

After conversion, review:

Data types
Constraints
Relationships
Default values
Generated SQL

Some objects may require manual adjustments depending on database-specific capabilities.

Limitations

Certain database features may not convert automatically.

Examples include:

Proprietary data types
Stored procedures
Database extensions
Triggers
Functions

Review the generated schema before deployment.

Best practices

Validate your schema before conversion.
Review all converted objects.
Test generated SQL in the target database.
Confirm data type compatibility.
Keep a backup of the original schema.

[!WARNING] Always verify converted SQL before deploying to production, especially when migrating between different database platforms.