Migration guide Design System 2.0 (DS 2.0) becomes the Government of Alberta standard in March 2026. New products starting after launch should use DS 2.0. Existing active products should plan their move to DS 2.0 during the recommended migration window, which runs from March 2026 to September 2026.

Migration pathways

The right migration path depends on your product’s context, including team funding and capacity, other delivery obligations, product lifecycle, and the effort required to update. The three pathways are standard migration, late migration, and no migration.

Starting a new product

If your product starts after March 2026, start with DS 2.0. Migration pathways apply to existing products moving from DS 1.x to DS 2.0.

Compare the pathways

PathwayUse it whenRecommendation
Standard migrationYour product has an active funded team and can migrate by September 2026Recommended default
Late migrationYour team cannot meet the standard window because of delivery timelines, dependencies, or capacity constraintsOnly when necessary
No migrationYour product does not have an active funded team and/or is not in a position to upgradeOnly in specific cases

Standard migration

Standard migration is the default pathway for active products. Choose this path if your product has an active funded team and can schedule migration work between March 2026 and September 2026. This is the recommended path for most teams because it keeps your product aligned with the current standard and gives you the best support. Use this pathway when:
  • your product is actively maintained
  • your team can reserve time to migrate by September 2026
  • you want access to the latest templates, components, tokens, and guidance
Plan for work across the product team. Typical upgrade tasks include the library updates, adjusting spacing and typography, and updating custom code to align with the DS 2.0 visual design. This is a significant update and will usually involve design, development, and testing.

Late migration

Late migration is a last-resort pathway for active products. Choose this path only when delivery deadlines, dependencies, or capacity constraints make the standard migration window unrealistic. This path gives your team more time, but it also increases risk and reduces your ongoing support. Use this pathway when:
  • a major delivery deadline blocks migration work
  • critical dependencies prevent the upgrade during the standard window
  • capacity or funding makes the standard window unrealistic
Delaying migration means your product will wait longer to benefit from DS 2.0 improvements. Over time, unresolved issues will accumulate and your product will be inconsistent with the new standard for longer.

No migration

No migration is an opt-out pathway for specific situations. Choose this path only when your product does not have an active funded team and/or is not in a position to upgrade. In these cases, the product may remain on DS 1.x. Teams on this path should understand that the product will not receive DS 2.0 improvements and will not align with the current standard. Support for DS 1.x is limited from March to September and ends after September 2026.

What changes after launch

After the DS 2.0 launch in March 2026:
  • New products should use DS 2.0
  • Active products should aim to migrate by September 2026
  • After launch, web components will move to version 2.x. Although this is a major version update, it does not include breaking changes.
  • Angular 4.x and React 6.x receive limited fixes or features from March to September
  • Support for DS 1.0 ends after September 2026
  • Web components will update to a new major version after September 2026

How to choose a pathway

Use these questions to guide your decision:
  • Is this a new product starting after March 2026?
  • Does the product have an active funded team?
  • Can the team schedule migration work before September 2026?
  • Are there delivery deadlines or dependencies that block the standard window?
  • Is the team prepared to accept reduced support and higher maintenance risk if migration is delayed?
Review the setup steps for developers