When a GUID is auto generated, it will not create a duplicate in the same column of a given table. Kentico Support, correct me if I'm wrong, but GUID's are used primarily for Content Staging. Don't get me wrong, you can use them to store permenant URLs and getting document info (and I use both of those religiously) but they are a must for Content Staging.

GUIDs are unique by machine, database, table. With that being said, there is nothing stating during an import or insert process you can't turn a few switches "off" and allow insert of a GUID that was not auto generated just like you can with a PK field.

Hi,

The GUID is the same also if you restore a DB. The import is basically just inserting some values to the DB - like when you create a SQL statement to insert values and you will use the same GUID. I do not see any issues with this and as mentioned below, they are mostly used for content staging. However, all the items are checked by several attributes to ensure the uniqueness. This design is ever since and there were no issues in workflow nor other modules with the same GUIDs in deployments with hundreds of sites created using the same web site template, import package. This is ensured by the code.

Best regards,
Juraj Ondrus