onnect your client to it by running zenml connect.use the zenml profile list and zenml profile migrate CLI commands to import the Stacks and Stack Components from your Profiles into your new ZenML deployment. If you have multiple Profiles that you would like to migrate, you can either use a prefix for the names of your imported Stacks and Stack Components, or you can use a different ZenML Project for each Profile.

The ZenML Dashboard is currently limited to showing only information that is available in the default Project. If you wish to migrate your Profiles to a different Project, you will not be able to visualize the migrated Stacks and Stack Components in the Dashboard. This will be fixed in a future release.

Once you've migrated all your Profiles, you can delete the old YAML files.

Example of migrating a default profile into the default project:

$ zenml profile list

ZenML profiles have been deprecated and removed in this version of ZenML. All

stacks, stack components, flavors etc. are now stored and managed globally,

either in a local database or on a remote ZenML server (see the `zenml up` and

`zenml connect` commands). As an alternative to profiles, you can use projects

as a scoping mechanism for stacks, stack components and other ZenML objects.

The information stored in legacy profiles is not automatically migrated. You can

do so manually by using the `zenml profile list` and `zenml profile migrate` commands.

Found profile with 1 stacks, 3 components and 0 flavors at: /home/stefan/.config/zenml/profiles/default

Found profile with 3 stacks, 6 components and 0 flavors at: /home/stefan/.config/zenml/profiles/zenprojects

Found profile with 3 stacks, 7 components and 0 flavors at: /home/stefan/.config/zenml/profiles/zenbytes

$ zenml profile migrate /home/stefan/.config/zenml/profiles/default

No component flavors to migrate from /home/stefan/.config/zenml/profiles/default/stacks.yaml...

Migrating stack components from /home/stefan/.config/zenml/profiles/default/stacks.yaml...