I don't know if migrating user security from a site collection to another one is not supported or I'm missing something. I have two site collections http://abc.com/ and http://xyz.com. I use STSADM Import/Export along with Includeusersecurity parameter to export then import from http://abc.com/site/ or any sub-site beneath http://abc.com site collection. This case works. But If I import an exported document library/list to http://xyz.com or any sub-sites beneath http://xyz.com site collection. I've not tried any 3rd party migration tool but I think these tools do support migrating components with security setting across site collections. One of the requirement would be the use of script (PowerShell or STSADM), not 3rd tool.

Has anyone had the same

See http://technet.microsoft.com/en-us/library/ff607895.aspx:

IncludeUserSecurity

Optional

System.Management.Automation.SwitchParameter

Preserves the user security settings except for SPLists that have broken inheritance and item level permissions set.

Thank Trevo. Does this state that the destination site collection has to have default permission and configuration of item level permission? I've checked the destination to make sure it doesn't have permission broken inheritance and item level permission. Everything has been set by default. When running STSADM, it shows the process of importing users, but it actually doesn't then preserve user setting (Created by, Modified By..). All items are modified by the account I use to run the command.

That is normal behavior using Import/Export commands. While security is imported/exported with IncludeUserSecurity, the metadata (Created/Modified By) is not. It ends up being that of the user who imported the object.

That's not correct Trevo. It does work if I import content inside a site collection. I mean after the move, both Created By or Modified By are preserved. It just doesn't work if the destination is a different site collection str

Export/Import has always brought in the items as the user who did the import. IncludeUserSecurity has nothing to do with it. Backup/Restore preserves metadata.

If you have a chance, just test. I've done a dozen of times exporting and importing content inside a site collection. Just in case the destination is a different site collection then it doesn't preserve. The command I'm using is

stsadm -o Export/Import -URL -filename -IncludeUserSecurity.

Again, what you're seeing is expected behavior.

Not sure if I'm fully understanding your thoughts. I'm just wondering if Export/Import (even IncludeUserSecurity in Windows PowerShell) (http://blogs.architectingconnectedsystems.com/blogs/cjg/archive/2012/05/10/HUGE-Permissions-bug-with-Import_2D00_SPWeb-_2D00_includeusersecurity.aspx) doesn't help preserve over site collection. The requirement is to preserve metadata and to keep permission. If not I would just easily open Windows View Explore then drag and drop documents to the new destination. 

You need to use a 3rd party tool if you want to preserve metadata, such as Created/Modified By and Created/Modified times. IncludeUserSecurity does not impact metadata -- only security.

Hi Trevo,

I just really wanted to check to make sure the Export/Import with Includeusersecurity does work inside a site collection. I've just tested many times in case:

- Root site collection: http://abc.com
- Subsite under abc: http://abc.com/test

Both Created By and Modified are preserved. If you are free, please check to see it works inside a site collection. If the destination has a different permission or its permission is inherited from the source then metadata won't be preserved. 

Regards,
-T.s

Created/Modified By is metadata information, not security.