Docs / Migration Guide
This guide covers all paths to Maree-DB - from a simple connection-string change to a full Oracle migration.
For MySQL, PostgreSQL, and Redis: just change your connection string. Your application doesn't know the difference. (SQL Server TDS connectivity is in final development - migrate your data today with the export/import path below.)
Use Oracle's own tools - Data Pump (expdp) or a CSV/SQL export. Your Oracle database only ever gets read.
Translate any Oracle type to its Maree-DB equivalent with the built-in, tested converter:
Load the converted schema + data into Maree-DB with the standard psql or mysql client, or the REST bulk loader.
Column types convert automatically. PL/SQL packages and stored procedures are ported by hand - the free compatibility assessment from SupportCALL tells you which ones need attention. Automated PL/SQL translation is not a shipped feature.
Your Oracle database is untouched throughout - the workflow only reads from it, never writes. To revert, just point your app back at Oracle.
MongoDB collections load into Maree-DB's document model. Export each collection with MongoDB's own tool, then load the JSON over the REST endpoint.
BSON documents become JSONB columns; nested objects and arrays are preserved as JSONB.
Consolidating several databases into one Maree-DB? Migrate each with its own native export, then load them into the same instance - SQL sources over the wire, documents/KV over REST.
On the roadmap - not yet wired. A future release will add fully-automated live connectors that stream a source's binlog/WAL in real time so you cut over at zero lag. Today, use the export -> convert -> import workflow above (your source stays online during export). The command below is the target design.
For cPanel hosting environments, the Maree-DB cPanel plugin takes over the MySQL socket transparently. All sites continue working.