
In some cases, the “domain” may look the same, but as far as Google’s concerned, it isn’t. But they can’t, because of the restriction above. When they do this, the first thing they want to do is to migrate their documents over to the new account. However, reading the forums, it’s a real frustration for a number of organisations who are moving from a single Google account to a full-blown Google Apps For Business setup. I guess this restriction in Google Docs is a security feature of some sort. Please note: as with all software-related issues more than a few months old, things have moved on, so do read all comments at the end of this post thoroughly. Ownership can only be transferred to another user in the same domain as the current owner.” Although I haven’t found a direct solution to this, I have found a just-about-acceptable workaround, so read on.



So, if you’ve just arrived here from a web search, it’s probably because you’ve just come across the Google Docs/Google Drive error message “Sorry, cannot transfer ownership to xxxx.
