← Part of Migrate to Gluesync

CONTINUITY AFTER END OF SUPPORT

From Syniti Replicate to Gluesync

Syniti Replicate reached end of support in June 2026. Preserve the CDC workflows your teams rely on and move forward with Gluesync from MOLO17.

Download full guide (PDF) ↗

Gluesync for Syniti Replicate users

WHO THIS IS FOR

Teams still running Syniti Replicate, Syniti Data Replication, or DBMoto.

This page is for teams that still run:

  • Syniti Replicate versions that reached EOL in June 2026.
  • Syniti Data Replication, the earlier product name for the same lineage.
  • DBMoto, the original product name many operators still search for.

If you administer heterogeneous CDC jobs across IBM i, Oracle, SQL Server, and other databases, and need a supported path after vendor support ended, this hub covers the Gluesync replacement and migration sequence.

AFTER END OF SUPPORT

What ended in June 2026

According to Syniti’s public support matrix, Syniti Replicate and Syniti Data Replication versions reached end of life in June 2026. Older DBMoto releases were already retired earlier.

  • No further product updates for those versions
  • No further security patches from the vendor for EOL releases
  • No ongoing vendor support path for the discontinued product line

Your existing jobs may still run on the machines you already operate. What ends is the vendor lifecycle: patches, upgrades, and official support. Staying on an unsupported CDC platform increases operational and compliance risk over time.

Source: Syniti Replicate Support Matrix ↗ . Exact calendar day within June 2026 may vary by notice; MOLO17 uses June 2026 as the public month-level EOL window.

PRESERVE CONTINUITY

Your established CDC processes do not need to stop.

For two decades, organizations have relied on Syniti Replicate—formerly DBMoto and Syniti Data Replication—to move data across heterogeneous systems. Gluesync provides a path forward for the core replication patterns your teams already use, backed by ongoing support from MOLO17.

  • Per-agent change data capture using each database’s native mechanism, including IBM i journals, Oracle LogMiner, SQL Server Change Tracking or transaction-log CDC, and triggers where documented for that agent.
  • IBM i (AS/400) journal capture via native journal APIs.
  • Bidirectional synchronization through two directional pipelines, with explicit entities and mappings per direction.
  • Heterogeneous targets across relational systems, NoSQL, streams, object storage, and data-lake destinations.
  • Deployment choice with installers, Docker or Compose, and Kubernetes on premises or in private cloud.
  • Operations through the Gluesync Core Hub web Control Plane and REST APIs.

MODERNIZE THE PLATFORM

Keep your CDC logic consistent across old and new architectures.

Gluesync is built for hybrid and multi-cloud deployments, connecting established platforms such as IBM i, Oracle, and SQL Server with Couchbase, MongoDB, data lakes, and other modern targets.

  • Extend CDC across relational, NoSQL, and data-lake ecosystems with specialized source and target agents.
  • Deploy configuration with Gluesync Automator when migrating from Syniti metadata YAML.
  • Manage pipelines through the Core Hub web Control Plane or REST APIs.
  • Deploy on premises, in private cloud, or on Kubernetes.
  • Monitor and schedule CDC work from the Control Plane, including group-based scheduling where Conductor is part of the deployment.

COMPARE THE PATHS

Compare your options after Syniti Replicate EOL

Buyers evaluating Syniti Replicate alternatives typically weigh three paths. This is a factual, high-level comparison, not a scorecard of every edition.

Decision Stay on Syniti Replicate post-EOL SymmetricDS-class open source / Pro Gluesync (MOLO17)
Vendor supportEnded for EOL versions in June 2026Community plus commercial Pro options from JumpMindOngoing product support from MOLO17
CDC modelExisting Syniti jobs may still run locallyTrigger-based and other CDC options depending on edition; Pro adds log-based CDCPer-agent native CDC: journals, LogMiner, Change Tracking, transaction-log CDC, triggers, and other documented methods
IBM i / AS/400Existing Syniti journal workflowsEvaluate coverage against your IBM i estateDocumented IBM i journal CDC agents
Migration from Syniti metadataNot applicableRebuild configuration in SymmetricDS conceptsExport metadata.xml, convert to YAML, then deploy with Automator or Bootstrapper
Heterogeneous modern targetsLimited by frozen product lineBroad RDBMS focus; check NoSQL and lake needsRelational plus NoSQL, streams, file and lake agents
LicensingProprietary, unsupported after EOLApache 2.0 community; commercial ProCommercial Gluesync with trial on your infrastructure

