Just save the master component to a local file. Locate component in the components pane. Right click and select make local. Then copy component to the master library XD you wish. Boom! That will remove the link to the master library.

🤙

Seems like there is now a solution for this problem. If you locate the linked component inside resources panel now you have the option to apply local changes to the component. Im sorry for the screenshot in italian

Hello guys,

To answer the question, we need a tip for it instead waiting for new function from Adobe XD.

Let me show you how to move assets (master components) to another file:

1/ Copy the component that you want to move on the other file.

2/ Paste it to new file.

3/ Delete the main component in source file.

4/ Back to the copied component in new file, now right click to choose "make local"

Now you had the new main component in new file, the problem only now is everything included the old one deleted need to change into a new main component.

You have to change all into new main component that relocated in new file.

Everything done ;)

Well... nothing more to add. 80% of my working time in a XD project is wasted only to overcome usability issues like this.

I've to improvise tricks and workarounds, bloat components with hundreds of random stuff and states to make it look and behavior as expected, only to “Ungroup component” and start from zero again, when customer wants a name change in a button or a color variation in a hover state.

Obviously, no room for creativity, nor inspiration.

For real, Adobe. XD has come so far! Components are awesome, but the linking thing quickly becomes spaghetti. Please do something!

The following worked for me but we need a function built in to either transfer the component from the original master doc to the current doc (library file) as the master component or to copy as a master into the library file.

Workaround for me:
Delete the component in the source document. Click "Update" in the Assets panel on the destination (new document) and select "Make Local Copy"

Make Local Copy absolutely should be available even if the component is currently linked.

The following work around solved the issue of having moved library files that resulted in broken links.
I had 200+ broken links (Library is Missing) from the work file.

1. Copy the artboards from the file and paste into the library

2. Copy the same artboards you pasted into the library and paste back into your file.

3. That's it. This fixed all broken links components.

You can delete the second copy of the artboards you pasted back.

I am facing same issue. Copied components from one file to another and making it local does not work. All states created are lost and it is a rework. This is a huge time waste. please find a solution on this. This has been must have solution.

Is there a workaround for this that works?

Please fix this - I see it as a huge "fail" that you can not move a master component to another file.

workaround

1- created a new document
2- copy the artboards( from the working document with masters)
3- pasted designed screens in the new document ... all master components used remained in the original file and were linked to the new document
*rename the files

=)

This issue is becoming a huge time-waster. I've used the workaround of copying, deleting, making local before, but today, for some unknown reason, I'm not getting "Make Local" as an option. And Edit Main is greyed out. It looks like I have no choice but to recreate this component completely which is a problem since it is already used in multiple places in the new file. You really should be able to easily disconnect a component in any file from its originating Main component and retain all of the states you've spent time defining. I would also like to be able to re-assign an instance to a different main component then reset to main as needed.

I am with Ash De on this one. Making components local indeed does make a component local however it remains as a copy of the master and you have to redo the whole process of making it a master component again in the new file.

Making components local with 'Make local' does not solve the issue. Changes in this new local component do not reflect in all other files. We have a big team that is working on one project which has more than 80 pages. My team members have created additional components in their files whenever required. Now for the design system, I can not gather all master components in one file.
Adobe please help us. Give the facility to move/export/relocate the master components.

Okay, update on my previous comment:

See the three screenshots I have attached.

1. The first linked component did not give me the option to 'make it local'.
2. The second did give me the option.
3. When I highlighted them both I was given the option 'make local' and it worked...

😏🤔😣 While my issue is now solved I am baffled as to why this was the workaround, but thankful that I stumbled across it! Maybe this will help some others out there...

In the past, I have copied components from one doc to another and when I hover the item in my document assets I have the option to 'Make local component'. Today I tried this and I only get the options:
1. Edit Main in source.
2. Highlight on canvas.

Why today when I am having a major tidy-up and merging multiple files does this happen? Am I doing something wrong (It's never been an issue for me in the past)? 😖 So frustrating Adobe!!!!

1. You copy the component to another document
2. Right-Click the asset and select "reveal component in "assets"
3. Right-click the component in the assets panel and select "make local component"

Hi Everyone, locate your component, right-click just click "Make Local Component", works a charm!

Huge blocker for me right now! Please, prioritize this feature Adobe.

Initially, I created my design system in the same file and also added other screens in the source document. Later I decided to move the design system to the new file and all the original components should remain linked but this didn't happen. It's a blocker for me.