Assets & tasks / MERCHANT WORKFLOW
How Can an Agency Move Published Figma Components to a Client Library Without Breaking Existing Instances?
Figma provides a specific workflow for moving published components between files while preserving their relationships to existing instances. The decisive publication choice is Move to this file, not Publish as copy. Figma warns that publishing as a copy creates a new main component and breaks the connection to existing instances.
Preserve component identity, not merely its appearance
An agency may deliver a visually identical component to a client by copying and pasting it into a new file. That does not establish continuity of the original component's instance relationships.
Figma's Move published components instructions provide a dedicated migration path. The workflow includes moving components to the destination file, publishing affected library changes, and accepting updates in subscribed files.
The official publication dialog distinguishes two actions. Move to this file preserves the relationship between moved main components and their existing instances. Publish as copy creates a new main component and breaks the old instance connection for future updates.
This difference matters more than whether the component looks correct in the destination file. An apparently successful visual handoff can still leave the agency library as the update owner.
Plan the migration before moving anything
Record the source library, destination file, component names, subscribed campaign files, and intended ownership after handoff. Confirm that the relevant editors have the access and publication authority required for the documented workflow.
Follow Figma's Move published components procedure in the actual files. Figma recommends publishing the move before making structural changes to components or variants, reducing the number of simultaneous causes if an instance behaves unexpectedly.
During publication, review each moved component's disposition. Choose Move to this file for components whose existing instances must remain linked. Do not use Publish as copy merely because the destination should contain a new library.
Publish the required changes, then inspect the subscribed files' library updates. Figma documents that instances may continue pointing to the deleted source-file component until those updates are accepted.
Hypothetical agency-to-client poster migration
Hypothetical exercise. No library move, publication, or subscriber acceptance was performed. Agency source file AGENCY-ADS-LIB contains published component ProductPoster/Card. Client destination file is CLIENT-BRAND-LIB.
Campaign files CAMPAIGN-SPRING and CAMPAIGN-SUMMER contain instances of the agency component. Fictional SKU TEA-GREEN-80 uses approved image tea-green-front-v2.png and exact product title Green Tea 80 g.
The intended result is that both campaigns retain their content while their component source is transferred to CLIENT-BRAND-LIB after the documented publication and acceptance sequence.
| Record | Expected relationship | Actual state |
|---|---|---|
| AGENCY-ADS-LIB | Former source | Not moved |
| CLIENT-BRAND-LIB | New main-component owner | Not published |
| CAMPAIGN-SPRING | Linked to moved component after update | Not checked |
| CAMPAIGN-SUMMER | Linked to moved component after update | Not checked |
Diagnose broken or pending relationships
If a component was published as a copy, do not claim that the original instances migrated successfully. Inspect their actual component source and plan an authorized correction; the documentation explicitly distinguishes this from the connection-preserving move.
If the correct move was published but CAMPAIGN-SPRING still references the old source, inspect whether that subscribed file has received and accepted its library update. Do not recreate the component as a workaround before checking that state.
If an instance in the destination file updates but an instance in the source file does not, apply Figma's documented source-file update procedure and inspect both relationships separately.
If a campaign loses SKU-specific image or text content, stop the rollout and compare the instance's overrides against the approved product record. A preserved component connection does not certify every commercial field.
For ordinary revision propagation, see the library-update guide. CartVisual does not migrate Figma libraries or verify account permissions.
Use the example with your own product records
The filled records are hypothetical editorial examples. The entry-template row is for your own files, settings and observations; it does not connect to another application.
| Component | Source file | Destination file | Subscriber | Publication choice | Actual accepted update | Actual component source | Next action |
|---|---|---|---|---|---|---|---|
| ProductPoster/Card | AGENCY-ADS-LIB | CLIENT-BRAND-LIB | CAMPAIGN-SPRING | Move to this file proposed | Not accepted | Not inspected | Publish and review subscriber |
| ProductPoster/Card | AGENCY-ADS-LIB | CLIENT-BRAND-LIB | CAMPAIGN-SUMMER | Move to this file proposed | Not accepted | Not inspected | Confirm override and source relationship |
What the sources establish
- Figma — Move published components: Documents connection-preserving moves, Publish as copy, required publication, and subscriber update behavior.
Sources and further reading
Recorded source-review dates are listed individually below. An undated source does not inherit the article’s publication date. Software and platform rules can change; check the current original before acting.
- Figma — Move published components · Review date not separately recorded
Frequently asked questions
Which Figma publication choice preserves existing instance connections?
Move to this file. Figma documents that Publish as copy creates a new main component and breaks the original instance connection.
Do subscribed campaign files need a separate update step?
Yes. Figma documents reviewing and accepting updates after the move is published.
YOUR NEXT CAMPAIGN
Create assets from a clear source
Bring your reviewed source photo or brand brief to CartVisual. Check the current tools, account access and credits before generating, then compare every result with your source.
Create a CartVisual account Open the workspace Check access and credits