How to read this: SymmetricDS is a legitimate alternative many teams evaluate on Syniti EOL queries. Gluesync is for teams that want a supported commercial CDC platform, a documented Syniti metadata conversion path, strong IBM i journal capture, and hybrid targets beyond classic RDBMS-to-RDBMS sync. Choose based on architecture fit, not marketing volume.

A GUIDED TRANSITION

Migration path: from Syniti metadata to running Gluesync CDC

Migrating from Syniti Replicate, Syniti Data Replication, or DBMoto to Gluesync is a guided sequence: export metadata, convert to Gluesync YAML, deploy, validate, then operate.

01

Export metadata.xml

From the Syniti Replicate management console, export the XML metadata that defines sources, targets, tables, mappings, and transformation rules.

02

Convert with the online metadata converter

Upload the XML and generate a ZIP of Gluesync-ready YAML. Conversion runs as a secure asynchronous browser job with no local Python install.

Try the metadata converter →
03

Deploy YAML with Gluesync Automator

Authenticate to Core Hub, select the pipeline, upload YAML, choose deployment options, and watch live logs. Automator embeds Bootstrapper logic.

Get Gluesync Automator →
04

Review and validate

Confirm source and target associations, field mappings and types, and CDC directionality. Test on a limited dataset or staging pipeline.

05

Monitor and schedule

Observe replication metrics and history in the Control Plane, then schedule ongoing work once validation passes.

Read the converter docs ↗

HTML summary of the Migration Guide PDF

The downloadable guide covers the same five steps in printable form: export → online convert → Automator deploy → validate → Control Plane monitor and schedule. Use the PDF for offline handoff; use this page as the indexable overview and deep link into the converter, Automator, and docs.

Migrate to Gluesync: assess → convert → validate → cut over

FREQUENTLY ASKED QUESTIONS

Syniti Replicate migration questions

When did Syniti Replicate end of support or end of life happen?

Syniti’s public support matrix lists Syniti Replicate and Syniti Data Replication versions as EOL June 2026. Older DBMoto versions were already retired. Confirm the matrix for your exact version string.

Is DBMoto the same product as Syniti Replicate?

DBMoto was the earlier product name. The lineage continued as Syniti Data Replication and then Syniti Replicate. Gluesync’s converter and migration materials treat Syniti Replicate, Syniti Data Replication, and DBMoto metadata the same way.

Does Gluesync support IBM i (AS/400) journal CDC?

Yes. Gluesync’s IBM i agents capture changes using native IBM i journal APIs, including QjoRetrieveJournalEntries, with documented journal reader modes. See IBM i journal data capture architecture ↗.

Is Gluesync “all log-based” CDC?

No. Capture methods are per agent. Examples include IBM i journals, Oracle LogMiner, SQL Server Change Tracking or transaction-log CDC agents, and Db2 CDC or trigger-based agents depending on the product path. Always check the agent docs for your source.

How does the Syniti metadata converter work?

Export metadata.xml from Syniti, upload it to the online converter, download the YAML ZIP, then deploy with Automator or Bootstrapper. See the converter documentation ↗.

Can Gluesync do bidirectional replication?

Yes. Bidirectional sync is implemented as two separate pipelines, one per direction, keeping mappings and filters explicit. See Bidirectional Synchronization ↗.

How do I start a trial or talk to MOLO17?

Request a 30-day trial on your infrastructure from Get Gluesync, or contact MOLO17 to discuss architecture and commercials first.

How does Gluesync compare to SymmetricDS for Syniti replacement?

Both appear in Syniti EOL evaluation sets. SymmetricDS offers open-source and Pro editions focused on database replication. Gluesync is a commercial hybrid platform with a dedicated Syniti metadata conversion path, documented IBM i journal CDC, and agents for relational and modern targets. Fit depends on IBM i depth, target types, and whether you want the converter and Automator migration tooling.

Plan your next step

Continue your CDC journey with Gluesync.

Start a trial on your infrastructure, or talk with MOLO17 about migration scope before you install.