Before making the transition

Read more about why we're moving to Flyway and its benefits. If you have any questions about transitioning to Flyway Enterprise, get in touch with our Database DevOps Team.

Learn more about about Flyway Desktop by watching this 6.5 minute video for a quick overview.

Flyway Desktop is a standalone tool since it supports over 50 different databases. It integrates directly with Git version control systems. If you are using another version control system (VCS), we still recommend trying Flyway Desktop, but you'll need to use your own VCS cmdline or VCS tool for any version control operations that you need to perform.

Before making the transition to Flyway, there are a few options to try it out:

Create a new project in Flyway Desktop that goes to a new Git repository/folder. Link your development database or a sample database. If you're using your existing development database, this won't bring over the Git history of your objects that have been built up using SQL Source Control, but is a good way to try Flyway before making the full move.
Try out Flyway with our Flyway AutoPilot sample project.

What's next?

Import your Source Control for Oracle project to Flyway
Learn more about:
- Deploying - How to deploy changes manually or automatically

Any Questions?

If you have any questions about transitioning to Flyway from Source Control for Oracle, please get in touch with our Database DevOps Team.