Export metadata.xml
From the Syniti Replicate management console, export the XML metadata that defines sources, targets, tables, mappings, and transformation rules.
CONTINUITY AFTER END OF SUPPORT
Syniti Replicate reached end of support in June 2026. Preserve the CDC workflows your teams rely on and move forward with Gluesync from MOLO17.
WHO THIS IS FOR
This page is for teams that still run:
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
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.
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
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.
MODERNIZE THE PLATFORM
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.
COMPARE THE PATHS
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 support | Ended for EOL versions in June 2026 | Community plus commercial Pro options from JumpMind | Ongoing product support from MOLO17 |
| CDC model | Existing Syniti jobs may still run locally | Trigger-based and other CDC options depending on edition; Pro adds log-based CDC | Per-agent native CDC: journals, LogMiner, Change Tracking, transaction-log CDC, triggers, and other documented methods |
| IBM i / AS/400 | Existing Syniti journal workflows | Evaluate coverage against your IBM i estate | Documented IBM i journal CDC agents |
| Migration from Syniti metadata | Not applicable | Rebuild configuration in SymmetricDS concepts | Export metadata.xml, convert to YAML, then deploy with Automator or Bootstrapper |
| Heterogeneous modern targets | Limited by frozen product line | Broad RDBMS focus; check NoSQL and lake needs | Relational plus NoSQL, streams, file and lake agents |
| Licensing | Proprietary, unsupported after EOL | Apache 2.0 community; commercial Pro | Commercial 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
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.
metadata.xmlFrom the Syniti Replicate management console, export the XML metadata that defines sources, targets, tables, mappings, and transformation rules.
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 →Authenticate to Core Hub, select the pipeline, upload YAML, choose deployment options, and watch live logs. Automator embeds Bootstrapper logic.
Get Gluesync Automator →Confirm source and target associations, field mappings and types, and CDC directionality. Test on a limited dataset or staging pipeline.
Observe replication metrics and history in the Control Plane, then schedule ongoing work once validation passes.
Read the converter docs ↗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.
FREQUENTLY ASKED QUESTIONS
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.
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.
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 ↗.
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.
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 ↗.
Yes. Bidirectional sync is implemented as two separate pipelines, one per direction, keeping mappings and filters explicit. See Bidirectional Synchronization ↗.
Request a 30-day trial on your infrastructure from Get Gluesync, or contact MOLO17 to discuss architecture and commercials first.
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
Start a trial on your infrastructure, or talk with MOLO17 about migration scope before you install.