In my previous post on upgrading Google Apps to get all Google products and services, I covered what this transition is all about, what conflicting accounts are, and the steps involved in the transition. I recommend checking out that post first if you’re not aware of this important change that Google Apps is rolling out soon (manual rollout has been an option for months now, but now Google is moving the automatic if the webmaster doesn’t do it himself).
In this post, I will talk more about conflicting accounts, especially the part where you need to migrate or migrate data from them to Google Apps. Google provides a data migration tool to migrate data for those accounts, however, it’s not perfect. Should you do that? Are there any warnings? These are the questions I hope to answer in this article.
Google and Google Apps account conflict
The screenshot below, also part of a previous post, provides an overview of what exactly the conflicting account is. It’s basically a Google account with the exact same email address as a Google Apps account and created to access services not supported by Google Apps.
The video below dives deeper into this concept and why these conflicting accounts will no longer work.
So now that you understand what conflicting accounts are, the Google Apps users among you might be a little concerned about the data that you have stored in the various Google services you are using with that account. Well, as shown in the video above, the data will be safe. But there are inconveniences associated with this transition and we will see what they are.
I recently moved Guiding Tech’s Google Apps account to the new infrastructure, and that meant I had to stop using the conflicting Google account I had for products like Google Reader, Google Alerts, and associates. The following steps show the exact process I followed and what I achieved.
Data migration / Steps to create a new account
Step 1. If you have a conflicting account, Google will mention it during the transition and ask you to notify the user of the conflicting account. If any of your users have conflicting accounts, they will have to deal with it themselves by following the steps below. You cannot migrate data for them.
Step 2. Now, when you have completed the conversion process and signed in to the conflicting Google account, it will show the following screen.
Step 3. If you expand the Compare your accounts link, Google will clearly show you that your personal account needs to be renamed.
Step 4. When you continue by clicking Start, Google will give you two options: 1. You can move the data from the conflicting personal account to the organization’s Google Apps account, or 2. You can rename the account to a new Gmail account (or use an existing Google account that doesn’t have a gmail.com address).
I decided to check the migration data option first. So I clicked transfer data to your organization’s account.
Step 5. Here, Google will ask you to log in to the account that is receiving the data (in this case, the Google Apps admin account) and then select the product data from the personal account to transfer to the Apps account.
Step 6. Finally, when you click on the prompt and continue, you will see the products supported by the data migration tool. And as you can see below, it doesn’t support many major Google products.
So that means if I transfer the data to the Apps account, I will have to manually transfer the data for the rest of them..or I can transfer the data for some products and create new accounts for others. As you can see below, data is permanently moved during this process.
I finally decided to create a new Gmail account instead and have all the conflicting account data in there. Much better than automatically migrating data for some products and then manually (and confusingly) transferring data for most others.
In the above step, I chose the first option that says create a new gmail.com address. I don’t own a Google account and use a non-Google or non-Gmail address, but if you do, you can use that as well.
If you’re not an admin then obviously the above process of not using a data migration tool to migrate your data makes more sense, because any data you transfer to Google Apps will be owned by that organization and that organization will have full control over your account.
If you’re a Google Apps admin with a conflicting account (like me), use the data migration tool to migrate your data if most of the products you use are supported by it. If not, then create a new account. You don’t have a choice here really.
Overall, this new Google Apps infrastructure is more beneficial for new Google Apps users who don’t need to use separate Google accounts for different Google products. Going forward, Google Apps will work exactly like a Google account, so they can access all services with their Google Apps login credentials. For veteran Google Apps users like me, it makes for two good tutorials for this site. ????
Categories: How to
Source: thpttranhungdao.edu.vn/en/
