Introducing Genie Migrate for Serverless Databricks launched Genie Migrate for Serverless in Beta, an agent that migrates jobs and notebooks from classic clusters to serverless compute, run via the `/compute migrate` slash command inside Genie with no setup required. The agent scans Jobs and Notebooks to mark each workload's serverless readiness, then proposes translation changes as a diff that is not applied until the user approves it. Databricks said thousands of customers now run notebooks and jobs on serverless and that workloads whose source of truth lives outside the workspace, such as jobs managed by Databricks Asset Bundles or notebooks in Git folders, cannot be migrated yet. Making serverless migrations faster, safer, and effortless by Piyush https://www.databricks.com/blog/author/piyush , Singh https://www.databricks.com/blog/author/singh , Vijay Raja https://www.databricks.com/blog/author/vijay-raja and Feng Lu https://www.databricks.com/blog/author/feng-lu Serverless compute in Databricks offers a simpler, faster way to run your data and AI workloads. It removes the operational burden of managing infrastructure, automatically handling provisioning, scaling, and optimization so teams can focus on their business outcomes. With serverless, organizations can move faster, improve efficiency, and unlock the benefits of cloud-native compute without managing and maintaining complex clusters. Our serverless usage has grown multifold just in the past year, and today thousands of customers run notebooks and jobs on it. Most teams still have a classic fleet they want to migrate over to the serverless world in order to get the cost and operational benefits without managing infrastructure themselves. The work of moving each workload one at a time often prevents our customers from unlocking serverless benefits for their existing workloads. You have probably watched this happen. You pick a job, flip it to serverless, and then get hit with an error, an access-mode incompatibility, a Spark config that does not apply, a library that is installed on classic but not on serverless. What should take an afternoon stretches into weeks, and most of the time goes to translation you have done many times before. Not any more Today we are excited to announce the launch of Genie Migrate for Serverless in Beta , the Databricks agent that migrates your jobs and notebooks from classic to serverless compute - easily and effortlessly. A workload migration becomes a review-and-approve step rather than a research project. Until now, migrating a workload to serverless was manual. The knowledge of how a classic cluster config maps to serverless, which libraries resolve, which Spark confs still apply, and which access mode a workload needs lived in the practitioner's head and in the trial-and-error of running the notebook or job and reading the failure. Genie Migrate for Serverless moves that translation off you and onto the platform, the same way serverless moved provisioning and scaling onto the platform. What stays with you is judgment: whether to migrate a workload now, whether the proposed changes look right, and whether the migrated run is healthy. The agent handles the translation itself, proposing as a diff you review before anything changes. In order to build successful serverless migration tooling, we kept these critical principles in mind: Those three needs shape how the migration agent works, and the workflow below defines how it executes the migration: assess what can move, translate it, and apply the change reversibly. The agent runs from the /compute migrate slash command inside Genie on any job or notebook. It is fully managed, and you need no setup to start scanning. Because Databricks manages it, the agent reads your job config and workload code inside your own workspace. Let’s dive a bit deeper into each of these areas listed above. Before you touch anything, the agent scans your Jobs and Notebooks and marks each workload with its serverless readiness. You see which workloads are ideal candidates for migration instead of auditing the fleet by hand - eliminating painstaking manual discovery and triage work A quick note on external sources: if a workload's source of truth lives outside the workspace, for example a job managed by Databricks Asset Bundles or a notebook in a Git folder, the agent cannot migrate it yet. Support for those is coming soon. Once you pick an eligible workload, the migration agent proposes the changes it needs for serverless and presents them for review before anything is written. Nothing is applied until you approve it. The migration agent effectively translates the pieces that differ between classic and serverless: Every change, including the code rewrites, is presented as a reviewable diff. Before applying, the agent shows a side-by-side comparison of what will change and what will not, an explicit contract you can hand to a manager or an on-call rotation. Check out the latest demo on how to migrate classic workloads easily using Genie Migrate for Serverless. If the agent is unsure about something, for example whether a Spark conf is still needed, it reports the conf rather than removing it. A conf can look unused to a static scan while a listener loaded at runtime depends on it. Silent removal would drop the telemetry a team relies on. The agent leaves that decision with you. Applying a migration is where you are most exposed, so Genie Migrate for Serverless is most conservative here. It performs deterministic checks for correctness today, and deeper runtime validation is coming next. If you opt not to migrate, cloned jobs or suggested changes to notebooks will not be applied. One thing to be cautious about: this does not undo data that serverless runs wrote to production tables in the meantime if you tested with the changed versions. Today the validation is static. It confirms the translation is sound without running the workload, and it is honest about what it has and has not proven. The deeper check is coming next via Sandbox validation. With this, the agent will be able to run the migrated workload in an isolated sandbox without affecting your production tables and compare its output against the classic baseline – so you see a runtime and correctness signal on a critical job before Apply, not after. Migrating one workload at a time in Genie works well for a handful of jobs. For a larger fleet, you can run Genie Migrate for Serverless in the background with the Databricks CLI. Start a migration for multiple jobs from a script using the compute-migrations command group, and the agent builds a serverless working copy of each job without an open Genie session. Your original job does not change until you review and approve its migration, and approving keeps the job's ID, schedule, and permissions. Bulk migration supports jobs today support for notebooks coming soon and requires Databricks CLI version 1.24.0 or above. Let’s put the three key capabilities of the Genie Migrate for Serverless back together: Here is a quick summary of what workloads are good fit today to migrate using the agent, and what’s coming in the future. You can start moving workloads to serverless today using Genie Migrate for Serverless. Here is how to get going: /compute migrate in Genie on a job or notebook to scan what is eligible. The Genie Migrate for Serverless is available today via the /compute migrate command in Genie, on any job or notebook. We are actively shaping the sandbox-validation capability with preview customers, and we continue to evolve the agent to make serverless migrations faster, simpler and easier. Subscribe to our blog and get the latest posts delivered to your inbox.