migrate-from-model-serving

Migrate MLflow ResponsesAgents from Databricks Model Serving to Databricks Apps.

6|10|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/AnanyaDBJ/databricks-ai-workshops --skill migrate-from-model-serving-ananyadbj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-from-model-serving
Source: https://github.com/AnanyaDBJ/databricks-ai-workshops/tree/main/medium/.claude/skills/migrate-from-model-serving
Command: npx skills add https://github.com/AnanyaDBJ/databricks-ai-workshops --skill migrate-from-model-serving-ananyadbj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires mlflow, databricks-sdk, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the migration process of MLflow ResponsesAgents from Databricks Model Serving to Databricks Apps, enhancing deployment flexibility and operational efficiency.

Core Features & Use Cases

  • Model Serving to Apps Migration: Transforms an existing agent from Model Serving using predict() and predict_stream() to Databricks Apps using @invoke and @stream decorators.
  • Async/Sync Conversion: Offers both synchronous and asynchronous migration options based on user preference.
  • Use Case: Ideal for developers looking to shift from Model Serving's synchronous predict methods to the more scalable, asynchronous Databricks Apps architecture.

Quick Start

Migrate your MLflow ResponsesAgent to Databricks Apps by running 'migrate-from-model-serving --app-name <app-name>'.

Frequently Asked Questions about migrate-from-model-serving

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate an MLflow ResponsesAgent from Model Serving to Databricks Apps?

To migrate an MLflow ResponsesAgent from Model Serving to Databricks Apps, run the migration command with your desired app name. The process transforms existing predict and predict_stream methods into invoke and stream decorators for the new architecture.

Can I convert Model Serving synchronous predict methods to asynchronous Databricks Apps?

Yes, you can convert Model Serving synchronous predict methods to asynchronous Databricks Apps. The migration supports both synchronous and asynchronous operation modes based on your preference when configuring the target app.

Do I need Databricks CLI profiles configured to migrate MLflow agents to Databricks Apps?

Yes, you need Databricks CLI profiles configured before migrating MLflow agents to Databricks Apps. The migration process requires these profiles alongside MLflow and Databricks SDK dependencies to successfully execute the transition.

What is the difference between Model Serving predict methods and Databricks Apps invoke decorators?

Model Serving uses predict and predict_stream methods for synchronous operations, while Databricks Apps uses invoke and stream decorators. This migration enables a more scalable architecture and enhances deployment flexibility for MLflow agents.

Does the MLflow agent migration to Databricks Apps support streaming responses?

Yes, the MLflow agent migration to Databricks Apps supports streaming responses. It transforms the existing predict_stream methods from Model Serving into dedicated stream decorators within the Databricks Apps architecture.