BugWP logo BugWP
Back to Community
Home / Community / Plugin → Jetpack

How to Recover Lost Jetpack Stats After a Site Migration or Staging Copy

24 threads Sep 9, 2025 Plugin → Jetpack

Content

One of the most common issues reported by Jetpack users is the sudden disappearance of historical statistics and subscriber data. This often occurs after routine site maintenance, such as migrating to a new server, cloning a site for staging, or even changing the site's URL structure. If you've found yourself in this frustrating situation, this guide explains why it happens and the most effective steps to get your valuable data back.

Why Do Jetpack Stats Go Missing?

Unlike content stored in your WordPress database, Jetpack statistics and subscriber data are stored on WordPress.com's servers. Your site is linked to this remote data by a unique, hidden identifier called a Blog ID or Site ID.

This system works flawlessly until a site's fundamental identity changes. Common triggers include:

  • Staging/Development Sites: Copying your live site's database to a staging environment (e.g., staging.yoursite.com) often copies the unique Blog ID. When both sites report the same ID, it can cause an "Identity Crisis," where data tracking gets rerouted to the most recently active site.
  • Site Migrations: Moving your site to a new host or server can sometimes disrupt the connection linked to the original Blog ID.
  • URL Changes: Switching from HTTP to HTTPS, adding/removing "www," or changing the site's path (e.g., from yoursite.com/old to yoursite.com) can make Jetpack treat the site as a new entity.
  • Manual Disconnection: Simply disconnecting and reconnecting the Jetpack plugin can, in some cases, generate a new Blog ID for the site, leaving the historical data attached to the old ID.

How to Restore Your Jetpack Stats and Subscribers

Based on numerous community reports, the following process is the most reliable way to resolve this issue.

Step 1: Disconnect and Reconnect Jetpack

Before taking further action, a simple reset of the connection can sometimes re-establish a lost link.

  1. In your WordPress dashboard, navigate to Jetpack > Dashboard.
  2. Scroll to the bottom of the page and click Disconnect or Disconnect from WordPress.com.
  3. After disconnecting, click the button to Connect to WordPress.com again and log in with your account.

Check if your historical stats have reappeared. If not, proceed to the next step.

Step 2: Seek Assistance to Merge Stats (The Most Common Solution)

If a simple reconnect doesn't work, the problem is almost certainly that your site's data is attached to a different Blog ID. This is not something you can fix from your dashboard; it requires a backend fix by the Jetpack team.

To get help, you will need to provide specific information. The Jetpack team will typically ask for:

  • Your current site URL: (e.g., https://yourwebsite.com)
  • Your WordPress.com username: The account used to connect Jetpack.
  • Previous site URLs: Any old addresses your site used, including staging site URLs (e.g., https://staging.yourwebsite.com).
  • A clear explanation: Briefly describe what changed (e.g., "I migrated my site," "I created a staging copy,").

With this information, a support agent can locate the historical data under the old Blog ID and merge it with your current site's ID. This process, as seen in the sample threads, is often resolved quickly once the correct details are provided.

Best Practices to Prevent Future Issues

To avoid this headache in the future, follow these guidelines when working on your site:

  • Use Jetpack's Staging Mode: When developing on a staging site, enable the Staging Mode setting. This tells Jetpack to treat the site as a development environment and prevents it from interfering with your live site's stats.
  • Avoid Copying the Database to Staging: If possible, use a fresh database for your staging site instead of copying the live one. This ensures a new Blog ID is created for the staging site.
  • Document Your Site's Details: Keep a record of your site's URL and any changes you make. This information is invaluable if you need to request a stats merge later.

Losing years of analytics data can be alarming, but as the many resolved threads show, the problem is almost always reversible. By understanding the cause and knowing how to request help, you can restore your site's complete history.

Related Support Threads Support