On this page
The standalone Claude Design site closes on December 14, 2026. Design systems can be migrated into Claude now, while the official guide still says more project-migration details are coming. Chats and comments are not carried over, and standalone public project links stop working after closure. Preserve those items separately and track their replacement destinations before treating the transition as complete.
A Claude Design migration needs separate records for transferred systems and preserved discussions.
What moves, what stays and what expires
Claude's standalone Design migration guide, checked October 15, 2026, distinguishes several kinds of work. They require different actions.
| Design work type | Current documented treatment | Your preservation task |
|---|---|---|
| Eligible design systems | Can migrate into Claude artifacts | Verify each migrated system and its access |
| Standalone projects | Continue working until closure; more migration details pending | Inventory and monitor the project-specific path |
| Chats with Claude | Not carried over | Save needed content separately |
| Comments | Not carried over | Preserve decisions and unresolved feedback |
| Public standalone project links | Stop working after closure | Identify audiences and plan verified replacements |
Design is available across the listed Claude plans, but availability does not make every existing object automatically migrated. Keep a completion status for each object type. An accessible project entry in the Artifacts tab can still open the standalone site rather than a migrated artifact.
Create a preservation inventory first
Before starting, record design-system names, owners, projects, important chat decisions, comments and public links. Add the purpose of each item and the person who will verify its replacement. Avoid copying sensitive content into a widely shared tracking sheet; record a safe reference to the approved storage location.
For links, inventory where they appear: client handoffs, internal documents, a portfolio, a website or a bookmarked review thread. A project can survive locally while its audience loses the path they were given. Link preservation is therefore a delivery task as well as a file task.
Use fields like these:
The example is a planning record. It does not promise that an old public URL can be preserved or redirected. A new destination needs its own access test and an update to the places where the old link was shared.
Migrate design systems with one coordinator
The official guide says one migration brings over the organization's design systems, including other people's. Anyone who can use Claude Design can start it. Choose one coordinator so people understand who will inspect the results and handle failures.
Start from the Artifacts page and use “Migrate team design systems.” Review the result lists instead of assuming the operation moved everything. The guide identifies Migrated, Couldn't be migrated and Not started states. Record each object's actual outcome.
The migration retains owners and sharing, with the Primary Owner taking ownership if the original owner has left. Published non-private systems become available across the organization. Inspect that visibility with the owner before describing a system as private or restricting its audience in your inventory.
Empty systems and systems created from a built-in starter theme are excluded, even if the theme was edited. Put those in a separate disposition rather than repeatedly retrying them as unexplained failures. The original systems remain unchanged in the standalone version until closure, which gives you a source for comparison.
Resolve failures without overwriting new work
For an unsuccessful system, use the guide's check in the standalone version and review the listed reason. Files may need changes to size, name, type or readability. Some blockers belong to an organization owner because they involve feature or role settings.
Fix the identified cause, then check and migrate again. Preserve the original failure reason and the successful result. Do not claim completion from merely pressing Migrate a second time.
The guide says a later migration skips a system changed in Claude, preserving those newer edits. Treat that as a conflict to review, not a broken migration to overwrite blindly. Compare the versions and decide which work should be retained before taking any replacement action.
Use the artifact admin guide to check organization Artifacts and Design systems settings. An owner controls the organization default and wider sharing; standalone Design administration and artifact administration have separate permission boundaries.
Save chats and comments separately
The migration guide explicitly excludes chats and comments from carryover. Before closure, save the content your team needs in an approved location and keep its relationship to the design clear. A screenshot of a finished screen does not preserve the discussion that explained why it was approved.
Prioritize decisions, requirements, unresolved feedback and references that another editor would need. Record the source object and author or context where appropriate. Preserve attribution and avoid turning tentative comments into final requirements merely because they were copied into a new document.
After saving, have the intended editor open the preserved material and use it to understand a representative design decision. That check tests usability of the preservation, not just existence of a file. Mark missing or unreadable content as a remaining item.
Keep the backup procedure separate from any future automated project migration. New project guidance may cover the design object while still leaving historical conversation material outside the transfer. Review the current official boundary when that guidance changes.
Replace links through a controlled handoff
The official notice says standalone public project links stop after the site closes. Do not promise that the old URLs redirect to equivalent public artifacts. The documented site-level destination change does not establish per-project link preservation.
For each old link, identify a replacement only after the intended work is available at a verified destination. Open it using the intended viewer's access level. Confirm that it shows the correct version and contains the material the audience needs.
Then update the authorized source documents or website references where you control them. When a link was sent to someone else, prepare a clear handoff with the replacement and purpose. This guide describes the workflow; it does not send messages or update any real link.
Do not publish sensitive material merely to avoid a broken public link. Choose the replacement sharing scope based on the content and audience. Test both the intended viewer and a viewer who should have no access.
Validate the new artifact before closing the record
Compare the migrated design system with its original: files, fonts, colors, components, owner and sharing. Create or inspect a representative design using it and verify that the result matches the requirements that matter to your team.
A migration result page can establish that a system was transferred. It does not prove every downstream design renders correctly or that a former public audience can open it. Keep transfer, content validation and audience access as separate checks.
A synthetic inventory containing two saved systems, one project, one unsaved chat, one unsaved comment and one public link without a replacement was checked locally. The review flagged three attention items: the unsaved chat, unsaved comment and unresolved public-link destination. Those are author-defined preservation rules; no real Claude account migration was performed.
Use the same pattern for your actual inventory. Empty fields should remain pending rather than become automatic passes. Projects awaiting official migration guidance can stay in a named pending state while you complete the independent preservation work.
Build a migration register in Atoms
Atoms' AI app builder can help prototype an inventory app that makes the object-specific checks visible. Start with synthetic records and review its status rules.
The QA dashboard guide supplies a related way to present observable acceptance. Atoms supports generating and iterating the app; the actual source backups, migration results and access tests remain evidence you must supply.
Check the prototype against the six-row example and verify that it does not label the pending project as migrated. Before entering real team data, review authentication, persistence, permissions and retention for the deployed application.
Conclusion
Migrate eligible systems, preserve conversation decisions separately and plan verified replacements for public links. Keep project transfer pending where the official path remains unspecified. Build the preservation register in Atoms to coordinate those checks before the standalone site closes.
Frequently asked questions
01Q1: Does migrating systems also migrate every project?
The current guide separates them. It supports system migration now and says more project-moving details are coming. Keep your project inventory and preservation tasks active until their actual path is documented and verified.
02Q2: Will existing public project links continue working?
The official guide says they stop after closure. Do not promise a per-project redirect; prepare and test a replacement destination with the required audience access.
03Q3: Are chats and comments included?
They are not carried over under the current migration guidance. Save needed content separately before closure, preserving its context and relationship to the design.
