Map the dependencies
Use the list below as a working checklist. Each item is something you can verify or action directly on your own site.
- Images, videos and fonts.
- Component variants and property controls.
- Stacks, breakpoints and layout constraints.
- Shared libraries and source project ownership.
- Interactions, links and CMS connections.
Once the dependencies are mapped, move the work across in this order.
- Duplicate or copy the smallest reusable unit.
- Place it in the destination project and check missing assets.
- Test every variant and breakpoint with real content.
- Reconnect CMS, links and forms deliberately.
- Decide whether the destination should remain linked or become independent.
A visually identical copy is not necessarily a maintainable component. Check the source relationship before editing it.
Post-move verification checklist
Here are the key things to get right. None of them are complicated on their own, but skipping one tends to undermine the rest.
- Every font renders as intended, not a fallback typeface.
- Property controls still expose the expected editable options.
- Variants respond correctly at each breakpoint after the move.
- Interactions and links point to destination-project pages, not the source.
- No orphaned image or video references remain broken.
Signs a component should stay linked to its source
The list below breaks this down into the parts that matter most. Read through each one and note anything that applies to your own setup.
- It is updated frequently and used across many projects.
- Design changes need to propagate consistently everywhere it appears.
- The destination team is not expected to maintain it independently.