Export metadata.xml
From the Syniti Replicate management console, export the XML metadata that defines sources, targets, tables, mappings, and keys.
← 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.
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 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
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.
Export
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 →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 →Review and validate
Confirm source and target associations, field mappings and types, and CDC directionality. Test on a limited dataset or staging pipeline.
Monitor and schedule
Observe replication metrics and history in the Control Plane, then schedule ongoing work once validation passes.
Read the converter docs ↗Take the full migration guide with you
The Migration Guide walks through the same five steps in detail: export your metadata, convert it online, deploy with Automator, validate, then monitor and schedule in the Control Plane. Download it to share with your team or keep it at hand during the migration.
CUSTOM SCRIPTS AND BUSINESS LOGIC
Global scripts or custom code in Syniti? Our AI agents convert them.
Many Syniti Replicate and DBMoto jobs run global scripts, replication scripts, or script functions written in Visual Basic .NET or C#, with your own business logic inside. That is not a blocker: MOLO17 has AI agent skills made specifically for converting that code to Gluesync, and our Professional Services team runs them with you.
The converter handles your configuration
The metadata converter
is static: it turns metadata.xml into Gluesync YAML.
Replications, field mappings, types, snapshot WHERE clauses,
keys, and IBM i journal checkpoints carry over, and a script that uses
the RRN gets the RRN set up as the key.
Business logic needs more than a static converter
A script is code, not a setting. Converting it means understanding the rules it enforces and rewriting it for another runtime, which no static converter can do from a metadata file. That is why scripts take a dedicated step.
AI agent skills built for Syniti scripts
Our team runs AI agent skills made specifically for this task: they read your Visual Basic .NET and C# scripts and rewrite the logic as Gluesync User Defined Functions ↗ in Java or Custom Field Functions ↗.
Reviewed and tested before cutover
MOLO17 engineers review the converted functions with your team, attach them to your entities in the Fields Editor ↗, and test them against your data next to the converted YAML.
Running custom scripts in Syniti? Talk to Professional Services.
Tell us which jobs carry scripts or functions. We scope the conversion, run the AI agent skills on your code, and deliver tested Gluesync functions ready for your migration.
FAQ
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 end of life in June 2026. Older DBMoto versions were already retired. Check the matrix for your exact version.
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. The Gluesync metadata 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 with the native IBM i journal APIs, including QjoRetrieveJournalEntries, with dedicated journal reader modes.
Is Gluesync “all log-based” CDC?
Capture methods are per agent and use each database's native mechanism: IBM i journals, Oracle LogMiner, SQL Server Change Tracking or transaction-log CDC, and Db2 CDC or trigger-based agents, depending on the source.
How does the Syniti metadata converter work?
Export metadata.xml from Syniti, upload it to the online metadata converter, download the ZIP of Gluesync YAML, then deploy it with Gluesync Automator or Bootstrapper.
Does the converter translate my Syniti global scripts or custom functions?
Not the converter itself. It translates configuration statically: replications, mappings, types, keys, and journal checkpoints. Scripts written in Visual Basic .NET or C# carry business logic, which is rewritten as Gluesync User Defined Functions or Custom Field Functions. MOLO17 Professional Services converts them for you with AI agent skills made specifically for Syniti scripts.
Can Gluesync do bidirectional replication?
Yes. Bidirectional sync runs as two pipelines, one per direction, so mappings and filters stay explicit for each direction.
How do I start a trial or talk to MOLO17?
Request a 30-day trial on your infrastructure from the Get Gluesync page, or contact MOLO17 to discuss architecture and commercials first.
How does Gluesync compare to SymmetricDS for Syniti replacement?
Both appear in Syniti end-of-life evaluations. SymmetricDS offers open-source and Pro editions focused on database replication. Gluesync is a commercial hybrid platform with a dedicated Syniti metadata conversion path, IBM i journal CDC, and agents for relational and modern targets.
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.