Moving a domain with Computer Use — getting it done and learning along the way

I wanted to move a domain from a personal GoDaddy account to a company account and organise the connected services. It is a one-off task that needs doing, although I do not manage domains every day. Just learning the settings, dependencies, and order of actions would have taken me a lot of time.

At times like this, I let AI — artificial intelligence — operate the panels through Computer Use: the ability to act in a computer and browser interface. I watch what the agent does and learn while the task is being carried out. This lets me work through it faster without having to master the whole subject first.

Why I choose Computer Use for a one-off task

I do not need to become a domain specialist to organise my own configuration. I do need to understand what I am changing and what it affects. Working with an agent lets me learn these things through a concrete example: I see the panel, the action, and its effect.

Another big benefit is considering things I would not have thought of as a beginner. Behind the instruction “move the domain” were website settings, email, files, user accounts, and scripts. AI also helped identify those dependencies before we started making changes.

The agent checked open panels, prepared operations, and, after approval, performed the successive steps. I defined the scope, indicated what had to remain, and made decisions. I could move the work forward while gaining a better understanding of the configuration.

Below, I show specific situations from this process. The GoDaddy domain transfer was confirmed; switching the old email addresses still had no final confirmation. I describe the state in the saved work record, omitting domain names and private data.

First we established what actually had to move

My initial instruction also included closing the old Workspace. After checking, however, it turned out that one person still had to use that organisation. Their account and data had to remain. We were moving the data of two other users to the company Workspace.

That changed the plan. The old organisation could not be treated as an empty container to throw away. Users, domains, and services had to be separated, while retaining the ability to administer what remained.

The review also revealed a shared drive, spreadsheets, a script, and access for a technical account. A small number of files did not determine whether something was unnecessary. One small spreadsheet can be the data source for a running application.

Before a similar task, I would ask AI to compile this:

DNS is the system that helps route traffic for a domain name to the right service. A registrar such as GoDaddy is responsible for domain registration. The DNS provider and hosting provider can be different companies. Moving an address therefore does not have to mean moving the website.

In my session, checking showed that the running website used Vercel and Supabase. Its existence was not therefore a reason to retain every old product found in GoDaddy or Google Cloud. Every dependency had to be established according to what it was actually used for.

Moving between GoDaddy accounts is one stage

In this case, the task was to change the account within GoDaddy: from a personal one to a company one. That is a different operation from moving a domain to an entirely different registrar.

GoDaddy says that when a domain is moved between its accounts, existing DNS settings remain, while related products such as a website or email do not automatically move with the domain. That is exactly why they must be identified separately. Instructions for transfers between GoDaddy accounts.

In my work, we checked both accounts before the transfer and retained a copy of the DNS settings. The agent then prepared the request for the specific company account. Accepting the domain on the company side also involved registrant details and declarations that required my decision. I performed sign-ins and additional identity confirmations in the appropriate panels.

After accepting the domain, checking did not end with a success message. We returned to its settings. The province in the contact details had to be corrected. Only a second read confirmed that correction had been saved.

This is an ordinary but useful example of working with an agent. It can work through a form, but the result still has to be checked: the right account, the right details, domain settings, and the operation of services. A correctly performed transfer does not mean every field in the form had the right value from the start.

Why could I still see the domain in the personal account?

At one point, I asked why I could still see a tile with the name of the domain being moved in personal GoDaddy. It looked as though the transfer had not been performed.

The agent compared both accounts. The company portfolio already contained the domain registration. The personal account retained a separate project in the website builder, marked as a site. It had a similar name, but it was not the domain itself.

That difference changes the decision. Deleting an unnecessary website project, removing a domain from a Google organisation, and changing the account that manages a domain in GoDaddy are three different actions. The name visible on a tile does not yet tell us what we are deleting.

A reader can use a very simple instruction:

Check what this item is: a domain registration, a DNS service, a website, hosting, or a domain assignment to email. Identify the account, product, and effect of deleting it. Show the findings first.

This is a useful example of learning while getting a task done: a similar name in two panels can refer to different things. Watching that check makes it easier to understand why it matters to distinguish a domain, a website, and an email service.

Copying messages does not switch email addresses

Email migration had its own course. First, we created a map: source mailbox → existing company mailbox. It covered two users; the person remaining in the old organisation was not added to it.

