Deprecated Concepts & Migration

⚠️ This section documents deprecated features

The concepts on this page are being phased out in favor of the bundle system.

This documentation is maintained to help users migrate existing setups.

What's Deprecated and Why

Deprecated Concept	Replacement	Status	Migration Path
Profiles	Bundles	Deprecated (still works)	Profile → Bundle migration
Collections	Bundles	Deprecated (still works)	Collection → Bundle migration
amplifier-profiles library	amplifier-foundation	Replaced	Use foundation's bundle system
amplifier-collections library	amplifier-foundation	Replaced	Use foundation's bundle system
amplifier-config library	amplifier-foundation	Replaced	Use foundation's configuration
amplifier-module-resolution library	amplifier-foundation	Replaced	Use foundation's module resolution

Profile to Bundle Migration

For Users (Using Profiles)

If you're using profiles via amplifier profile use:

# Check current configuration
amplifier bundle current

# If it shows "Mode: Profile (deprecated)", switch to bundles:
amplifier bundle clear  # Clears profile, defaults to foundation bundle

# Or explicitly set a bundle
amplifier bundle use foundation
amplifier bundle use recipes

For Profile Authors (Custom Profiles)

Convert profile YAML to bundle markdown:

Before (profile)

# profiles/my-custom.yaml
profile:
  name: my-custom
  extends: base

providers:
  - module: provider-anthropic
    config:
      default_model: claude-opus-4

tools:
  - module: tool-filesystem
  - module: tool-bash

After (bundle)

# bundle.md
---
bundle:
  name: my-custom
  version: 1.0.0

includes:
  - bundle: foundation

providers:
  - module: provider-anthropic
    source: git+https://...
    config:
      default_model: claude-opus-4
---

# Custom instructions here

Collection to Bundle Migration

Key Differences

Aspect	Collections (old)	Bundles (new)
Format	Python package with pyproject.toml	Markdown with YAML frontmatter
Loading	`amplifier collection add ...`	`amplifier bundle add ...`
Configuration	`[tool.amplifier.collection]` in pyproject.toml	YAML in bundle.md frontmatter
Composition	Limited (profile extends)	Full (bundle includes)
Complexity	High (Python packaging)	Low (just markdown)

Why the Change?

Problems with Profiles/Collections

Complex packaging: Collections required Python packaging knowledge
Limited composition: Profile inheritance was rigid
Multiple libraries: amplifier-profiles, amplifier-collections, amplifier-config, amplifier-module-resolution
CLI-specific: Designed primarily for CLI, not reusable for other apps

Benefits of Bundles

Simple format: Just markdown + YAML frontmatter
Flexible composition: Include multiple bundles, override as needed
Single library: Everything in amplifier-foundation
Universal: Works for CLI, web apps, services, IDE plugins
Reproducible: Self-contained with module sources

Timeline & Support

Current Status

Profiles: Still work but deprecated. Will be removed in a future major version.
Collections: Still work but deprecated. Will be removed in a future major version.
Bundles: Current and recommended. Default for new users.

Resources

Official Migration Guide: MIGRATION_COLLECTIONS_TO_BUNDLES.md
Bundle System Documentation: Bundles page
Bundle Guide: amplifier-foundation/docs/BUNDLE_GUIDE.md
Old Profile Documentation: Profiles page (archived)
Old Collection Documentation: Collections page (archived)