> For the complete documentation index, see [llms.txt](https://boomi.markusschmidt.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://boomi.markusschmidt.pro/boomi-console/commands/comp-components/smart-copy-explained/smart-copy-example.md).
# Smart Copy Example
Imagine you created an API endpoint listener `GET /Contact` and you want to copy this functionality to use it in another endpoint.
The API Endpoint looks pretty simple. But when you look at the explorer pane you'll see the referenced components which include one *shared* component (the REST Client operation) and a *global* component, which is not even visible in this view: the REST Connector Component `REST # MSPro.Services`.
With Boomi's copy feature, and no matter what you decide, copy with or without dependent components, you will end up in a little "mess" that requires a lot of clean-up in the created process.
If you chose *Smart Copy* ...
1. you start to collect the Ids of those components, you want to copy.\ In the sample above: the four green components.
2. Run the `COMP SmartCopy` command with the four ids - your template components:\
`bc comp SmartCopy /c d27f-..,8d82-..,aaeb..,d3e9..`
As the result, you get a smart copy of the template components. You see the result in the picture:
* Only the four green source components have been copied.
* *API Contract 3* references the copied *getContract 2*
* because it was part of the source components
* If you opened the *getContract 2* operation you will see that\
it references the new profiles *j.GetContact.REQ 2* and *j.GetContact.RES 2*.
* API Contract 3 still references the REST connector and operation\
as it was used in the original (source) component
* because these components did not participate in the Smart Copy.