Blog
No items found.
5
minutes

How to migrate your PostHog self-hosted to PostHog Cloud

PostHog is an open-source product analytics tool that we use at Qovery to improve the developer experience. PostHog is similar to famous proprietary product analytics tools like Mixpanel, Heap, Amplitude.
Romaric Philogène
CEO & Co-founder
Summary
Twitter icon
linkedin icon

At Qovery, we were using PostHog self-hosted for 8 months in production. It was running nicely on Qovery (yes, we deployed PostHog with Qovery 😎 #eatYourOwnDogFood), but we decided to move to the PostHog Cloud. Here are the two main reasons why we decided to make this move:

If you are not yet using it, give it a try with Qovery or PostHog Cloud version.
  1. To support the PostHog project: Because we love their product, keeping them by using their Cloud version makes complete sense to us.
  2. Stay focused on our business: Using the self-hosted version of PostHog requires you to spend time to maintain it. Meaning, you have to handle the upgrade yourself and make sure the service is up and running all day long.

How to migrate

Looking at their documentation, there is no guide to migrate from PostHog self-hosted to their Cloud version. I asked them the procedure on Slack, and Paolo from the PostHog team responded that it should not be too complicated to transfer the data by fetching the data from the PostHog source and pushing them to the PostHog destination via the web API.

Conversation with Paolo from Posthog on Slack

So the idea was to make a Python script to fetch the data from our self-hosted PostHog instance and forward the data to the PostHog Cloud version.

(Self-hosted PostHog) <--[fetch event data via web API]-- Python Script --[send event data via web API]--> (PostHog Cloud)

Before migrating

As I know that we have more than one million events to send, I notified the PostHog support team that we will migrate our self-hosted version. Just in case they have to adjust their infrastructure. Who knows :) Paolo (once again, he is everywhere 🙂) responded to me and was super proactive.

null
null

I encourage you always to keep informed the support team of service when you are about to migrate. They can help you. It was the case here with the PostHog support team.

We can migrate now

To migrate, I made a simple Python script using no external dependencies. Only HTTP requests, and that's it. Note: This script is compatible with Python 3.6+.

#!/usr/bin/env python
import copy
import time
import uuid
from urllib.parse import urlparse

import requests

# Your source PostHog instance
source_posthog_scheme_and_host = 'https://posthog.your-domain.tld'

# Generate a personal API key to read the data from your source PostHog instance
source_api_key = 'xxx'

# Your project API key provided by PostHog in your project settings
dest_project_api_key = 'xxx'


def is_valid(key: str, data: dict) -> bool:
"""
Helper function to check if the value is empty or none
:param key: data key to check
:param value: dict
:return: true if valid (not empty, None), false otherwise
"""
if key not in data or not data[key] or str(data[key]).strip().lower() == 'none':
return False

return True


def clean_source_data(results: [dict]) -> [dict]:
"""
Clean up data from PostHog source
Note: this function do not mutate `results`
:param results:
:return:
"""
_results = []
if not results:
return _results

distinct_id = 'distinct_id'

for result in results:
data = copy.deepcopy(result)
del data['id']

if not is_valid(distinct_id, data):
data[distinct_id] = str(uuid.uuid4())

if 'properties' in data:
properties = data['properties']
if not is_valid(distinct_id, properties):
# copy distinct_id value from the parent object
properties[distinct_id] = data[distinct_id]

_results.append(data)

return _results


def capture(data: [dict], count: int = 0):
"""
Function to send data to the dest PostHog instance
:param data:
:param count:
:return:
"""
res = requests.post('https://app.posthog.com/capture', json={'api_key': dest_project_api_key, 'batch': data},
headers={'Content-type': 'application/json'})

if res.status_code != 200:
if count >= 100:
print('retry exceeded')
exit(1)
time.sleep(3)
print('Retry sending data (status code: {}) to dest PostHog with data {}'.format(res.status_code, data))
return capture(data, count + 1)

return res


def get_source_data() -> dict:
headers = {'Authorization': 'Bearer {}'.format(source_api_key)}

url = '{}/api/event'.format(source_posthog_scheme_and_host)

with open('posthog_completed_urls', 'a') as f:
while 1:
query = urlparse(url).query
if query:
# PostHog return weird next URL with tons of 'before' params
url = '{}/api/event?before={}'.format(source_posthog_scheme_and_host, query.split('=')[-1])

