Five things, one license
- Migrate — copy tables between the leading databases, with type mapping and on-screen checks before writing.
- Keep in sync — upsert, insert new or update only, nightly or incremental by a date or version column, with compare and resume.
- Integrate — send rows from a database, JSON or CSV to REST (with OAuth2), SOAP, gRPC, a stored procedure, Kafka, Redpanda, Pulsar or RabbitMQ.
- Notify (Postback) — write a row, and once the database confirms it, call your API or queue with the key and whether it was an insert or an update. How it works →
- Automate — every operation becomes a job: command line, Windows scheduler, or the Linux edition's scheduler and REST API. E-mail and webhook on success or failure.
What it looks like in practice
- ERP replacement: the legacy ERP stays live while customers and products are kept in sync into the new one, every night, until cutover.
- CRM that knows right away: a customer created in the ERP is synced and, in the same run, the CRM's API receives it.
- A table into Kafka: rows published to a topic without writing a producer and without touching the source database. See database to Kafka.
- Reporting in the cloud: production stays on-premises; a reporting copy in your cloud is refreshed incrementally.
- Safe test data: production copied to staging with personal data masked on the way. See masked staging copy.
Where it runs
On Windows (desktop or server) and as a Linux edition in Docker, on your servers or in your cloud account. It is not a hosted service: your data goes from your systems to your systems.
What it is not
- Not real time and not change data capture: jobs run at the interval you choose.
- Not two-way sync with conflict resolution: each job has one source and one target.
- No built-in SAP or Salesforce connector: dbSlice talks to them through their APIs or your message queue.
- Not an integration platform with hundreds of connectors: it is a data tool focused on databases that also speaks to APIs and queues.