After years of wanting way to quickly convert components to group I finally sat down and got it down. This can be useful to turn components into unique objects before performing a solid operation on them /given you don’t use the native solid tools that don’t honor components in the first place).
Awesome! Thanks! 
I can see another great use when importing Revit models into sketchup. For some reason Revit exports each entity as a component (when using the dwg workflow which I have found most efficient), which can be very annoying (for many reasons)
Being able to convert multiple components at a time is going to be very useful!
No longer works in 2026!
No, you are not right. It does work.
Oh! Not sure why it didn’t work for me then.
There could be many reasons: you didn’t install it, you didn’t install it properly, you didn’t install SketchUp itself properly, the migration failed, you’re not using it properly…
Well, I installed it using Extension Warehouse.
I tried restarting Sketchup, but it still doesn’t work.
I just updated to the latest version of Sketchup recently.
I right-clicked a solid component that I imported from Revit and clicked “Component to Group”.
Do you think I need to re-install Sketchup to use this extension?
Open the Ruby Console and see if any errors appear when using the utilty.
Thanks for your reply, Dan. I tested the command on a new file with Sketchup-created components and it totally works, but it’s having issues with the IFC objects I have imported from Revit.
When I try the command on the IFC components, it seems to work, with one caveat: it creates the group in the same place as the component, so I have to delete the component left in place. I think this is why I was mistaken in saying it doesn’t work at all - because I wasn’t aware that the groups were created in the same place as the components, and I was only able to select the components that were still remaining in the place where the new groups were created.
Here’s what the console lists when I run the command on the IFC components:
C:/Users/clayt/AppData/Roaming/SketchUp/SketchUp 2026/SketchUp/Plugins/ene_component_to_group/main.rb:65:in `block in copy_attributes’
C:/Users/clayt/AppData/Roaming/SketchUp/SketchUp 2026/SketchUp/Plugins/ene_component_to_group/main.rb:60:in `each’
C:/Users/clayt/AppData/Roaming/SketchUp/SketchUp 2026/SketchUp/Plugins/ene_component_to_group/main.rb:60:in `copy_attributes’
C:/Users/clayt/AppData/Roaming/SketchUp/SketchUp 2026/SketchUp/Plugins/ene_component_to_group/main.rb:65:in `block in copy_attributes’
C:/Users/clayt/AppData/Roaming/SketchUp/SketchUp 2026/SketchUp/Plugins/ene_component_to_group/main.rb:60:in `each’
C:/Users/clayt/AppData/Roaming/SketchUp/SketchUp 2026/SketchUp/Plugins/ene_component_to_group/main.rb:60:in `copy_attributes’
C:/Users/clayt/AppData/Roaming/SketchUp/SketchUp 2026/SketchUp/Plugins/ene_component_to_group/main.rb:65:in `block in copy_attributes’
C:/Users/clayt/AppData/Roaming/SketchUp/SketchUp 2026/SketchUp/Plugins/ene_component_to_group/main.rb:60:in `each’
C:/Users/clayt/AppData/Roaming/SketchUp/SketchUp 2026/SketchUp/Plugins/ene_component_to_group/main.rb:60:in `copy_attributes’
C:/Users/clayt/AppData/Roaming/SketchUp/SketchUp 2026/SketchUp/Plugins/ene_component_to_group/main.rb:51:in `mimic_definition’
C:/Users/clayt/AppData/Roaming/SketchUp/SketchUp 2026/SketchUp/Plugins/ene_component_to_group/main.rb:13:in `block in convert_to_groups’
C:/Users/clayt/AppData/Roaming/SketchUp/SketchUp 2026/SketchUp/Plugins/ene_component_to_group/main.rb:9:in `each’
C:/Users/clayt/AppData/Roaming/SketchUp/SketchUp 2026/SketchUp/Plugins/ene_component_to_group/main.rb:9:in `convert_to_groups’
C:/Users/clayt/AppData/Roaming/SketchUp/SketchUp 2026/SketchUp/Plugins/ene_component_to_group/main.rb:82:in `block in module:ComponentToGroup’
Your backtrace listing omitted the error message at the top which tells @eneroth3 what the exception is and where in her code the error occurred (well, I guess it happened in her copy_attributes() method.)
In order to add existing geometry to a new group without crashing SketchUp, the new group must be added into the same nesting context as the existing geometry. This is if the workflow was to encapsulate the IFC instance in the new group, copy it’s properties and attribute dictionaries to the new group parent, then explode the instance inside the group.
The other way to do this would be to do this at the top level with a new group and insert a new instance of the component into the new group and repeat the copying of properties. This second workflow would leave the original component definition and instance untouched, and would likely be more stable avoiding the crash “add to group” scenario.
It seems to be an issue with copying certain attributes. You could try using an attribute editor to investigate and isolate what attributes cause issues