res = requests.get(url, headers=headers)
if res.status_code == 200:
j_res = res.json()
_data = clean_source_data(j_res['results'])

yield _data

f.write(url + '\n')
url = j_res['next']
else:
print('Retry fetching events (status code: {}) from PostHog source with URL {}'.format(res.status_code, url))
time.sleep(3)


if __name__ == '__main__':
for data in get_source_data():
capture(data)
print('{} lines migrated'.format(len(data)))

print('ok')
Before running the migration script, I strongly recommend making your apps send the data to the PostHog Cloud instance before and waiting for the old instance to stop receiving new events.

Now it is time to:

  1. Copy this script.
  2. Change the value of the variables source_posthog_scheme_and_host, source_api_key, dest_project_api_key
  3. Run the script and wait until it is done 👌

Wrapping up

The migration went smoothly and took one day because we had more than 1 million events. We are super excited to use PostHog Cloud. It is fast and efficient for improving the developer experience on Qovery. Any questions about our usage of PostHog? Join our Discord to chat about it.

Resources:

  • PostHog: open-source product analytics tool.
  • Qovery: the simplest way to deploy your apps on AWS.
Share on :
Twitter icon
linkedin icon
Ready to rethink the way you do DevOps?
Qovery is a DevOps automation platform that enables organizations to deliver faster and focus on creating great products.
Book a demo

Suggested articles

DevOps
 minutes
The Top 10 Porter Alternatives: Finding a More Flexible DevOps Platform

Looking for a Porter alternative? Discover why Qovery stands out as the #1 choice. Compare features, pros, and cons of the top 10 platforms to simplify your deployment strategy and empower your team.

Mélanie Dallé
Senior Marketing Manager
AWS
Deployment
 minutes
AWS App Runner Alternatives: Top 10 Choices for Effortless Container Deployment

AWS App Runner limits control and locks you into AWS. See the top 10 alternatives, including Qovery, to gain crucial customization, cost efficiency, and multi-cloud flexibility for containerized application deployment.

Mélanie Dallé
Senior Marketing Manager
Kubernetes
 minutes
Kubernetes Management: Best Practices & Tools for Managing Clusters and Optimizing Costs

Master Kubernetes management and cut costs with essential best practices and tools. Learn about security, reliability, autoscaling, GitOps, and FinOps to simplify cluster operations and optimize cloud spending.

Mélanie Dallé
Senior Marketing Manager
AWS
GCP
Azure
Cloud
Business
10
 minutes
10 Best AWS Elastic Beanstalk Alternatives

AWS Elastic Beanstalk is often rigid and slow. This guide details the top 10 Elastic Beanstalk alternatives—including Heroku, Azure App Service, and Qovery—comparing the pros, cons, and ideal use cases for achieving superior flexibility, faster deployments, and better cost control.

Morgan Perry
Co-founder
Kubernetes
DevOps
7
 minutes
Kubernetes Cloud Migration Strategy: Master the Shift, Skip the Disaster

Master your Kubernetes migration strategy with this expert guide. Learn the critical planning phases, mitigate major risks (data, security, dependencies), and see how Qovery simplifies automation and compliance for a fast, successful, and reliable transition.

Morgan Perry
Co-founder
SecurityAndCompliance
DevSecOps
 minutes
Qovery Achieves SOC 2 Type II Compliance

Qovery is officially SOC 2 Type II compliant with an Unqualified Opinion. Get the highest assurance of continuously verified security controls for enterprise-grade application deployments and simplify due diligence.

Pierre Mavro
CTO & Co-founder
Product
Observability
 minutes
Troubleshoot Faster with the New Log Search and Filtering in Qovery Observe

Following the launch of Qovery Observe, we’re progressively adding new capabilities to help you better monitor, debug, and understand your applications. Today, we’re excited to announce a major improvement to the Logs experience: you can now search and filter directly within your application logs.

Alessandro Carrano
Lead Product Manager
Platform Engineering
DevOps
Terraform
7
 minutes
Top 5 Crossplane Alternatives & Competitors

Go beyond Crossplane. Discover Qovery, the #1 DevOps automation tool, and 4 other IaC alternatives (Terraform, Pulumi) for simplified multi-cloud infrastructure management and deployment.

Morgan Perry
Co-founder

It’s time to rethink
the way you do DevOps

Say goodbye to DevOps overhead. Qovery makes infrastructure effortless, giving you full control without the trouble.