There was also a very practical moment when automation stopped at uploading the file with this map. A browser file-handling limitation required my participation. Preparing the file, loading it into the form, and starting the import were separate states. Until the map had been accepted, there was no basis for saying that migration had started.

After the import, the Google panel showed 69 detected and 69 imported messages for two accounts, with no skipped messages or transfer errors. This was a concrete result to check. Google also provides a user report and import report; it describes statuses, the number of transferred items, and problems. Email-import-report documentation.

Later, an incremental import was performed for messages that arrived after the first run. This stage must be included if the old system continues to receive email during the migration. The available import options are described in Google’s tool documentation.

At the same time, a different task remained: make new messages sent to the old addresses arrive at the appropriate company mailboxes. Simply copying history does not provide that. It required moving the domain assignment between Google organisations and configuring additional addresses, or aliases.

For this operation, the change needs an agreed time window. Google indicates that making a removed domain available for use in a new organisation may require waiting for up to 48 hours. That is a risk to continuity of address handling, not a promise of an interruption-free migration. Rules for removing and reusing a domain in Google Workspace.

In the last checked record, switching the old addresses to company mailboxes was still awaiting completion. I therefore do not present confirmed email import as evidence that all email was already working in the target arrangement.

Files, scripts, and old accounts have dependencies too

The work also covered Drive materials and keeping the needed data. At this stage, more than a file’s presence in a new folder must be checked. Can the right person open it? Do they have appropriate permissions? Does a script still refer to the old owner or old address? Does the application sign in through an account we intend to delete?

In our session, before account clean-up, there was also the question of one user’s unchecked contacts and calendar. That was a separate decision about the scope of data to preserve. Transferred email did not close that question.

This story is not instructions to repeat every operation in exactly the same order. It also shows a place that needed a more cautious plan: the two old accounts of the users being moved were deleted when switching the old addresses was not yet complete. The account of the person remaining in the old organisation was retained. In a similar task, I would make account clean-up dependent on a previously agreed email-continuity plan and confirmation of what would happen to the old addresses.

For automations, I would prepare a separate row in the plan: owner, account used, required permissions, related files, and test after the change. For a running application, I would include sign-in and database connections too. A copy of public website files does not replace a copy of its database or complete backend.

How to check the result without one over-broad “done”

The state of this work is best described separately for each part:

For your own migration, add a check date, responsible person, and evidence for every row. For the website, this means checking the right addresses and key functions. For email, send and receive messages at destination and retained addresses. For files, test access from the right account; for automations, perform a test run.

Also retain the state from before the change and describe how you will respond to a problem. Restoring DNS records alone will not automatically reverse a data transfer, account deletion, or a domain assignment in another system.

A prompt to use in your own work

The template below organises what emerged in successive stages of my work. It also asks for explanations while operating the panels. You can adapt it to your own one-off task.

I want to move a domain from a personal account to a company account
and organise the services connected with it.

This is a one-off task for me, and I do not know these panels well.
Use Computer Use so I can watch the successive actions.
Before each stage, briefly explain what you are doing and why.
Explain new terms alongside the setting they relate to.
Point out dependencies a beginner might not think to ask about.
If you do not know something, say so and establish how to check it.

First perform a review without changes. Confirm the source account,
the destination account, and the scope of my permissions. Establish separately:
domain registration, DNS, hosting, email, data, automations,
application sign-in, and extra products and billing.

Prepare a table: what we are moving, what remains, what is unknown,
what the dependencies are, and how we will check the result.
Do not treat a product as unnecessary just because it is small or old.

Propose the order of actions, needed copies, and a way to respond
to problems. Separate copying data from switching traffic
and from deleting old accounts or services.

Before changes, show the exact scope for approval.
When changing live email, identify the risk of interruption and its plan.
I will enter passwords and confirmation codes directly in the panels.

After every stage, read the state again. In the report, distinguish:
prepared, completed, confirmed, and work remaining.
Do not mark the whole task complete if even one
agreed dependency has not yet been checked.

What this way of working gives me

For a one-off task, what helps me most is combining execution with learning. With Computer Use, I work through the configuration faster, while watching the actions helps me understand what is happening in the panels. I also account for dependencies I might have missed as a beginner.

After this kind of work, I want to know what changed, why, and what still needs checking. In this case, the domain was already in the company account, while handling the old addresses remained an open task. That is part of learning too: being able to recognise which stage I have actually reached.