What are the migration paths between them?

I need to clarify your question: conductor-oss/conductor and lingochamp/filedownloader are separate, unrelated projects with no migration path between them.

conductor-oss/conductor is a Java-based workflow orchestration engine for microservices and AI agents (originated at Netflix, maintained by Orkes). It handles durable execution, task scheduling, and agent workflows.

lingochamp/filedownloader is an Android file download library focused on resumable downloads, database management, and multi-threaded download handling.

These projects solve fundamentally different problems and are not designed to migrate to one another.

However, if you're asking about migration paths within each repository:

In conductor-oss/conductor, the CHANGELOG mentions upgrading to Java 17+:

• [CHANGELOG.md:L47-L52] notes that existing workflows remain compatible when upgrading from previous versions; the CONDUCTOR_NASHORN_ES6_ENABLED environment variable is no longer needed as ES6+ is now default.

In lingochamp/filedownloader, there are database implementation changes documented:

• [CHANGELOG-ZH.md:L306-L318] describes decoupling FileDownloadModel from FileDownloadDatabase in version 1.5.4
• [CHANGELOG-ZH.md:L185-L201] introduces NoDatabaseImpl in version 1.6.4 for users who need FileDownloader without a database
• [CHANGELOG-ZH.md:L100-L142] describes the RemitDatabase optimization in version 1.6.9 to reduce database overhead for small, fast-completing tasks

Could you clarify what kind of migration path you're interested in exploring?

FOLLOW_UPS:

• How do I upgrade conductor-oss/conductor to Java 17?
• What database implementations does filedownloader support?
• How does RemitDatabase differ from the default database?