In case anyone else has the same issue I did, here is why I was getting this and what I did to fix it.
I was getting a failure on solution import with ("Cannot add a Root Component {guid} of type 60 because it is not in the target system. I used the following post to figure out what the type 60 was: _https://community.dynamics.com/crm/f/117/t/70370.
In my case type 60 was "System Form". However, in my case, the guid was NOT IN the customizations.xml file. Also, by just deleting these lines from the xml files, you will encounter the same issue if you export the solution again.
Once I identified that this was a form, I opened the form editor for another unrelated form and then pasted the guid from the error message into the url for the form editor. This allowed me to identify which form was the culprit. Come to find out it was
a form for an entity that WAS NOT in the solution! This threw me for a bit of a loop. So I added the entity for the offending form to the solution, and when I was selecting the entity components to include, sure enough, the offending form was not visible to
add (suggesting that the form was already included in the solution, even though the entity was NOT included in the solution!). I added the other forms for this entity, and then once the entity was included in the solution, the offending form showed up. I removed
the forms individually from the solution and then removed the entity from the solution and subsequent exports/imports work as expected.
Important to note that the offending entity/form were included temporarily into this solution. Somehow when I removed that entity from the solution, traces of it were still in the xml files.
