How to Move a Property in Google Analytics
Moving a Google Analytics property isn’t something you do every day, but when the need arises - like a company merger or an agency handoff - it’s important to get it right. This guide walks you through the exact process for moving your GA4 property to a different Google account, covering the essential pre-move checklist and post-move cleanup steps to ensure a smooth transition with no data loss.
Reasons to Move a Google Analytics Property
Transferring a GA property is typically done for organizational or ownership reasons. While every situation is unique, most moves fall into one of these common scenarios:
- Client Handoffs: A marketing agency initially sets up a client’s website tracking under its own master Google Analytics account. When the contract ends or as part of the agreement, the agency transfers property ownership directly to the client’s Google account.
- Company Acquisitions or Mergers: When one company acquires another, it’s common practice to consolidate all digital assets. This involves moving the acquired company’s web properties into the parent company’s primary GA account for unified reporting and administration.
- Internal Restructuring: A large organization might reshuffle departments or business units. A website that previously belonged to the 'Marketing' division’s GA account may need to be moved to a newly formed 'E-commerce' division’s account.
- Account Consolidation: You might have properties scattered across several Google accounts you’ve created over the years. Moving them all into a single, primary account simplifies management, streamlines user access, and gives you a single place to log in.
The Pre-Move Checklist: What to Prepare
Before you even click the "Move property" button, a little preparation goes a long way. Running through this checklist first will prevent frustrating permission issues and unexpected outcomes.
1. Confirm You Have the Right Permissions
This is the most common roadblock. To move a property, you must have specific access levels on both the source account (the one the property is in now) and the destination account (where it’s going).
- On the Source Account: You need both Administrator and Editor roles.
- On the Destination Account: You also need both Administrator and Editor roles.
If you have Administrator access to both, you’ll typically have the Editor role by default. If you’re missing any of these permissions, the process won’t work, and the destination account won’t even appear as an option during the move. You’ll need to ask an existing Administrator on the necessary account to elevate your access level.
Free PDF · the crash course
AI Agents for Marketing Crash Course
Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.
2. Understand What Moves (and What Doesn't)
It’s critical to know what comes along with the property and what gets left behind. Not everything is transferred automatically.
What gets moved automatically:
- All Your Reports and Data: All historical data collected to date will move with the property. You won’t lose any of your traffic history, event data, or conversion information.
- Core Property Settings: Your Measurement ID, data stream settings, data retention settings, and other core configurations are preserved.
- Audiences, Conversions, and Custom Dimensions: All the audiences, conversions, custom dimensions, and custom metrics you’ve set up will be transferred.
What DOES NOT get moved:
- Product Links: This is a big one. Any links to other Google products are broken and must be manually re-established after the move. This includes integrations with Google Ads, Google Search Console, BigQuery, Merchant Center, and Google Optimize.
- User Permissions: Property-level users are NOT moved. You will have to manually add team members and assign their roles again after the property is in its new home. The only user who is guaranteed access afterward is the person who performed the move.
3. Check the Destination Account Limits
A single Google Analytics account can hold a maximum of 2,000 properties. For most users, this is a non-issue. However, if you’re a large agency or enterprise consolidating many sites, it’s worth a quick check to ensure the destination account has room.
Once you’ve run through this checklist, you’re ready for the actual move.
How to Move a Google Analytics 4 Property: A Step-by-Step Guide
The process itself is straightforward and happens within the Google Analytics Admin panel. Follow these steps carefully.
Step 1: Navigate to the Admin Section
Log in to your Google Analytics account and click the Admin gear icon in the bottom-left corner of your screen.
Step 2: Select the Account and Property to Move
In the Admin panel, you'll see two primary columns: "Account" and "Property." Make sure the correct source account is selected in the first column, and then select the specific property you intend to move from the second column.
Step 3: Access “Property Details”
In the "Property" column, find and click on Property Details. This is where the "Move property" function is now located in GA4.
Step 4: Initiate the Move
On the "Property details" page, you will see a blue Move property button in the top-right corner. Click on it to begin the transfer process.
Step 5: Select the Destination Account
A new screen named "Move Property" will appear. Use the dropdown menu under "Move to this account" to select the destination account. Remember, only accounts where you have the required Administrator and Editor permissions will show up in this list. If the account you’re looking for is missing, it’s almost certainly a permissions issue.
Step 6: Choose How to Handle Permissions
Below the destination account, you’ll see a section for handling permissions. You have two options:
- Replace existing property permissions with permissions from the destination account: This is a clean slate option. Only users who have access at the destination account level will have access to the property after the move. Any user who only had property-level access will lose it.
- Keep existing property and destination account permissions: This option merges the two sets of users. Existing property-level users will keep their access, and users from the destination account will inherit their permissions. This can sometimes lead to cluttered user lists.
For handoffs and clean consolidations, the "Replace" option is generally recommended.
Step 7: Confirm and Start the Move
Read through the confirmation boxes that summarize the consequences of the move (e.g., losing product links). You must check the box to acknowledge this. Once you’ve made your selections, click the bold Start move button.
The transfer process begins immediately and usually takes only a few minutes. You’ll receive a confirmation notice once it’s complete, and the property will no longer appear in the old source account.
After the Move: Your To-Do List
Moving the property is only half the battle. Now you need to perform some simple cleanup to ensure everything works correctly in its new home.
1. Re-Link Your Google Products
This is your top priority. Your newly moved property is now an island cut off from your other Google tools. You need to rebuild those bridges.
In the "Property" column of your Admin panel, go to the Product Links section. From there, systematically re-link your essential services:
- Google Ads
- Google Search Console
- BigQuery
- Merchant Center
- Firebase
You’ll need to have administrative access on those respective platforms to complete the linking process. For example, to link Google Ads, you must be an admin on the specific Google Ads account you want to connect.
Free PDF · the crash course
AI Agents for Marketing Crash Course
Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.
2. Reinstate User Access
Your team members probably can’t see the property anymore. Navigate to Property Access Management in the Admin panel and begin adding back your team members. Assign them the appropriate roles (Administrator, Editor, Marketer, Analyst, Viewer) so they can get back to their work.
3. Triple-Check That Tracking is Working
Your data collection should not be interrupted by the move, as the Measurement ID doesn’t change. However, it’s always good to verify.
Head to the Realtime report in standard GA reporting. If you see active users, you know your tracking code is still firing correctly and sending data to the (now moved) property. Take a look at your main traffic reports as well to confirm that all historical data is present and accounted for.
Final Thoughts
Moving a Google Analytics property is a direct process that centers around having the correct permissions, following a few steps in the admin dashboard, and remembering to re-link your products and users afterward. By following the checklists above, you can confidently migrate any GA4 property without data loss or prolonged downtime.
Once your property is correctly situated and your data is consolidated, the task of analysis becomes much clearer. We built Graphed to streamline this next step. Instead of manually building reports or getting lost in different interfaces, you can connect all your data sources - including Google Analytics, Google Ads, and Shopify - and start building dashboards just by asking questions. Commands like "Show me a dashboard comparing my organic sessions from last quarter" let you get directly to the insight, all with real-time, live-updating data.
Related Articles
How to Create Facebook Ads API for Claude Code
Create a Meta Marketing API access token that never expires, using a system user, so Claude Code can pull Facebook ad reports and manage campaigns.
ClickHouse vs Postgres: When to Switch to Columnar
Comparing ClickHouse vs PostgreSQL means matching storage architecture to workload. Row storage wins for transactions. Columnar wins for scan-heavy analytics.
Google Ads for Orthodontists: Get More Booked Consults
Most orthodontic Google Ads campaigns waste money on low-intent searches. The problem is structure, not the platform.