Repository: PostHog/posthog.com
Pull request #11195: Add guidance for making the switch to PostHog
Author: login: daniloc
Created: 2025-04-04T16:13:28Z | Merged: 2025-04-15T14:45:36Z

## Changes

**Premise:** The switch to PostHog starts with one person. They get us. They get the power we're offering: a vast suite of products sharing the same data. Powerful tools that are also easy to use. They know we are better than the collection of junk they suffer through at work each day. This change agent can use our help: how to make the case, how to engage their teammates, how to set expectations for migration.

Thus, a supplement to Winning with PostHog based on multiple interviews with the sales crew. This switching guide aims to help both self-serve and sales-supported customers lay the right foundation for a long-term, fruitful integration.

- Social proof and talking points optimized for companies <100 people, to help persuade executives, product teams and engineers
- Pilot planning to give self-servers the same kind of structure that sales would recommend, with optional onboarding to a sales relationship for those who want it and qualify
- Prevent the seeds of churn with operational guidance to supplement our technical migration guides
- Throughout, support our change agent in getting more teammates to log in and use the product

<img width="353" alt="Screenshot 2025-04-04 at 12 01 21 PM" src="https://github.com/user-attachments/assets/e7295bcd-5539-4d0e-9165-53e424e0cc2d" />

Creating this PR at the 95% mark, feel free to request any screenshots or other missing niceties you think would help.

## Checklist

- [x] Words are spelled using American English
- [x] Titles are in [sentence case](https://apastyle.apa.org/style-grammar-guidelines/capitalization/sentence-case)
- [x] Feature names are in **[sentence case too]([https://apastyle.apa.org/style-grammar-guidelines/capitalization/title-case](https://apastyle.apa.org/style-grammar-guidelines/capitalization/sentence-case))**
- [x] Use relative URLs for internal links


Diff:
diff --git a/contents/docs/new-to-posthog/switch-guide/migration-planning.mdx b/contents/docs/new-to-posthog/switch-guide/migration-planning.mdx
new file mode 100644
index 000000000000..bb849843292c
--- /dev/null
+++ b/contents/docs/new-to-posthog/switch-guide/migration-planning.mdx
@@ -0,0 +1,94 @@
+---
+title: What to expect as you migrate
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+With your team onboarded and a successful pilot completed, you can turn your attention to **planning your migration**.
+
+## Technical planning
+
+PostHog provides tools and guides to support you making this switch. Check out our [migration docs](/docs/migrate) for details on moving from [Amplitude](/docs/migrate/migrate-from-amplitude), [Mixpanel](/docs/migrate/mixpanel), [LaunchDarkly](/docs/migrate/launchdarkly) and others.
+
+Stumped on any detail of the process? If you’ve already signed up and started sending events with a forecasted bill of $500 or more, our **onboarding** team will reach out to help. 
+
+If you haven’t heard from us yet, [drop us a line](/talk-to-a-human) with your migration questions!
+
+Some setup tips:
+
+1. Don’t create separate projects for mobile and web. PostHog works best when you can see user behavior across all versions of your products in one set of data and views.
+
+2. Healthy integrations have a few things in common. It can help to review the [health check](/handbook/growth/sales/health-checks) documentation used by our sales team to tackle the most common ways to keep your bill manageable and predictable.
+
+
+<CalloutBox icon="IconDatabase" title="Get help with large migrations" type="task">
+
+If your historical data is above 100 GB or 200 million events, you should [reach out to our sales team](/talk-to-a-human) or [open a support ticket](/docs/support-options) so we can make sure everything imports smoothly.
+
+</CalloutBox>
+
+### Reducing disruption for your teammates
+
+New software can take a moment to click. One way to help your teammates get comfortable is making sure vital numbers are already waiting in your new PostHog setup.
+
+To support this, it can help to make a spreadsheet for people to request their most essential metrics. Use it to create insights in PostHog, then link them in the spreadsheet.
+
+You want to know what data your teammates need to keep making good decisions, and ensure those metrics are easy to find in PostHog. Capturing these requirements can also help you check that your technical implementation is capturing all necessary events and properties.
+
+While moving historical events over is straightforward, you’ll need plan for some time rebuilding the views and dashboards your team relies on.
+
+### Conversion tracking
+
+An urgent need from marketing and product teams is **tracking conversions**. Getting clear on how to do this in PostHog can reduce frustration as everyone settles in. These docs on using **[funnels](/docs/product-analytics/funnels)** are a great starting point for this kind of reporting.
+
+***
+
+## Providing demos
+
+A great way to help PostHog land well is to offer a quick demo to everyone who’s interested.
+
+Here are some topics that might be worth covering. You know your teammates best, so be sure to adjust your demos to their needs and interests.
+
+### Events, persons, properties, and the activity view
+
+![The activity explorer](https://res.cloudinary.com/dmukukwp6/image/upload/activity_2923c81b32.png)
+
+Events are the core of PostHog’s reporting. Explain how they work, and the properties you plan to attach to them as part of your integration. Show off the **[activity](https://app.posthog.com/project/activity/explore)** view so everyone can see new events pouring in. 
+
+If you’re identifying users in your integration, showing how **[person profiles](https://app.posthog.com/project/persons)** collect information can also be helpful.
+
+### Web analytics
+
+Everyone who wants the basics of an analytics dashboard will find it in our **[web analytics](https://app.posthog.com/project/web)** tab right out of the box.
+
+### Actions
+
+Actions let you group and rename events, making them easier to use in reporting. The more your teammates understand actions, the easier everyone’s life gets to be, so take a moment in **[data management](https://app.posthog.com/project/data-management/actions)** to explain.
+
+### Creating insights and dashboards
+
+Creating, editing, and duplicating [insights](/docs/product-analytics/insights) is fast and easy, and so is adding these to dashboards. Make sure to give this part of the demo plenty of detail: playing with data is a big part of what makes PostHog fun. This is also a great time to explore **filters**, which are a common need.
+
+Popular insights include:
+
+- Trends: show change over time  
+- Funnels: track conversions and other sequential activity  
+- User paths: see how real people explore your sight
+
+### Replays
+
+[Replays](https://app.posthog.com/project/replay/home) are a hit across roles and teams. For engineers, they can be a way of catching layout problems and other bugs early. For product and design, they’re a way to make sure that new features and workflows are actually performing correctly. They’re a huge help to support, and even execs enjoy flipping through them.
+
+### Instant, no-code surveys
+
+If you’re talking to someone who really wants to hear from customers, [surveys](https://app.posthog.com/project/surveys) are going to be exciting. Walk through how to design and deploy one.
+
+### Toolbar
+
+This one is a visual crowd pleaser: launch your site’s PostHog [toolbar](https://app.posthog.com/project/toolbar) to show heatmap overlays and other stats directly on your site. You can even use it to launch [hedgehog mode](/blog/aruba-hackathon#hedgehog-mode--toolbar--awesomeness).
+
+<CalloutBox title="Get more help" type="fyi">
+
+We never want to waste your time with a call, so a self-serve migration is an open invitation. But if any part of this feels more daunting than fun, just [get in touch](/talk-to-a-human). We’re able to help accounts with $500 in projected monthly spending with onboarding, along with ongoing support for companies 25 people and up.
+
+</CalloutBox>
diff --git a/contents/docs/new-to-posthog/switch-guide/planning-your-pilot.mdx b/contents/docs/new-to-posthog/switch-guide/planning-your-pilot.mdx
new file mode 100644
index 000000000000..96ca37abead0
--- /dev/null
+++ b/contents/docs/new-to-posthog/switch-guide/planning-your-pilot.mdx
@@ -0,0 +1,84 @@
+---
+title: Planning your pilot
+nextPage: ./migration-planning.mdx
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+We want you to love using PostHog. 
+
+We’ve worked hard to craft a tool that can make you much more effective at giving your customers what they want.
+
+Here's how to get the most out of a pilot test with your team.
+
+## Ask for help if you want it
+
+For companies sized 25 and up, [we’ve got a team](/talk-to-a-human) who can answer questions and help you make a plan.
+
+But only if you want the help! They’re not going to pressure you or do anything corny, but their integration experience can save time and trouble. They can also help you map PostHog features to your business goals, developing a useful mental model for using all our products.
+
+But we’re not going to get in your way, either, because...
+
+## We want you to play around
+
+The most important job is getting familiar with PostHog in whatever way makes you most comfortable. 
+
+The most [basic integration takes 5 minutes](/docs/getting-started/install?tab=snippet) and we’ve got loads of documentation to support you exploring on your own.
+
+## First two weeks: get data in, then look at it
+
+Job one is making sure PostHog is reliably ingesting your data and reporting the basics in a dashboard. Once this is working, take a break, order a pizza[^1].
+
+### Invite everyone who cares about user behavior
+
+It doesn't matter what their role is. We charge by how successful your product is, not how many people have a login. We're building a product everyone will find useful.
+
+So it's all upside when you invite everyone who cares about user behavior. As your integration comes online, think about who else should have access. You'll have the option to invite them during setup, and any time after that.
+
+### Key metrics and event tracking
+
+With the basics in place, you have a few decisions to make to build a strong foundation for your reporting and data collection.
+
+- **Decide**: Your [North Star metric](/docs/new-to-posthog/getting-hogpilled)  
+- **Decide**: Make an event tracking plan, or rely on autocapture?  
+- **Decide**: Use [identified or anonymous events](/docs/data/anonymous-vs-identified-events)
+
+### Enhance your integration
+
+From here, you can get more sophisticated:
+
+- Configure a [reverse proxy](/docs/advanced/proxy) to improve reliability of event capture  
+- Experiment with measuring [activation](/docs/new-to-posthog/activation) and [retention](/docs/new-to-posthog/retention)  
+- [Watch some session replays](https://app.posthog.com/project/replay/home), see what you can learn  
+- Try out a [no-code survey](/docs/surveys/creating-surveys) to learn what customers are feeling about your product
+- Fire up [web analytics](/docs/web-analytics/getting-started), see if you like it better than your existing provider
+
+### Check in with your teammates
+
+After two weeks to explore, check in with your teammates. See if there’s anything they want but aren't getting. If you can get them excited with you, you'll have a better chance of making this pilot turn into a full-on switch.
+
+## Assess costs
+
+After a couple weeks, you should have a decent picture of how much activity PostHog is tracking, and you can use that to understand your costs.
+
+From here there’s no sneaky stuff. All our [pricing is posted publicly](/pricing), and you can see your projected costs in [your billing settings](https://us.posthog.com/organization/billing). 
+
+Want to lower your bill? Check out our guides on cutting costs for [product analytics](/docs/product-analytics/cutting-costs), [session replay](/docs/session-replay/cutting-costs), and [feature flags](/docs/feature-flags/cutting-costs).
+
+<CalloutBox icon="IconRocket" title="We guarantee your safe pilot" type="fyi">
+
+You don't need to worry about a surprise billing spike as you're getting started. If something unexpected happens, just [get in touch](/talk-to-a-human). We’ll work it out with you. We need your trust and enthusiasm way more than we need a month of charges you weren't expecting.
+
+We’re in this for the long-haul. If you want more time to evaluate, and our generous free tier isn’t going to cover your volume of usage, just tell us about it. We can offer you a longer no-cost trial so you can be completely confident in switching over.
+
+It means a lot to us that you want to make this switch. We've got your back.
+
+</CalloutBox>
+
+## Migration planning
+
+Once you’re clear on the path forward, we’ve got you covered on historical data as well.
+
+Let's talk about everything you need to [plan a migration](/docs/new-to-posthog/switch-guide/migration-planning).
+
+[^1]: Pineapple or not is up to you.
\ No newline at end of file
diff --git a/contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx b/contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
new file mode 100644
index 000000000000..304f09c5d4ab
--- /dev/null
+++ b/contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
@@ -0,0 +1,138 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+PostHog is an easy sell for new projects and companies: one login and one simple integration gets you everything you need to build great products.
+
+But if you're already leaning on another tool, switching can require some planning and diplomacy. A little finesse. 
+
+Our switching guide exists to support your journey. Start here and learn to pitch PostHog to your teammates. With your team on board, we'll walk through [how to plan your pilot deployment](/docs/new-to-posthog/switch-guide/planning-your-pilot), and then how to [nail your migration](/docs/new-to-posthog/switch-guide/migration-planning).
+
+***
+
+## Why everyone will love PostHog
+
+PostHog is one login and one bill.
+
+This means less headache for more power, with all your data available across a range of products that help you understand user behavior as it happens.
+
+You'll get a responsive team that cares about user needs, delivering on customer feedback constantly.
+
+PostHog is completely agnostic to the language, framework, and stack you build your product with. You can adopt it incrementally, adding new functionality as needed.
+
+Best of all, PostHog is built so that you’ll actually enjoy using it. We really want you to have a good time.
+
+***
+
+## Why product teams love PostHog
+
+PostHog gives product teams the power to understand users, improve adoption, and test assumptions. Once PostHog is in place, your product teammates can dive in immediately, with loads of power that doesn't require further engineering intervention.
+
+**Visualize anything** with [charts and trend reporting](docs/product-analytics/insights), and [dashboards](/docs/product-analytics/dashboards) that are easy to build, but also deeply customizable for SQL enthusiasts.
+
+**Learn anything you want** about everything the user touches in the product without manual instrumentation with [autocapture](/docs/product-analytics/autocapture).
+
+**Get clarity about navigation** and user priorities with [heatmaps](/docs/toolbar/heatmaps).
+
+**Use session replay to reveal bugs**, expose friction, and help instantly answer questions like “is this new design working?” We support both [web and mobile SDKS](/docs/session-replay/installation).
+
+**Integrate revenue data** from [Stripe](/docs/cdp/sources/stripe) and other sources using data warehouse, so you can get a clear picture of what changes really move the needle.
+
+**Send events and other details to any other tool**, powering automations and keeping data in sync, with setup you can accomplish in seconds, fully customizable for any API or webhook. [Data pipelines](/docs/cdp) makes it easy.
+
+**Gather feedback and book user interviews** from exactly the users you want to reach with no-code [surveys](/docs/surveys/creating-surveys) that deploy instantly.
+
+**Get unblocked by PostHog’s helpful sales and support teams**, ensuring you get the insights and information you need quickly.
+
+***
+
+## Why engineers love PostHog
+
+PostHog is designed for developers.
+
+The project is [developed in the open](https://github.com/PostHog/posthog), with a [public roadmap](/roadmap) and [dozens of pull requests landing](https://github.com/PostHog/posthog/pulls?q=is%3Apr+is%3Aclosed) each week. While other products are low-velocity black boxes, we’re constantly making PostHog better.
+
+ We’ve got a dedicated technical staff standing by to help keep you on track. If you ever do need support, you’ll be talking to someone who knows the technical details of the product really well.
+
+Giving other teams the data they want becomes much easier with PostHog in the mix, lowering the burden on engineering. Once a basic integration is in place, there are loads of features everyone can use without a developer's intervention.
+
+**Consolidate the tools your company needs**, with one login, one integration, one bill.
+
+**Comprehensive documentation** developers love for every every stack, framework, and language. You can also view [our source code directly](http://github.com/postHog/) if you can't find what you need. 
+
+**Get a data platform that encourages tinkering**: if something doesn’t fit quite right for your team, it’s easy to customize everything. We'll host all these customizations for you. You don't need to worry about infrastructure or uptime.
+
+**Integrating PostHog with other tools or even your own services is easy**, thanks to [data pipelines](/docs/cdp).
+
+**Roll features out gradually** using [feature flags](/docs/feature-flags/creating-feature-flags) that are easy to target with fine-grained queries across everything PostHog knows about your users.
+
+We also care about the technical details of switching over. 
+
+No matter your stack or existing tools, **complete integration and [migration docs](/docs/migration)** mean a clear path instead of a puzzle to solve. Our experienced Sales and CS team can even provide backup for more complex cases.
+
+***
+
+## Why executives love PostHog
+
+We’re in this for a long-term relationship, so **PostHog wants you to spend as little money as possible**. 
+
+Our sales team actually works with customers to reduce bills and optimize consumption. Instead of sneaky billing, we’d prefer to make more money as a result of you winning more business.
+
+There’s just no sneaky stuff going on here. You can get started immediately with no shenanigans, no calls with the sales team if you don't want them.
+
+**Your team will like PostHog**. It’s fresh, always getting fixes, improvements, and additional power. An investment in PostHog today means even more capabilities by next year.
+
+**There's no per-seat charge**, so PostHog makes it easy for everyone on your team to make data-driven decisions. No matter how quickly you scale your team, your costs remain fixed to the actual usage of your product. 
+
+**PostHog’s sales process is transparent and so is the whole company**: the company [handbook is public](/handbook), *even documenting the ways we can offer [discounts](/handbook/growth/sales/billing#coupons-and-discounts)*. Everything you want to know about pricing, processes, and our product is publicly documented.
+
+**You can have a free trial** to fully vet the costs and impact of your integration. Trying PostHog is low-risk, no cost, and fully reversible.
+
+**PostHog doesn’t require a contract**. You can save money with one, but it’s not a blocker to trying things out.
+
+***
+
+## Sharing social proof
+
+We’ve published [customer stories](/customers) with loads of companies who have loved their switch to PostHog. Here are some choice quotes.
+
+[ElevenLabs](/customers/elevenlabs):
+
+<Quote
+    imageSource="/images/customers/elevenlabs-sam.jpg"
+    size="sm"
+    name="Sam Sklar"
+    title="Growth engineer, ElevenLabs"
+    quote={`“We use basically everything in PostHog to understand more about our users and to plan new launches. We have an onboarding survey which is the first thing you see when you sign up.”`}
+/>
+
+***
+
+[Octomind](/customers/octomind):
+
+<Quote
+    imageSource="/images/customers/maria_octomind.jpg"
+    size="sm"
+    name="Maria Zahorcova"
+    title="Chief Marketing Officer, Octomind"
+    quote={`“We’re product-led and it’s really, really important that we keep an eye not only on marketing activities but also the experience beyond that. It was great when I found out I could use PostHog to track data across the site, the docs, and the product — I just had to speak to our engineers about implementing it.”`}
+/>
+
+***
+
+[ResearchGate](/customers/researchgate):
+
+<Quote
+    imageSource="/images/customers/paul_mccloud.jpg"
+    size="sm"
+    name="Paul McCloud"
+    title="Head of Product Engineering, ResearchGate"
+    quote={`“Something I didn't get at the start was the clip at which PostHog adds new products. What you don't really understand until you've experienced it is that, because all these tools are built on the same fundamental architecture, the value of PostHog becomes exponential as new tools get connected!”`}
+/>
+
+***
+
+You can use these points to start the conversation. No matter who you're talking to, remember: it's easy to try this out with no risk, fees, or commitment.
+
+Check out our [pilot planning guide](/docs/new-to-posthog/switch-guide/pilot-planning) for some ideas on how to quickly get your team to experience PostHog.
\ No newline at end of file
diff --git a/src/navs/index.js b/src/navs/index.js
index ce51d0040b68..904b776f83b7 100644
--- a/src/navs/index.js
+++ b/src/navs/index.js
@@ -2125,6 +2125,25 @@ export const docsMenu = {
                     url: '/docs/new-to-posthog/revenue',
                     icon: 'IconHandMoney',
                 },
+                {
+                    name: 'Switching to PostHog',
+                    icon: 'IconLeave',
+                    url: '/docs/new-to-posthog/switch-guide/switching-to-posthog',
+                    children: [
+                        {
+                            name: 'Convincing teammates',
+                            url: '/docs/new-to-posthog/switch-guide/switching-to-posthog',
+                        },
+                        {
+                            name: 'Planning your pilot',
+                            url: '/docs/new-to-posthog/switch-guide/planning-your-pilot',
+                        },
+                        {
+                            name: 'What to expect when migrating',
+                            url: '/docs/new-to-posthog/switch-guide/migration-planning',
+                        },
+                    ],
+                },
                 {
                     name: 'PostHog explained',
                 },


Reviews:
user: login: daniloc
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-04T16:28:54Z
user: login: ivanagas
body: A bunch of comments on the first page for now, I can dive into the others after you've had a look. 
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-09T17:58:46Z
user: login: daniloc
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-09T18:02:01Z
user: login: daniloc
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-09T18:07:50Z
user: login: daniloc
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-09T18:08:45Z
user: login: daniloc
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-09T18:10:44Z
user: login: daniloc
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-09T18:18:23Z
user: login: daniloc
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-09T18:20:28Z
user: login: daniloc
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-09T18:22:03Z
user: login: daniloc
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-09T18:30:27Z
user: login: daniloc
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-09T18:35:35Z
user: login: ivanagas
body: I think this turned out great and I see all the research and background that went into it!
state: APPROVED
author_association: CONTRIBUTOR
submitted_at: 2025-04-09T20:41:51Z
user: login: daniloc
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-09T20:51:04Z
user: login: daniloc
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-09T20:53:34Z
user: login: daniloc
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-09T20:57:19Z
user: login: daniloc
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-09T20:58:35Z
user: login: daniloc
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-09T21:00:12Z
user: login: daniloc
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-09T21:07:40Z
user: login: daniloc
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-09T21:08:25Z
user: login: daniloc
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-09T21:10:27Z
user: login: daniloc
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-09T21:19:43Z
user: login: andyvan-ph
body: Having read this a couple of times through, this is making me a feel a bit uneasy tbh. Here's a bit more context:

- Now I've read it irl, we definitely shouldn't put this in the docs, or at least not this prominently. Tonally, it just feels a bit weird to have quotes from customers here, for example. Unlike the Winning with PostHog stuff, which is explicitly about doing stuff in PostHog, this reads way more like sales collateral / marketing material. I appreciate this is very much a temporary / placeholder situation, but I think it's worth us figuring out the long term solution now, rather than shipping as is.

- More of an addendum to the above: would a developer expect clicking 'Switching to PostHog' to take them to a page about convincing their teammates? TL;DR: I suspect our goals with this content and the reader's expectations won't align.

- At times, I worry this guide makes switching to PostHog sound hard. My mind was just in a "shit, this feels like a lot of work tbh. i might not bother, thanks." Again, this is less of a problem when someone has already decided to switch to PostHog, but lots of people who are still only considering it will end up reading this, and I think they could be put off by the scope of all this.

- In places, we're asking people to disappear and read some other doc, rather than giving people the basic context in the guide so they can keep making progress. I think I felt this most keenly in this bit of planning your pilot. It also plays into the "phew, this feels like a lot of work" vibe.

<img width="657" alt="Screenshot 2025-04-10 at 17 24 47" src="https://github.com/user-attachments/assets/6fe0a654-0a53-47a6-a3c5-242cf84f2b39" />

Finally, some questions to ponder:

- What might this look like as its own section of the website? Could we, for example, create a separate migration docs that includes this content + existing migration guides, and product specific tutorials.

- If we didn't have this in the docs, how / when do we want people to discover it? Where should we have links to this guide on the website? Should we add to email people get after they signup based on specific criteria?
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-10T16:34:33Z
user: login: andyvan-ph
body: Have gone through and done a deeper read and made some suggestions. 

For the record, my reservations aren't about "is this worth having?" and more in the "where this should go?" and "does this work?" territory. 

I get that migrating is intrinsically harder, but I don't think we're totally nailing making it feel easier just yet.

In the interests of shipping a V1, I think we should do the following:

1. Park my ideas around creating a more opinionated timeline (see inline comment on Planning your pilot) for now. If that resonates with you guys too, we can return to that in a future revision.

2. Move this to a different part of the sidebar, either: 

- The bottom of the Integration section – I get this is actually more prominent, but in my head it makes more sense there than in 'Winning with PostHog', which is more about what you do after you've already integrated/migrated to PostHog.

- Slot it into the PostHog explained section, probably after 'What is Product OS?'. This is the less punchy option, obviously

I don't feel strongly about which of the above we choose, but I do feel strongly 'Winning with PostHog' is the wrong place for it.
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-11T12:23:58Z
user: login: daniloc
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-14T14:49:09Z
user: login: daniloc
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-14T16:29:07Z
user: login: daniloc
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-14T16:37:10Z
user: login: andyvan-ph
state: APPROVED
author_association: CONTRIBUTOR
submitted_at: 2025-04-14T17:13:43Z

Review comments:
diff_hunk: @@ -0,0 +1,83 @@
+---
+title: What to expect as you migrate
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+With your team onboard and a successful pilot completed, you can turn your attention to **planning your migration**.
+
+## Technical planning
+
+PostHog provides tools and guides to support you making this switch. Check out our migration section for details on moving from Amplitude, Mixpanel, LaunchDarkly and others.
+
+Stumped on any detail of the process? If you’ve already signed up and started sending events with a forecasted bill of $500 or more, our **onboarding** team will reach out to help. If you haven’t heard from us yet, [drop us a line](/talk-to-a-human) with your migration questions!
+
+<CalloutBox title="Avoid common setup pitfalls" type="caution">
+
+Don’t create separate projects for mobile and web. PostHog works best when you can see user behavior across all versions of your products in one set of data and views.
+
+Healthy integrations have a few things in common. It can help to review the [health check](/handbook/growth/sales/health-checks) documentation used by our sales team to tackle the most common ways to keep your bill manageable and predictable.
+
+If your historical data is above 50 GB, you should [reach out to our sales team](/talk-to-a-human) or [open a support ticket](/docs/support-options) so we can make sure everything goes through smoothly.
path: contents/docs/new-to-posthog/switch-guide/migration-planning.mdx
user: login: daniloc
body: > 50 GB

I chose this arbitrarily; lmk the scale we should indicate here
created_at: 2025-04-04T16:28:54Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,118 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and one easy integration gets you everything you need to build great products.
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: ivanagas
body: Avoiding saying easy twice
```suggestion
For new projects and companies, PostHog is an easy sell: one login and simple integration gets you everything you need to build great products.
```
created_at: 2025-04-09T17:36:49Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,118 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and one easy integration gets you everything you need to build great products.
+
+But convincing your teammates to switch horses later in a product's life can require some planning and diplomacy. We made you a cheatsheet to help make the case.
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: ivanagas
body: What do you mean "later in a product's life". Our product (PostHog) or their product? I'm not sure it is the right phrasing. 
created_at: 2025-04-09T17:37:42Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,118 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and one easy integration gets you everything you need to build great products.
+
+But convincing your teammates to switch horses later in a product's life can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+## Sharing social proof
+
+We’ve published [customer stories](/customers) with loads of companies who have loved their switch to PostHog. If you want to share a bit of social proof, these are a great place to start. Here are some choice quotes.
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: ivanagas
body: ```suggestion
We’ve published [customer stories](/customers) with loads of companies who have loved their switch to PostHog. Here are some choice quotes:
```
created_at: 2025-04-09T17:38:23Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,118 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and one easy integration gets you everything you need to build great products.
+
+But convincing your teammates to switch horses later in a product's life can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+## Sharing social proof
+
+We’ve published [customer stories](/customers) with loads of companies who have loved their switch to PostHog. If you want to share a bit of social proof, these are a great place to start. Here are some choice quotes.
+
+***
+
+[ElevenLabs](/customers/elevenlabs):
+
+<Quote
+    imageSource="/images/customers/elevenlabs-sam.jpg"
+    size="sm"
+    name="Sam Sklar"
+    title="Growth engineer, ElevenLabs"
+    quote={`“We use basically everything in PostHog to understand more about our users and to plan new launches. We have an onboarding survey which is the first thing you see when you sign up.”`}
+/>
+
+***
+
+[Octomind](/customers/octomind):
+
+<Quote
+    imageSource="/images/customers/maria_octomind.jpg"
+    size="sm"
+    name="Maria Zahorcova"
+    title="Chief Marketing Officer, Octomind"
+    quote={`“We’re product-led and it’s really, really important that we keep an eye not only on marketing activities but also the experience beyond that. It was great when I found out I could use PostHog to track data across the site, the docs, and the product — I just had to speak to our engineers about implementing it.”`}
+/>
+
+***
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: ivanagas
body: I think we should have one more quote here
created_at: 2025-04-09T17:38:53Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,118 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and one easy integration gets you everything you need to build great products.
+
+But convincing your teammates to switch horses later in a product's life can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+## Sharing social proof
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: ivanagas
body: I think we should move this section down. Social proof is more supporting than the main reason someone will be convinced. Maybe the right place for this is at the bottom. Definitely worth including though. 
created_at: 2025-04-09T17:39:46Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,118 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and one easy integration gets you everything you need to build great products.
+
+But convincing your teammates to switch horses later in a product's life can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+## Sharing social proof
+
+We’ve published [customer stories](/customers) with loads of companies who have loved their switch to PostHog. If you want to share a bit of social proof, these are a great place to start. Here are some choice quotes.
+
+***
+
+[ElevenLabs](/customers/elevenlabs):
+
+<Quote
+    imageSource="/images/customers/elevenlabs-sam.jpg"
+    size="sm"
+    name="Sam Sklar"
+    title="Growth engineer, ElevenLabs"
+    quote={`“We use basically everything in PostHog to understand more about our users and to plan new launches. We have an onboarding survey which is the first thing you see when you sign up.”`}
+/>
+
+***
+
+[Octomind](/customers/octomind):
+
+<Quote
+    imageSource="/images/customers/maria_octomind.jpg"
+    size="sm"
+    name="Maria Zahorcova"
+    title="Chief Marketing Officer, Octomind"
+    quote={`“We’re product-led and it’s really, really important that we keep an eye not only on marketing activities but also the experience beyond that. It was great when I found out I could use PostHog to track data across the site, the docs, and the product — I just had to speak to our engineers about implementing it.”`}
+/>
+
+***
+
+## Advantages for everyone
+
+PostHog is one login and one bill.
+
+That means less headache for more power, with all your data available across a range of products that help you understand user behavior as it happens.
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: ivanagas
body: This is a sentence fragment, feels like it is missing something
created_at: 2025-04-09T17:40:48Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,118 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and one easy integration gets you everything you need to build great products.
+
+But convincing your teammates to switch horses later in a product's life can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+## Sharing social proof
+
+We’ve published [customer stories](/customers) with loads of companies who have loved their switch to PostHog. If you want to share a bit of social proof, these are a great place to start. Here are some choice quotes.
+
+***
+
+[ElevenLabs](/customers/elevenlabs):
+
+<Quote
+    imageSource="/images/customers/elevenlabs-sam.jpg"
+    size="sm"
+    name="Sam Sklar"
+    title="Growth engineer, ElevenLabs"
+    quote={`“We use basically everything in PostHog to understand more about our users and to plan new launches. We have an onboarding survey which is the first thing you see when you sign up.”`}
+/>
+
+***
+
+[Octomind](/customers/octomind):
+
+<Quote
+    imageSource="/images/customers/maria_octomind.jpg"
+    size="sm"
+    name="Maria Zahorcova"
+    title="Chief Marketing Officer, Octomind"
+    quote={`“We’re product-led and it’s really, really important that we keep an eye not only on marketing activities but also the experience beyond that. It was great when I found out I could use PostHog to track data across the site, the docs, and the product — I just had to speak to our engineers about implementing it.”`}
+/>
+
+***
+
+## Advantages for everyone
+
+PostHog is one login and one bill.
+
+That means less headache for more power, with all your data available across a range of products that help you understand user behavior as it happens.
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: ivanagas
body: ```suggestion
PostHog is one login and one bill that means less headache for more power. All your data becomes available across a range of products to help you understand user behavior as it happens.
```
created_at: 2025-04-09T17:41:39Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,118 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and one easy integration gets you everything you need to build great products.
+
+But convincing your teammates to switch horses later in a product's life can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+## Sharing social proof
+
+We’ve published [customer stories](/customers) with loads of companies who have loved their switch to PostHog. If you want to share a bit of social proof, these are a great place to start. Here are some choice quotes.
+
+***
+
+[ElevenLabs](/customers/elevenlabs):
+
+<Quote
+    imageSource="/images/customers/elevenlabs-sam.jpg"
+    size="sm"
+    name="Sam Sklar"
+    title="Growth engineer, ElevenLabs"
+    quote={`“We use basically everything in PostHog to understand more about our users and to plan new launches. We have an onboarding survey which is the first thing you see when you sign up.”`}
+/>
+
+***
+
+[Octomind](/customers/octomind):
+
+<Quote
+    imageSource="/images/customers/maria_octomind.jpg"
+    size="sm"
+    name="Maria Zahorcova"
+    title="Chief Marketing Officer, Octomind"
+    quote={`“We’re product-led and it’s really, really important that we keep an eye not only on marketing activities but also the experience beyond that. It was great when I found out I could use PostHog to track data across the site, the docs, and the product — I just had to speak to our engineers about implementing it.”`}
+/>
+
+***
+
+## Advantages for everyone
+
+PostHog is one login and one bill.
+
+That means less headache for more power, with all your data available across a range of products that help you understand user behavior as it happens.
+
+You'll get a responsive team that cares about user needs, delivering improvements and customer requests constantly.
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: ivanagas
body: ```suggestion
You'll get a responsive team that cares about user needs, delivering improvements, and customer requests constantly.
```
created_at: 2025-04-09T17:41:53Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,118 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and one easy integration gets you everything you need to build great products.
+
+But convincing your teammates to switch horses later in a product's life can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+## Sharing social proof
+
+We’ve published [customer stories](/customers) with loads of companies who have loved their switch to PostHog. If you want to share a bit of social proof, these are a great place to start. Here are some choice quotes.
+
+***
+
+[ElevenLabs](/customers/elevenlabs):
+
+<Quote
+    imageSource="/images/customers/elevenlabs-sam.jpg"
+    size="sm"
+    name="Sam Sklar"
+    title="Growth engineer, ElevenLabs"
+    quote={`“We use basically everything in PostHog to understand more about our users and to plan new launches. We have an onboarding survey which is the first thing you see when you sign up.”`}
+/>
+
+***
+
+[Octomind](/customers/octomind):
+
+<Quote
+    imageSource="/images/customers/maria_octomind.jpg"
+    size="sm"
+    name="Maria Zahorcova"
+    title="Chief Marketing Officer, Octomind"
+    quote={`“We’re product-led and it’s really, really important that we keep an eye not only on marketing activities but also the experience beyond that. It was great when I found out I could use PostHog to track data across the site, the docs, and the product — I just had to speak to our engineers about implementing it.”`}
+/>
+
+***
+
+## Advantages for everyone
+
+PostHog is one login and one bill.
+
+That means less headache for more power, with all your data available across a range of products that help you understand user behavior as it happens.
+
+You'll get a responsive team that cares about user needs, delivering improvements and customer requests constantly.
+
+PostHog is completely agnostic to the language, framework and stack you build your product with. You can adopt it incrementally, adding more as needed.
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: ivanagas
body: ```suggestion
PostHog is completely agnostic to the language, framework, and stack you build your product with. You can adopt it incrementally, adding new functionality as needed.
```
created_at: 2025-04-09T17:42:14Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,118 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and one easy integration gets you everything you need to build great products.
+
+But convincing your teammates to switch horses later in a product's life can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+## Sharing social proof
+
+We’ve published [customer stories](/customers) with loads of companies who have loved their switch to PostHog. If you want to share a bit of social proof, these are a great place to start. Here are some choice quotes.
+
+***
+
+[ElevenLabs](/customers/elevenlabs):
+
+<Quote
+    imageSource="/images/customers/elevenlabs-sam.jpg"
+    size="sm"
+    name="Sam Sklar"
+    title="Growth engineer, ElevenLabs"
+    quote={`“We use basically everything in PostHog to understand more about our users and to plan new launches. We have an onboarding survey which is the first thing you see when you sign up.”`}
+/>
+
+***
+
+[Octomind](/customers/octomind):
+
+<Quote
+    imageSource="/images/customers/maria_octomind.jpg"
+    size="sm"
+    name="Maria Zahorcova"
+    title="Chief Marketing Officer, Octomind"
+    quote={`“We’re product-led and it’s really, really important that we keep an eye not only on marketing activities but also the experience beyond that. It was great when I found out I could use PostHog to track data across the site, the docs, and the product — I just had to speak to our engineers about implementing it.”`}
+/>
+
+***
+
+## Advantages for everyone
+
+PostHog is one login and one bill.
+
+That means less headache for more power, with all your data available across a range of products that help you understand user behavior as it happens.
+
+You'll get a responsive team that cares about user needs, delivering improvements and customer requests constantly.
+
+PostHog is completely agnostic to the language, framework and stack you build your product with. You can adopt it incrementally, adding more as needed.
+
+Best of all, PostHog is modern, fast, and built so that you’ll actually enjoy using it.
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: ivanagas
body: This is a weak point.

1. Honestly, we're not really that "fast", querying takes time and the interface can be complex.
2. I'm not sure what "modern" means.
created_at: 2025-04-09T17:43:20Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,118 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and one easy integration gets you everything you need to build great products.
+
+But convincing your teammates to switch horses later in a product's life can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+## Sharing social proof
+
+We’ve published [customer stories](/customers) with loads of companies who have loved their switch to PostHog. If you want to share a bit of social proof, these are a great place to start. Here are some choice quotes.
+
+***
+
+[ElevenLabs](/customers/elevenlabs):
+
+<Quote
+    imageSource="/images/customers/elevenlabs-sam.jpg"
+    size="sm"
+    name="Sam Sklar"
+    title="Growth engineer, ElevenLabs"
+    quote={`“We use basically everything in PostHog to understand more about our users and to plan new launches. We have an onboarding survey which is the first thing you see when you sign up.”`}
+/>
+
+***
+
+[Octomind](/customers/octomind):
+
+<Quote
+    imageSource="/images/customers/maria_octomind.jpg"
+    size="sm"
+    name="Maria Zahorcova"
+    title="Chief Marketing Officer, Octomind"
+    quote={`“We’re product-led and it’s really, really important that we keep an eye not only on marketing activities but also the experience beyond that. It was great when I found out I could use PostHog to track data across the site, the docs, and the product — I just had to speak to our engineers about implementing it.”`}
+/>
+
+***
+
+## Advantages for everyone
+
+PostHog is one login and one bill.
+
+That means less headache for more power, with all your data available across a range of products that help you understand user behavior as it happens.
+
+You'll get a responsive team that cares about user needs, delivering improvements and customer requests constantly.
+
+PostHog is completely agnostic to the language, framework and stack you build your product with. You can adopt it incrementally, adding more as needed.
+
+Best of all, PostHog is modern, fast, and built so that you’ll actually enjoy using it.
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: ivanagas
body: Free to use and try might be a replacement if we haven't used that point too much.
created_at: 2025-04-09T17:43:59Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,118 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and one easy integration gets you everything you need to build great products.
+
+But convincing your teammates to switch horses later in a product's life can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+## Sharing social proof
+
+We’ve published [customer stories](/customers) with loads of companies who have loved their switch to PostHog. If you want to share a bit of social proof, these are a great place to start. Here are some choice quotes.
+
+***
+
+[ElevenLabs](/customers/elevenlabs):
+
+<Quote
+    imageSource="/images/customers/elevenlabs-sam.jpg"
+    size="sm"
+    name="Sam Sklar"
+    title="Growth engineer, ElevenLabs"
+    quote={`“We use basically everything in PostHog to understand more about our users and to plan new launches. We have an onboarding survey which is the first thing you see when you sign up.”`}
+/>
+
+***
+
+[Octomind](/customers/octomind):
+
+<Quote
+    imageSource="/images/customers/maria_octomind.jpg"
+    size="sm"
+    name="Maria Zahorcova"
+    title="Chief Marketing Officer, Octomind"
+    quote={`“We’re product-led and it’s really, really important that we keep an eye not only on marketing activities but also the experience beyond that. It was great when I found out I could use PostHog to track data across the site, the docs, and the product — I just had to speak to our engineers about implementing it.”`}
+/>
+
+***
+
+## Advantages for everyone
+
+PostHog is one login and one bill.
+
+That means less headache for more power, with all your data available across a range of products that help you understand user behavior as it happens.
+
+You'll get a responsive team that cares about user needs, delivering improvements and customer requests constantly.
+
+PostHog is completely agnostic to the language, framework and stack you build your product with. You can adopt it incrementally, adding more as needed.
+
+Best of all, PostHog is modern, fast, and built so that you’ll actually enjoy using it.
+
+***
+
+## Persuading product teams
+
+PostHog gives product teams the power to understand users, improve adoption and test assumptions. Your product teammates can get dive in immediately without having to wait for engineers to write new code or hook up an integration.
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: ivanagas
body: ```suggestion
PostHog gives product teams the power to understand users, improve adoption, and test assumptions. Your product teammates can dive in immediately without having to wait for engineers to write new code or hook up an integration.
```
created_at: 2025-04-09T17:44:27Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,118 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and one easy integration gets you everything you need to build great products.
+
+But convincing your teammates to switch horses later in a product's life can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+## Sharing social proof
+
+We’ve published [customer stories](/customers) with loads of companies who have loved their switch to PostHog. If you want to share a bit of social proof, these are a great place to start. Here are some choice quotes.
+
+***
+
+[ElevenLabs](/customers/elevenlabs):
+
+<Quote
+    imageSource="/images/customers/elevenlabs-sam.jpg"
+    size="sm"
+    name="Sam Sklar"
+    title="Growth engineer, ElevenLabs"
+    quote={`“We use basically everything in PostHog to understand more about our users and to plan new launches. We have an onboarding survey which is the first thing you see when you sign up.”`}
+/>
+
+***
+
+[Octomind](/customers/octomind):
+
+<Quote
+    imageSource="/images/customers/maria_octomind.jpg"
+    size="sm"
+    name="Maria Zahorcova"
+    title="Chief Marketing Officer, Octomind"
+    quote={`“We’re product-led and it’s really, really important that we keep an eye not only on marketing activities but also the experience beyond that. It was great when I found out I could use PostHog to track data across the site, the docs, and the product — I just had to speak to our engineers about implementing it.”`}
+/>
+
+***
+
+## Advantages for everyone
+
+PostHog is one login and one bill.
+
+That means less headache for more power, with all your data available across a range of products that help you understand user behavior as it happens.
+
+You'll get a responsive team that cares about user needs, delivering improvements and customer requests constantly.
+
+PostHog is completely agnostic to the language, framework and stack you build your product with. You can adopt it incrementally, adding more as needed.
+
+Best of all, PostHog is modern, fast, and built so that you’ll actually enjoy using it.
+
+***
+
+## Persuading product teams
+
+PostHog gives product teams the power to understand users, improve adoption and test assumptions. Your product teammates can get dive in immediately without having to wait for engineers to write new code or hook up an integration.
+
+**[Report anything](/docs/product-analytics/insights)** with charts, trend reporting and [dashboards](/docs/product-analytics/dashboards) that are easy to build, but also deeply customizable for SQL enthusiasts.
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: ivanagas
body: ```suggestion
**[Visualize anything](/docs/product-analytics/insights)** with charts, trend reporting, and [dashboards](/docs/product-analytics/dashboards) that are easy to build, but also deeply customizable for SQL enthusiasts.
```
created_at: 2025-04-09T17:44:58Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,118 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and one easy integration gets you everything you need to build great products.
+
+But convincing your teammates to switch horses later in a product's life can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+## Sharing social proof
+
+We’ve published [customer stories](/customers) with loads of companies who have loved their switch to PostHog. If you want to share a bit of social proof, these are a great place to start. Here are some choice quotes.
+
+***
+
+[ElevenLabs](/customers/elevenlabs):
+
+<Quote
+    imageSource="/images/customers/elevenlabs-sam.jpg"
+    size="sm"
+    name="Sam Sklar"
+    title="Growth engineer, ElevenLabs"
+    quote={`“We use basically everything in PostHog to understand more about our users and to plan new launches. We have an onboarding survey which is the first thing you see when you sign up.”`}
+/>
+
+***
+
+[Octomind](/customers/octomind):
+
+<Quote
+    imageSource="/images/customers/maria_octomind.jpg"
+    size="sm"
+    name="Maria Zahorcova"
+    title="Chief Marketing Officer, Octomind"
+    quote={`“We’re product-led and it’s really, really important that we keep an eye not only on marketing activities but also the experience beyond that. It was great when I found out I could use PostHog to track data across the site, the docs, and the product — I just had to speak to our engineers about implementing it.”`}
+/>
+
+***
+
+## Advantages for everyone
+
+PostHog is one login and one bill.
+
+That means less headache for more power, with all your data available across a range of products that help you understand user behavior as it happens.
+
+You'll get a responsive team that cares about user needs, delivering improvements and customer requests constantly.
+
+PostHog is completely agnostic to the language, framework and stack you build your product with. You can adopt it incrementally, adding more as needed.
+
+Best of all, PostHog is modern, fast, and built so that you’ll actually enjoy using it.
+
+***
+
+## Persuading product teams
+
+PostHog gives product teams the power to understand users, improve adoption and test assumptions. Your product teammates can get dive in immediately without having to wait for engineers to write new code or hook up an integration.
+
+**[Report anything](/docs/product-analytics/insights)** with charts, trend reporting and [dashboards](/docs/product-analytics/dashboards) that are easy to build, but also deeply customizable for SQL enthusiasts.
+
+**Learn anything you want** about everything the user touches in the product with [autocapture](/docs/product-analytics/autocapture).
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: ivanagas
body: ```suggestion
**Learn anything you want** about everything the user touches in the product without manual instrumentation with [autocapture](/docs/product-analytics/autocapture).
```
created_at: 2025-04-09T17:45:51Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,118 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and one easy integration gets you everything you need to build great products.
+
+But convincing your teammates to switch horses later in a product's life can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+## Sharing social proof
+
+We’ve published [customer stories](/customers) with loads of companies who have loved their switch to PostHog. If you want to share a bit of social proof, these are a great place to start. Here are some choice quotes.
+
+***
+
+[ElevenLabs](/customers/elevenlabs):
+
+<Quote
+    imageSource="/images/customers/elevenlabs-sam.jpg"
+    size="sm"
+    name="Sam Sklar"
+    title="Growth engineer, ElevenLabs"
+    quote={`“We use basically everything in PostHog to understand more about our users and to plan new launches. We have an onboarding survey which is the first thing you see when you sign up.”`}
+/>
+
+***
+
+[Octomind](/customers/octomind):
+
+<Quote
+    imageSource="/images/customers/maria_octomind.jpg"
+    size="sm"
+    name="Maria Zahorcova"
+    title="Chief Marketing Officer, Octomind"
+    quote={`“We’re product-led and it’s really, really important that we keep an eye not only on marketing activities but also the experience beyond that. It was great when I found out I could use PostHog to track data across the site, the docs, and the product — I just had to speak to our engineers about implementing it.”`}
+/>
+
+***
+
+## Advantages for everyone
+
+PostHog is one login and one bill.
+
+That means less headache for more power, with all your data available across a range of products that help you understand user behavior as it happens.
+
+You'll get a responsive team that cares about user needs, delivering improvements and customer requests constantly.
+
+PostHog is completely agnostic to the language, framework and stack you build your product with. You can adopt it incrementally, adding more as needed.
+
+Best of all, PostHog is modern, fast, and built so that you’ll actually enjoy using it.
+
+***
+
+## Persuading product teams
+
+PostHog gives product teams the power to understand users, improve adoption and test assumptions. Your product teammates can get dive in immediately without having to wait for engineers to write new code or hook up an integration.
+
+**[Report anything](/docs/product-analytics/insights)** with charts, trend reporting and [dashboards](/docs/product-analytics/dashboards) that are easy to build, but also deeply customizable for SQL enthusiasts.
+
+**Learn anything you want** about everything the user touches in the product with [autocapture](/docs/product-analytics/autocapture).
+
+**Get clarity about navigation** and user priorities with [heatmaps](/docs/toolbar/heatmaps).
+
+Use [session replay](/docs/session-replay/installation) to **reveal bugs, expose friction, and help instantly answer questions** like “is this new design working?”
+
+**Send events and other details to any other tool**, powering automations and keeping data in sync, with setup you can accomplish in seconds, fully customizable for any API or webhook. [Data pipelines](/docs/cdp) makes it easy.
+
+**Gather feedback** from exactly the users you want to reach with no-code [surveys](/docs/surveys/creating-surveys) that launch instantly.
+
+**Integrate revenue data** from [Stripe](/docs/cdp/sources/stripe) and other sources using data warehouse, so you can get a clear picture of what changes really move the needle.
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: ivanagas
body: I think this should be higher than sending events to other destinations
created_at: 2025-04-09T17:46:12Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,118 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and one easy integration gets you everything you need to build great products.
+
+But convincing your teammates to switch horses later in a product's life can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+## Sharing social proof
+
+We’ve published [customer stories](/customers) with loads of companies who have loved their switch to PostHog. If you want to share a bit of social proof, these are a great place to start. Here are some choice quotes.
+
+***
+
+[ElevenLabs](/customers/elevenlabs):
+
+<Quote
+    imageSource="/images/customers/elevenlabs-sam.jpg"
+    size="sm"
+    name="Sam Sklar"
+    title="Growth engineer, ElevenLabs"
+    quote={`“We use basically everything in PostHog to understand more about our users and to plan new launches. We have an onboarding survey which is the first thing you see when you sign up.”`}
+/>
+
+***
+
+[Octomind](/customers/octomind):
+
+<Quote
+    imageSource="/images/customers/maria_octomind.jpg"
+    size="sm"
+    name="Maria Zahorcova"
+    title="Chief Marketing Officer, Octomind"
+    quote={`“We’re product-led and it’s really, really important that we keep an eye not only on marketing activities but also the experience beyond that. It was great when I found out I could use PostHog to track data across the site, the docs, and the product — I just had to speak to our engineers about implementing it.”`}
+/>
+
+***
+
+## Advantages for everyone
+
+PostHog is one login and one bill.
+
+That means less headache for more power, with all your data available across a range of products that help you understand user behavior as it happens.
+
+You'll get a responsive team that cares about user needs, delivering improvements and customer requests constantly.
+
+PostHog is completely agnostic to the language, framework and stack you build your product with. You can adopt it incrementally, adding more as needed.
+
+Best of all, PostHog is modern, fast, and built so that you’ll actually enjoy using it.
+
+***
+
+## Persuading product teams
+
+PostHog gives product teams the power to understand users, improve adoption and test assumptions. Your product teammates can get dive in immediately without having to wait for engineers to write new code or hook up an integration.
+
+**[Report anything](/docs/product-analytics/insights)** with charts, trend reporting and [dashboards](/docs/product-analytics/dashboards) that are easy to build, but also deeply customizable for SQL enthusiasts.
+
+**Learn anything you want** about everything the user touches in the product with [autocapture](/docs/product-analytics/autocapture).
+
+**Get clarity about navigation** and user priorities with [heatmaps](/docs/toolbar/heatmaps).
+
+Use [session replay](/docs/session-replay/installation) to **reveal bugs, expose friction, and help instantly answer questions** like “is this new design working?”
+
+**Send events and other details to any other tool**, powering automations and keeping data in sync, with setup you can accomplish in seconds, fully customizable for any API or webhook. [Data pipelines](/docs/cdp) makes it easy.
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: ivanagas
body: I don't think this is a big selling point for product teams, but I could be wrong. Seems much more like a marketing thing...
created_at: 2025-04-09T17:46:36Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,118 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and one easy integration gets you everything you need to build great products.
+
+But convincing your teammates to switch horses later in a product's life can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+## Sharing social proof
+
+We’ve published [customer stories](/customers) with loads of companies who have loved their switch to PostHog. If you want to share a bit of social proof, these are a great place to start. Here are some choice quotes.
+
+***
+
+[ElevenLabs](/customers/elevenlabs):
+
+<Quote
+    imageSource="/images/customers/elevenlabs-sam.jpg"
+    size="sm"
+    name="Sam Sklar"
+    title="Growth engineer, ElevenLabs"
+    quote={`“We use basically everything in PostHog to understand more about our users and to plan new launches. We have an onboarding survey which is the first thing you see when you sign up.”`}
+/>
+
+***
+
+[Octomind](/customers/octomind):
+
+<Quote
+    imageSource="/images/customers/maria_octomind.jpg"
+    size="sm"
+    name="Maria Zahorcova"
+    title="Chief Marketing Officer, Octomind"
+    quote={`“We’re product-led and it’s really, really important that we keep an eye not only on marketing activities but also the experience beyond that. It was great when I found out I could use PostHog to track data across the site, the docs, and the product — I just had to speak to our engineers about implementing it.”`}
+/>
+
+***
+
+## Advantages for everyone
+
+PostHog is one login and one bill.
+
+That means less headache for more power, with all your data available across a range of products that help you understand user behavior as it happens.
+
+You'll get a responsive team that cares about user needs, delivering improvements and customer requests constantly.
+
+PostHog is completely agnostic to the language, framework and stack you build your product with. You can adopt it incrementally, adding more as needed.
+
+Best of all, PostHog is modern, fast, and built so that you’ll actually enjoy using it.
+
+***
+
+## Persuading product teams
+
+PostHog gives product teams the power to understand users, improve adoption and test assumptions. Your product teammates can get dive in immediately without having to wait for engineers to write new code or hook up an integration.
+
+**[Report anything](/docs/product-analytics/insights)** with charts, trend reporting and [dashboards](/docs/product-analytics/dashboards) that are easy to build, but also deeply customizable for SQL enthusiasts.
+
+**Learn anything you want** about everything the user touches in the product with [autocapture](/docs/product-analytics/autocapture).
+
+**Get clarity about navigation** and user priorities with [heatmaps](/docs/toolbar/heatmaps).
+
+Use [session replay](/docs/session-replay/installation) to **reveal bugs, expose friction, and help instantly answer questions** like “is this new design working?”
+
+**Send events and other details to any other tool**, powering automations and keeping data in sync, with setup you can accomplish in seconds, fully customizable for any API or webhook. [Data pipelines](/docs/cdp) makes it easy.
+
+**Gather feedback** from exactly the users you want to reach with no-code [surveys](/docs/surveys/creating-surveys) that launch instantly.
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: ivanagas
body: ```suggestion
**Gather feedback and book user interviews** from exactly the users you want to reach with no-code [surveys](/docs/surveys/creating-surveys) that launch instantly.
```
created_at: 2025-04-09T17:47:08Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,118 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and one easy integration gets you everything you need to build great products.
+
+But convincing your teammates to switch horses later in a product's life can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+## Sharing social proof
+
+We’ve published [customer stories](/customers) with loads of companies who have loved their switch to PostHog. If you want to share a bit of social proof, these are a great place to start. Here are some choice quotes.
+
+***
+
+[ElevenLabs](/customers/elevenlabs):
+
+<Quote
+    imageSource="/images/customers/elevenlabs-sam.jpg"
+    size="sm"
+    name="Sam Sklar"
+    title="Growth engineer, ElevenLabs"
+    quote={`“We use basically everything in PostHog to understand more about our users and to plan new launches. We have an onboarding survey which is the first thing you see when you sign up.”`}
+/>
+
+***
+
+[Octomind](/customers/octomind):
+
+<Quote
+    imageSource="/images/customers/maria_octomind.jpg"
+    size="sm"
+    name="Maria Zahorcova"
+    title="Chief Marketing Officer, Octomind"
+    quote={`“We’re product-led and it’s really, really important that we keep an eye not only on marketing activities but also the experience beyond that. It was great when I found out I could use PostHog to track data across the site, the docs, and the product — I just had to speak to our engineers about implementing it.”`}
+/>
+
+***
+
+## Advantages for everyone
+
+PostHog is one login and one bill.
+
+That means less headache for more power, with all your data available across a range of products that help you understand user behavior as it happens.
+
+You'll get a responsive team that cares about user needs, delivering improvements and customer requests constantly.
+
+PostHog is completely agnostic to the language, framework and stack you build your product with. You can adopt it incrementally, adding more as needed.
+
+Best of all, PostHog is modern, fast, and built so that you’ll actually enjoy using it.
+
+***
+
+## Persuading product teams
+
+PostHog gives product teams the power to understand users, improve adoption and test assumptions. Your product teammates can get dive in immediately without having to wait for engineers to write new code or hook up an integration.
+
+**[Report anything](/docs/product-analytics/insights)** with charts, trend reporting and [dashboards](/docs/product-analytics/dashboards) that are easy to build, but also deeply customizable for SQL enthusiasts.
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: ivanagas
body: I think it makes sense to use a list for all of the below points
created_at: 2025-04-09T17:47:35Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,118 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and one easy integration gets you everything you need to build great products.
+
+But convincing your teammates to switch horses later in a product's life can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+## Sharing social proof
+
+We’ve published [customer stories](/customers) with loads of companies who have loved their switch to PostHog. If you want to share a bit of social proof, these are a great place to start. Here are some choice quotes.
+
+***
+
+[ElevenLabs](/customers/elevenlabs):
+
+<Quote
+    imageSource="/images/customers/elevenlabs-sam.jpg"
+    size="sm"
+    name="Sam Sklar"
+    title="Growth engineer, ElevenLabs"
+    quote={`“We use basically everything in PostHog to understand more about our users and to plan new launches. We have an onboarding survey which is the first thing you see when you sign up.”`}
+/>
+
+***
+
+[Octomind](/customers/octomind):
+
+<Quote
+    imageSource="/images/customers/maria_octomind.jpg"
+    size="sm"
+    name="Maria Zahorcova"
+    title="Chief Marketing Officer, Octomind"
+    quote={`“We’re product-led and it’s really, really important that we keep an eye not only on marketing activities but also the experience beyond that. It was great when I found out I could use PostHog to track data across the site, the docs, and the product — I just had to speak to our engineers about implementing it.”`}
+/>
+
+***
+
+## Advantages for everyone
+
+PostHog is one login and one bill.
+
+That means less headache for more power, with all your data available across a range of products that help you understand user behavior as it happens.
+
+You'll get a responsive team that cares about user needs, delivering improvements and customer requests constantly.
+
+PostHog is completely agnostic to the language, framework and stack you build your product with. You can adopt it incrementally, adding more as needed.
+
+Best of all, PostHog is modern, fast, and built so that you’ll actually enjoy using it.
+
+***
+
+## Persuading product teams
+
+PostHog gives product teams the power to understand users, improve adoption and test assumptions. Your product teammates can get dive in immediately without having to wait for engineers to write new code or hook up an integration.
+
+**[Report anything](/docs/product-analytics/insights)** with charts, trend reporting and [dashboards](/docs/product-analytics/dashboards) that are easy to build, but also deeply customizable for SQL enthusiasts.
+
+**Learn anything you want** about everything the user touches in the product with [autocapture](/docs/product-analytics/autocapture).
+
+**Get clarity about navigation** and user priorities with [heatmaps](/docs/toolbar/heatmaps).
+
+Use [session replay](/docs/session-replay/installation) to **reveal bugs, expose friction, and help instantly answer questions** like “is this new design working?”
+
+**Send events and other details to any other tool**, powering automations and keeping data in sync, with setup you can accomplish in seconds, fully customizable for any API or webhook. [Data pipelines](/docs/cdp) makes it easy.
+
+**Gather feedback** from exactly the users you want to reach with no-code [surveys](/docs/surveys/creating-surveys) that launch instantly.
+
+**Integrate revenue data** from [Stripe](/docs/cdp/sources/stripe) and other sources using data warehouse, so you can get a clear picture of what changes really move the needle.
+
+**Get unblocked by PostHog’s helpful sales and support teams,** ensuring you get the insights and information you need quickly.
+
+***
+
+## Good news for engineering teams
+
+PostHog is designed for developers. We’ve got a dedicated technical staff standing by to help keep you on track. When you reach out to support, you’ll be talking to someone who knows the technical details of the product really well.
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: ivanagas
body: I don't think "support" should be the first point. This one is better at the very least:

> The project is [developed in the open](https://github.com/PostHog/posthog), with a [public roadmap](/roadmap) and [dozens of pull requests landing]([https://github.com/PostHog/posthog/pulls?q=is%3Apr+is%3Aclosed](https://github.com/PostHog/posthog/pulls?q=sort%3Aupdated-desc+is%3Apr+is%3Aclosed)) each week.
created_at: 2025-04-09T17:49:04Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,118 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and one easy integration gets you everything you need to build great products.
+
+But convincing your teammates to switch horses later in a product's life can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+## Sharing social proof
+
+We’ve published [customer stories](/customers) with loads of companies who have loved their switch to PostHog. If you want to share a bit of social proof, these are a great place to start. Here are some choice quotes.
+
+***
+
+[ElevenLabs](/customers/elevenlabs):
+
+<Quote
+    imageSource="/images/customers/elevenlabs-sam.jpg"
+    size="sm"
+    name="Sam Sklar"
+    title="Growth engineer, ElevenLabs"
+    quote={`“We use basically everything in PostHog to understand more about our users and to plan new launches. We have an onboarding survey which is the first thing you see when you sign up.”`}
+/>
+
+***
+
+[Octomind](/customers/octomind):
+
+<Quote
+    imageSource="/images/customers/maria_octomind.jpg"
+    size="sm"
+    name="Maria Zahorcova"
+    title="Chief Marketing Officer, Octomind"
+    quote={`“We’re product-led and it’s really, really important that we keep an eye not only on marketing activities but also the experience beyond that. It was great when I found out I could use PostHog to track data across the site, the docs, and the product — I just had to speak to our engineers about implementing it.”`}
+/>
+
+***
+
+## Advantages for everyone
+
+PostHog is one login and one bill.
+
+That means less headache for more power, with all your data available across a range of products that help you understand user behavior as it happens.
+
+You'll get a responsive team that cares about user needs, delivering improvements and customer requests constantly.
+
+PostHog is completely agnostic to the language, framework and stack you build your product with. You can adopt it incrementally, adding more as needed.
+
+Best of all, PostHog is modern, fast, and built so that you’ll actually enjoy using it.
+
+***
+
+## Persuading product teams
+
+PostHog gives product teams the power to understand users, improve adoption and test assumptions. Your product teammates can get dive in immediately without having to wait for engineers to write new code or hook up an integration.
+
+**[Report anything](/docs/product-analytics/insights)** with charts, trend reporting and [dashboards](/docs/product-analytics/dashboards) that are easy to build, but also deeply customizable for SQL enthusiasts.
+
+**Learn anything you want** about everything the user touches in the product with [autocapture](/docs/product-analytics/autocapture).
+
+**Get clarity about navigation** and user priorities with [heatmaps](/docs/toolbar/heatmaps).
+
+Use [session replay](/docs/session-replay/installation) to **reveal bugs, expose friction, and help instantly answer questions** like “is this new design working?”
+
+**Send events and other details to any other tool**, powering automations and keeping data in sync, with setup you can accomplish in seconds, fully customizable for any API or webhook. [Data pipelines](/docs/cdp) makes it easy.
+
+**Gather feedback** from exactly the users you want to reach with no-code [surveys](/docs/surveys/creating-surveys) that launch instantly.
+
+**Integrate revenue data** from [Stripe](/docs/cdp/sources/stripe) and other sources using data warehouse, so you can get a clear picture of what changes really move the needle.
+
+**Get unblocked by PostHog’s helpful sales and support teams,** ensuring you get the insights and information you need quickly.
+
+***
+
+## Good news for engineering teams
+
+PostHog is designed for developers. We’ve got a dedicated technical staff standing by to help keep you on track. When you reach out to support, you’ll be talking to someone who knows the technical details of the product really well.
+
+While other products are low-velocity black boxes, we’re constantly making PostHog better.
+
+The project is [developed in the open](https://github.com/PostHog/posthog), with a [public roadmap](/roadmap) and [dozens of pull requests landing](https://github.com/PostHog/posthog/pulls?q=is%3Apr+is%3Aclosed) each week.
+
+Giving other teams the data they want becomes much easier with PostHog in the mix, with lower friction for engineering, and loads of features everyone can use without complex setup.
+
+**Consolidate the tools your company needs**, with one login, one integration, one bill, and one [deep set of docs](/docs).
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: ivanagas
body: Docs is sort of hidden in here, maybe its own point?

created_at: 2025-04-09T17:49:39Z
author_association: CONTRIBUTOR
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: ivanagas
body: Overall, I don't think this is as effective as it should be. The content is great, but the format is letting it down a little. The "teams" sections should be:

- Intro paragraph
- 3-5 key points as bullets

That's it
created_at: 2025-04-09T17:52:21Z
author_association: CONTRIBUTOR
diff_hunk: @@ -2109,6 +2109,21 @@ export const docsMenu = {
                     url: '/docs/new-to-posthog/revenue',
                     icon: 'IconHandMoney',
                 },
+                {
+                    name: 'Switching to PostHog',
+                    url: '/docs/new-to-posthog/switch-guide/switching-to-posthog',
path: src/navs/index.js
user: login: ivanagas
body: One slightly annoying land mine is that having a parent link, without a page in the children (like "Overview") causes it to break on mobile (you can't click the link and open the children).

Maybe the section could be "Switching to PostHog" and `docs/new-to-posthog/switch-guide/switching-to-posthog` becomes "Convincing your team" as a page title and URL.
created_at: 2025-04-09T17:54:38Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,118 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and one easy integration gets you everything you need to build great products.
+
+But convincing your teammates to switch horses later in a product's life can require some planning and diplomacy. We made you a cheatsheet to help make the case.
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: daniloc
body: Maybe I don't need to say it all
created_at: 2025-04-09T18:02:01Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,118 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and one easy integration gets you everything you need to build great products.
+
+But convincing your teammates to switch horses later in a product's life can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+## Sharing social proof
+
+We’ve published [customer stories](/customers) with loads of companies who have loved their switch to PostHog. If you want to share a bit of social proof, these are a great place to start. Here are some choice quotes.
+
+***
+
+[ElevenLabs](/customers/elevenlabs):
+
+<Quote
+    imageSource="/images/customers/elevenlabs-sam.jpg"
+    size="sm"
+    name="Sam Sklar"
+    title="Growth engineer, ElevenLabs"
+    quote={`“We use basically everything in PostHog to understand more about our users and to plan new launches. We have an onboarding survey which is the first thing you see when you sign up.”`}
+/>
+
+***
+
+[Octomind](/customers/octomind):
+
+<Quote
+    imageSource="/images/customers/maria_octomind.jpg"
+    size="sm"
+    name="Maria Zahorcova"
+    title="Chief Marketing Officer, Octomind"
+    quote={`“We’re product-led and it’s really, really important that we keep an eye not only on marketing activities but also the experience beyond that. It was great when I found out I could use PostHog to track data across the site, the docs, and the product — I just had to speak to our engineers about implementing it.”`}
+/>
+
+***
+
+## Advantages for everyone
+
+PostHog is one login and one bill.
+
+That means less headache for more power, with all your data available across a range of products that help you understand user behavior as it happens.
+
+You'll get a responsive team that cares about user needs, delivering improvements and customer requests constantly.
+
+PostHog is completely agnostic to the language, framework and stack you build your product with. You can adopt it incrementally, adding more as needed.
+
+Best of all, PostHog is modern, fast, and built so that you’ll actually enjoy using it.
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: daniloc
body: So by contrast, Amplitood, Muxpanel and GA are ANCIENT, right. We're the best balance of "sturdy and reliable" while built in this decade, and you can feel it in all the ways the product doesn't suck.

Some other way to say it maybe?
created_at: 2025-04-09T18:07:50Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,118 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and one easy integration gets you everything you need to build great products.
+
+But convincing your teammates to switch horses later in a product's life can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+## Sharing social proof
+
+We’ve published [customer stories](/customers) with loads of companies who have loved their switch to PostHog. If you want to share a bit of social proof, these are a great place to start. Here are some choice quotes.
+
+***
+
+[ElevenLabs](/customers/elevenlabs):
+
+<Quote
+    imageSource="/images/customers/elevenlabs-sam.jpg"
+    size="sm"
+    name="Sam Sklar"
+    title="Growth engineer, ElevenLabs"
+    quote={`“We use basically everything in PostHog to understand more about our users and to plan new launches. We have an onboarding survey which is the first thing you see when you sign up.”`}
+/>
+
+***
+
+[Octomind](/customers/octomind):
+
+<Quote
+    imageSource="/images/customers/maria_octomind.jpg"
+    size="sm"
+    name="Maria Zahorcova"
+    title="Chief Marketing Officer, Octomind"
+    quote={`“We’re product-led and it’s really, really important that we keep an eye not only on marketing activities but also the experience beyond that. It was great when I found out I could use PostHog to track data across the site, the docs, and the product — I just had to speak to our engineers about implementing it.”`}
+/>
+
+***
+
+## Advantages for everyone
+
+PostHog is one login and one bill.
+
+That means less headache for more power, with all your data available across a range of products that help you understand user behavior as it happens.
+
+You'll get a responsive team that cares about user needs, delivering improvements and customer requests constantly.
+
+PostHog is completely agnostic to the language, framework and stack you build your product with. You can adopt it incrementally, adding more as needed.
+
+Best of all, PostHog is modern, fast, and built so that you’ll actually enjoy using it.
+
+***
+
+## Persuading product teams
+
+PostHog gives product teams the power to understand users, improve adoption and test assumptions. Your product teammates can get dive in immediately without having to wait for engineers to write new code or hook up an integration.
+
+**[Report anything](/docs/product-analytics/insights)** with charts, trend reporting and [dashboards](/docs/product-analytics/dashboards) that are easy to build, but also deeply customizable for SQL enthusiasts.
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: daniloc
body: nice
created_at: 2025-04-09T18:08:44Z
author_association: CONTRIBUTOR
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: daniloc
body: That should improve the skimmability, let me try that
created_at: 2025-04-09T18:10:44Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,118 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and one easy integration gets you everything you need to build great products.
+
+But convincing your teammates to switch horses later in a product's life can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+## Sharing social proof
+
+We’ve published [customer stories](/customers) with loads of companies who have loved their switch to PostHog. If you want to share a bit of social proof, these are a great place to start. Here are some choice quotes.
+
+***
+
+[ElevenLabs](/customers/elevenlabs):
+
+<Quote
+    imageSource="/images/customers/elevenlabs-sam.jpg"
+    size="sm"
+    name="Sam Sklar"
+    title="Growth engineer, ElevenLabs"
+    quote={`“We use basically everything in PostHog to understand more about our users and to plan new launches. We have an onboarding survey which is the first thing you see when you sign up.”`}
+/>
+
+***
+
+[Octomind](/customers/octomind):
+
+<Quote
+    imageSource="/images/customers/maria_octomind.jpg"
+    size="sm"
+    name="Maria Zahorcova"
+    title="Chief Marketing Officer, Octomind"
+    quote={`“We’re product-led and it’s really, really important that we keep an eye not only on marketing activities but also the experience beyond that. It was great when I found out I could use PostHog to track data across the site, the docs, and the product — I just had to speak to our engineers about implementing it.”`}
+/>
+
+***
+
+## Advantages for everyone
+
+PostHog is one login and one bill.
+
+That means less headache for more power, with all your data available across a range of products that help you understand user behavior as it happens.
+
+You'll get a responsive team that cares about user needs, delivering improvements and customer requests constantly.
+
+PostHog is completely agnostic to the language, framework and stack you build your product with. You can adopt it incrementally, adding more as needed.
+
+Best of all, PostHog is modern, fast, and built so that you’ll actually enjoy using it.
+
+***
+
+## Persuading product teams
+
+PostHog gives product teams the power to understand users, improve adoption and test assumptions. Your product teammates can get dive in immediately without having to wait for engineers to write new code or hook up an integration.
+
+**[Report anything](/docs/product-analytics/insights)** with charts, trend reporting and [dashboards](/docs/product-analytics/dashboards) that are easy to build, but also deeply customizable for SQL enthusiasts.
+
+**Learn anything you want** about everything the user touches in the product with [autocapture](/docs/product-analytics/autocapture).
+
+**Get clarity about navigation** and user priorities with [heatmaps](/docs/toolbar/heatmaps).
+
+Use [session replay](/docs/session-replay/installation) to **reveal bugs, expose friction, and help instantly answer questions** like “is this new design working?”
+
+**Send events and other details to any other tool**, powering automations and keeping data in sync, with setup you can accomplish in seconds, fully customizable for any API or webhook. [Data pipelines](/docs/cdp) makes it easy.
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: daniloc
body: Apparently it comes up a lot, this was specifically suggested in the doc
created_at: 2025-04-09T18:18:23Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,118 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and one easy integration gets you everything you need to build great products.
+
+But convincing your teammates to switch horses later in a product's life can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+## Sharing social proof
+
+We’ve published [customer stories](/customers) with loads of companies who have loved their switch to PostHog. If you want to share a bit of social proof, these are a great place to start. Here are some choice quotes.
+
+***
+
+[ElevenLabs](/customers/elevenlabs):
+
+<Quote
+    imageSource="/images/customers/elevenlabs-sam.jpg"
+    size="sm"
+    name="Sam Sklar"
+    title="Growth engineer, ElevenLabs"
+    quote={`“We use basically everything in PostHog to understand more about our users and to plan new launches. We have an onboarding survey which is the first thing you see when you sign up.”`}
+/>
+
+***
+
+[Octomind](/customers/octomind):
+
+<Quote
+    imageSource="/images/customers/maria_octomind.jpg"
+    size="sm"
+    name="Maria Zahorcova"
+    title="Chief Marketing Officer, Octomind"
+    quote={`“We’re product-led and it’s really, really important that we keep an eye not only on marketing activities but also the experience beyond that. It was great when I found out I could use PostHog to track data across the site, the docs, and the product — I just had to speak to our engineers about implementing it.”`}
+/>
+
+***
+
+## Advantages for everyone
+
+PostHog is one login and one bill.
+
+That means less headache for more power, with all your data available across a range of products that help you understand user behavior as it happens.
+
+You'll get a responsive team that cares about user needs, delivering improvements and customer requests constantly.
+
+PostHog is completely agnostic to the language, framework and stack you build your product with. You can adopt it incrementally, adding more as needed.
+
+Best of all, PostHog is modern, fast, and built so that you’ll actually enjoy using it.
+
+***
+
+## Persuading product teams
+
+PostHog gives product teams the power to understand users, improve adoption and test assumptions. Your product teammates can get dive in immediately without having to wait for engineers to write new code or hook up an integration.
+
+**[Report anything](/docs/product-analytics/insights)** with charts, trend reporting and [dashboards](/docs/product-analytics/dashboards) that are easy to build, but also deeply customizable for SQL enthusiasts.
+
+**Learn anything you want** about everything the user touches in the product with [autocapture](/docs/product-analytics/autocapture).
+
+**Get clarity about navigation** and user priorities with [heatmaps](/docs/toolbar/heatmaps).
+
+Use [session replay](/docs/session-replay/installation) to **reveal bugs, expose friction, and help instantly answer questions** like “is this new design working?”
+
+**Send events and other details to any other tool**, powering automations and keeping data in sync, with setup you can accomplish in seconds, fully customizable for any API or webhook. [Data pipelines](/docs/cdp) makes it easy.
+
+**Gather feedback** from exactly the users you want to reach with no-code [surveys](/docs/surveys/creating-surveys) that launch instantly.
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: daniloc
body: HOT
created_at: 2025-04-09T18:20:28Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,118 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and one easy integration gets you everything you need to build great products.
+
+But convincing your teammates to switch horses later in a product's life can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+## Sharing social proof
+
+We’ve published [customer stories](/customers) with loads of companies who have loved their switch to PostHog. If you want to share a bit of social proof, these are a great place to start. Here are some choice quotes.
+
+***
+
+[ElevenLabs](/customers/elevenlabs):
+
+<Quote
+    imageSource="/images/customers/elevenlabs-sam.jpg"
+    size="sm"
+    name="Sam Sklar"
+    title="Growth engineer, ElevenLabs"
+    quote={`“We use basically everything in PostHog to understand more about our users and to plan new launches. We have an onboarding survey which is the first thing you see when you sign up.”`}
+/>
+
+***
+
+[Octomind](/customers/octomind):
+
+<Quote
+    imageSource="/images/customers/maria_octomind.jpg"
+    size="sm"
+    name="Maria Zahorcova"
+    title="Chief Marketing Officer, Octomind"
+    quote={`“We’re product-led and it’s really, really important that we keep an eye not only on marketing activities but also the experience beyond that. It was great when I found out I could use PostHog to track data across the site, the docs, and the product — I just had to speak to our engineers about implementing it.”`}
+/>
+
+***
+
+## Advantages for everyone
+
+PostHog is one login and one bill.
+
+That means less headache for more power, with all your data available across a range of products that help you understand user behavior as it happens.
+
+You'll get a responsive team that cares about user needs, delivering improvements and customer requests constantly.
+
+PostHog is completely agnostic to the language, framework and stack you build your product with. You can adopt it incrementally, adding more as needed.
+
+Best of all, PostHog is modern, fast, and built so that you’ll actually enjoy using it.
+
+***
+
+## Persuading product teams
+
+PostHog gives product teams the power to understand users, improve adoption and test assumptions. Your product teammates can get dive in immediately without having to wait for engineers to write new code or hook up an integration.
+
+**[Report anything](/docs/product-analytics/insights)** with charts, trend reporting and [dashboards](/docs/product-analytics/dashboards) that are easy to build, but also deeply customizable for SQL enthusiasts.
+
+**Learn anything you want** about everything the user touches in the product with [autocapture](/docs/product-analytics/autocapture).
+
+**Get clarity about navigation** and user priorities with [heatmaps](/docs/toolbar/heatmaps).
+
+Use [session replay](/docs/session-replay/installation) to **reveal bugs, expose friction, and help instantly answer questions** like “is this new design working?”
+
+**Send events and other details to any other tool**, powering automations and keeping data in sync, with setup you can accomplish in seconds, fully customizable for any API or webhook. [Data pipelines](/docs/cdp) makes it easy.
+
+**Gather feedback** from exactly the users you want to reach with no-code [surveys](/docs/surveys/creating-surveys) that launch instantly.
+
+**Integrate revenue data** from [Stripe](/docs/cdp/sources/stripe) and other sources using data warehouse, so you can get a clear picture of what changes really move the needle.
+
+**Get unblocked by PostHog’s helpful sales and support teams,** ensuring you get the insights and information you need quickly.
+
+***
+
+## Good news for engineering teams
+
+PostHog is designed for developers. We’ve got a dedicated technical staff standing by to help keep you on track. When you reach out to support, you’ll be talking to someone who knows the technical details of the product really well.
+
+While other products are low-velocity black boxes, we’re constantly making PostHog better.
+
+The project is [developed in the open](https://github.com/PostHog/posthog), with a [public roadmap](/roadmap) and [dozens of pull requests landing](https://github.com/PostHog/posthog/pulls?q=is%3Apr+is%3Aclosed) each week.
+
+Giving other teams the data they want becomes much easier with PostHog in the mix, with lower friction for engineering, and loads of features everyone can use without complex setup.
+
+**Consolidate the tools your company needs**, with one login, one integration, one bill, and one [deep set of docs](/docs).
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: daniloc
body: reasonable
created_at: 2025-04-09T18:22:03Z
author_association: CONTRIBUTOR
diff_hunk: @@ -2109,6 +2109,21 @@ export const docsMenu = {
                     url: '/docs/new-to-posthog/revenue',
                     icon: 'IconHandMoney',
                 },
+                {
+                    name: 'Switching to PostHog',
+                    url: '/docs/new-to-posthog/switch-guide/switching-to-posthog',
path: src/navs/index.js
user: login: daniloc
body: Yeah, I don't hate it

<img width="309" alt="Screenshot 2025-04-09 at 2 29 56 PM" src="https://github.com/user-attachments/assets/ddd72108-f610-4d91-9430-156e0d83ebba" />

created_at: 2025-04-09T18:30:26Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,118 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and one easy integration gets you everything you need to build great products.
+
+But convincing your teammates to switch horses later in a product's life can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+## Sharing social proof
+
+We’ve published [customer stories](/customers) with loads of companies who have loved their switch to PostHog. If you want to share a bit of social proof, these are a great place to start. Here are some choice quotes.
+
+***
+
+[ElevenLabs](/customers/elevenlabs):
+
+<Quote
+    imageSource="/images/customers/elevenlabs-sam.jpg"
+    size="sm"
+    name="Sam Sklar"
+    title="Growth engineer, ElevenLabs"
+    quote={`“We use basically everything in PostHog to understand more about our users and to plan new launches. We have an onboarding survey which is the first thing you see when you sign up.”`}
+/>
+
+***
+
+[Octomind](/customers/octomind):
+
+<Quote
+    imageSource="/images/customers/maria_octomind.jpg"
+    size="sm"
+    name="Maria Zahorcova"
+    title="Chief Marketing Officer, Octomind"
+    quote={`“We’re product-led and it’s really, really important that we keep an eye not only on marketing activities but also the experience beyond that. It was great when I found out I could use PostHog to track data across the site, the docs, and the product — I just had to speak to our engineers about implementing it.”`}
+/>
+
+***
+
+## Advantages for everyone
+
+PostHog is one login and one bill.
+
+That means less headache for more power, with all your data available across a range of products that help you understand user behavior as it happens.
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: daniloc
body: I think if I say "this" instead of "that" it will parse better (first line really needs to stand alone), lmk how that lands
created_at: 2025-04-09T18:35:34Z
author_association: CONTRIBUTOR
diff_hunk: @@ -2109,6 +2109,24 @@ export const docsMenu = {
                     url: '/docs/new-to-posthog/revenue',
                     icon: 'IconHandMoney',
                 },
+                {
+                    name: 'Switching to PostHog',
+                    icon: 'IconLeave',
path: src/navs/index.js
user: login: ivanagas
body: You can still do this and it will redirect to the child
```suggestion
                    icon: 'IconLeave',
                    url: '/docs/new-to-posthog/switch-guide/switching-to-posthog'
```
created_at: 2025-04-09T18:47:25Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,132 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and simple integration gets you everything you need to build great products.
+
+But if you're already leaning on another tool, switching can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+***
+
+## Advantages for everyone
+
+PostHog is one login and one bill.
+
+This means less headache for more power, with all your data available across a range of products that help you understand user behavior as it happens.
+
+You'll get a responsive team that cares about user needs, delivering improvements, and customer requests constantly.
+
+PostHog is completely agnostic to the language, framework, and stack you build your product with. You can adopt it incrementally, adding new functionality as needed.
+
+Best of all, PostHog is modern, constantly improving, and built so that you’ll actually enjoy using it.
+
+***
+
+## Persuading product teams
+
+PostHog gives product teams the power to understand users, improve adoption, and test assumptions. Your product teammates can dive in immediately without having to wait for engineers to write new code or hook up an integration.
+
+- **[Visualize anything](/docs/product-analytics/insights)** with charts, trend reporting, and [dashboards](/docs/product-analytics/dashboards) that are easy to build, but also deeply customizable for SQL enthusiasts.
+
+- **Learn anything you want** about everything the user touches in the product without manual instrumentation with [autocapture](/docs/product-analytics/autocapture).
+
+- **Get clarity about navigation** and user priorities with [heatmaps](/docs/toolbar/heatmaps).
+
+- Use [session replay](/docs/session-replay/installation) to **reveal bugs, expose friction, and help instantly answer questions** like “is this new design working?”
+
+- **Integrate revenue data** from [Stripe](/docs/cdp/sources/stripe) and other sources using data warehouse, so you can get a clear picture of what changes really move the needle.
+
+- **Send events and other details to any other tool**, powering automations and keeping data in sync, with setup you can accomplish in seconds, fully customizable for any API or webhook. [Data pipelines](/docs/cdp) makes it easy.
+
+- **Gather feedback and book user interviews** from exactly the users you want to reach with no-code [surveys](/docs/surveys/creating-surveys) that launch instantly.
+
+- **Get unblocked by PostHog’s helpful sales and support teams,** ensuring you get the insights and information you need quickly.
+
+***
+
+## Good news for engineering teams
+
+PostHog is designed for developers.
+
+The project is [developed in the open](https://github.com/PostHog/posthog), with a [public roadmap](/roadmap) and [dozens of pull requests landing](https://github.com/PostHog/posthog/pulls?q=is%3Apr+is%3Aclosed) each week. While other products are low-velocity black boxes, we’re constantly making PostHog better.
+
+ We’ve got a dedicated technical staff standing by to help keep you on track. When you reach out to support, you’ll be talking to someone who knows the technical details of the product really well.
+
+Giving other teams the data they want becomes much easier with PostHog in the mix, lowering the burden on engineering. Once a basic integration is in place, there are loads of features everyone can use without a developer's intervention.
+
+- **Consolidate the tools your company needs**, with one login, one integration, one bill.
+
+- **[Get comprehensive documentation](/docs)** developers love for every every stack, framework, and language.
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: ivanagas
body: ```suggestion
- **[Get comprehensive documentation](/docs)** developers love for every every stack, framework, and language. You can also view [our source code directly](http://github.com/postHog/) if you can't find what you need. 
```
created_at: 2025-04-09T18:51:23Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,132 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and simple integration gets you everything you need to build great products.
+
+But if you're already leaning on another tool, switching can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+***
+
+## Advantages for everyone
+
+PostHog is one login and one bill.
+
+This means less headache for more power, with all your data available across a range of products that help you understand user behavior as it happens.
+
+You'll get a responsive team that cares about user needs, delivering improvements, and customer requests constantly.
+
+PostHog is completely agnostic to the language, framework, and stack you build your product with. You can adopt it incrementally, adding new functionality as needed.
+
+Best of all, PostHog is modern, constantly improving, and built so that you’ll actually enjoy using it.
+
+***
+
+## Persuading product teams
+
+PostHog gives product teams the power to understand users, improve adoption, and test assumptions. Your product teammates can dive in immediately without having to wait for engineers to write new code or hook up an integration.
+
+- **[Visualize anything](/docs/product-analytics/insights)** with charts, trend reporting, and [dashboards](/docs/product-analytics/dashboards) that are easy to build, but also deeply customizable for SQL enthusiasts.
+
+- **Learn anything you want** about everything the user touches in the product without manual instrumentation with [autocapture](/docs/product-analytics/autocapture).
+
+- **Get clarity about navigation** and user priorities with [heatmaps](/docs/toolbar/heatmaps).
+
+- Use [session replay](/docs/session-replay/installation) to **reveal bugs, expose friction, and help instantly answer questions** like “is this new design working?”
+
+- **Integrate revenue data** from [Stripe](/docs/cdp/sources/stripe) and other sources using data warehouse, so you can get a clear picture of what changes really move the needle.
+
+- **Send events and other details to any other tool**, powering automations and keeping data in sync, with setup you can accomplish in seconds, fully customizable for any API or webhook. [Data pipelines](/docs/cdp) makes it easy.
+
+- **Gather feedback and book user interviews** from exactly the users you want to reach with no-code [surveys](/docs/surveys/creating-surveys) that launch instantly.
+
+- **Get unblocked by PostHog’s helpful sales and support teams,** ensuring you get the insights and information you need quickly.
+
+***
+
+## Good news for engineering teams
+
+PostHog is designed for developers.
+
+The project is [developed in the open](https://github.com/PostHog/posthog), with a [public roadmap](/roadmap) and [dozens of pull requests landing](https://github.com/PostHog/posthog/pulls?q=is%3Apr+is%3Aclosed) each week. While other products are low-velocity black boxes, we’re constantly making PostHog better.
+
+ We’ve got a dedicated technical staff standing by to help keep you on track. When you reach out to support, you’ll be talking to someone who knows the technical details of the product really well.
+
+Giving other teams the data they want becomes much easier with PostHog in the mix, lowering the burden on engineering. Once a basic integration is in place, there are loads of features everyone can use without a developer's intervention.
+
+- **Consolidate the tools your company needs**, with one login, one integration, one bill.
+
+- **[Get comprehensive documentation](/docs)** developers love for every every stack, framework, and language.
+
+- **Get a data platform that encourages tinkering**: if something doesn’t fit quite right for your team, it’s easy to customize everything from visualizations to integrations with other services. We'll host all these customizations for you. You don't need to worry about infrastructure or uptime.
+
+- **Integrating PostHog with other tools or even your own services is easy**, thanks to [data pipelines](/docs/cdp).
+
+- **Roll features out gradually** using [feature flags](/docs/feature-flags/creating-feature-flags) that are easy to target with fine-grained queries across everything PostHog knows about your users.
+
+We also care about the technical details of switching over. No matter your stack or existing tools, **complete integration and [migration docs](/docs/migration)** mean a clear path instead of a puzzle to solve. Our experienced Sales and CS team can even provide backup for more complex cases.
+
+***
+
+## Make the case to executives
+
+We’re in this for a long-term relationship, so **PostHog wants you to spend as little money as possible**. Our sales team actually works with customers to reduce bills and optimize consumption. Instead of sneaky billing, we’d prefer to make more money as a result of you winning more business.
+
+There’s just no sneaky stuff going on here. You can get started immediately with no shenanigans, no calls with the sales team.
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: ivanagas
body: ```suggestion
There’s just no sneaky stuff going on here. You can get started immediately with no shenanigans, no calls with the sales team if you don't want them.
```
created_at: 2025-04-09T18:52:35Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,132 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and simple integration gets you everything you need to build great products.
+
+But if you're already leaning on another tool, switching can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+***
+
+## Advantages for everyone
+
+PostHog is one login and one bill.
+
+This means less headache for more power, with all your data available across a range of products that help you understand user behavior as it happens.
+
+You'll get a responsive team that cares about user needs, delivering improvements, and customer requests constantly.
+
+PostHog is completely agnostic to the language, framework, and stack you build your product with. You can adopt it incrementally, adding new functionality as needed.
+
+Best of all, PostHog is modern, constantly improving, and built so that you’ll actually enjoy using it.
+
+***
+
+## Persuading product teams
+
+PostHog gives product teams the power to understand users, improve adoption, and test assumptions. Your product teammates can dive in immediately without having to wait for engineers to write new code or hook up an integration.
+
+- **[Visualize anything](/docs/product-analytics/insights)** with charts, trend reporting, and [dashboards](/docs/product-analytics/dashboards) that are easy to build, but also deeply customizable for SQL enthusiasts.
+
+- **Learn anything you want** about everything the user touches in the product without manual instrumentation with [autocapture](/docs/product-analytics/autocapture).
+
+- **Get clarity about navigation** and user priorities with [heatmaps](/docs/toolbar/heatmaps).
+
+- Use [session replay](/docs/session-replay/installation) to **reveal bugs, expose friction, and help instantly answer questions** like “is this new design working?”
+
+- **Integrate revenue data** from [Stripe](/docs/cdp/sources/stripe) and other sources using data warehouse, so you can get a clear picture of what changes really move the needle.
+
+- **Send events and other details to any other tool**, powering automations and keeping data in sync, with setup you can accomplish in seconds, fully customizable for any API or webhook. [Data pipelines](/docs/cdp) makes it easy.
+
+- **Gather feedback and book user interviews** from exactly the users you want to reach with no-code [surveys](/docs/surveys/creating-surveys) that launch instantly.
+
+- **Get unblocked by PostHog’s helpful sales and support teams,** ensuring you get the insights and information you need quickly.
+
+***
+
+## Good news for engineering teams
+
+PostHog is designed for developers.
+
+The project is [developed in the open](https://github.com/PostHog/posthog), with a [public roadmap](/roadmap) and [dozens of pull requests landing](https://github.com/PostHog/posthog/pulls?q=is%3Apr+is%3Aclosed) each week. While other products are low-velocity black boxes, we’re constantly making PostHog better.
+
+ We’ve got a dedicated technical staff standing by to help keep you on track. When you reach out to support, you’ll be talking to someone who knows the technical details of the product really well.
+
+Giving other teams the data they want becomes much easier with PostHog in the mix, lowering the burden on engineering. Once a basic integration is in place, there are loads of features everyone can use without a developer's intervention.
+
+- **Consolidate the tools your company needs**, with one login, one integration, one bill.
+
+- **[Get comprehensive documentation](/docs)** developers love for every every stack, framework, and language.
+
+- **Get a data platform that encourages tinkering**: if something doesn’t fit quite right for your team, it’s easy to customize everything from visualizations to integrations with other services. We'll host all these customizations for you. You don't need to worry about infrastructure or uptime.
+
+- **Integrating PostHog with other tools or even your own services is easy**, thanks to [data pipelines](/docs/cdp).
+
+- **Roll features out gradually** using [feature flags](/docs/feature-flags/creating-feature-flags) that are easy to target with fine-grained queries across everything PostHog knows about your users.
+
+We also care about the technical details of switching over. No matter your stack or existing tools, **complete integration and [migration docs](/docs/migration)** mean a clear path instead of a puzzle to solve. Our experienced Sales and CS team can even provide backup for more complex cases.
+
+***
+
+## Make the case to executives
+
+We’re in this for a long-term relationship, so **PostHog wants you to spend as little money as possible**. Our sales team actually works with customers to reduce bills and optimize consumption. Instead of sneaky billing, we’d prefer to make more money as a result of you winning more business.
+
+There’s just no sneaky stuff going on here. You can get started immediately with no shenanigans, no calls with the sales team.
+
+- **Your team will like PostHog**. It’s fresh, always getting fixes, improvements and additional power. An investment in PostHog today means even more capabilities by next year.
+
+- **There's no per-seat charge**, so PostHog makes it easy for everyone on your team to make data-driven decisions. No matter how quickly you scale your team, your costs remain fixed to the actual usage of your product. 
+
+- **PostHog’s sales process is transparent and so is the whole company**: the company [handbook is public](/handbook), *even documenting the ways we can offer [discounts](/handbook/growth/sales/billing#coupons-and-discounts)*. Everything you want to know about pricing, processes and our product is publicly documented.
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: ivanagas
body: ```suggestion
- **PostHog’s sales process is transparent and so is the whole company**: the company [handbook is public](/handbook), *even documenting the ways we can offer [discounts](/handbook/growth/sales/billing#coupons-and-discounts)*. Everything you want to know about pricing, processes, and our product is publicly documented.
```
created_at: 2025-04-09T18:53:02Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,132 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and simple integration gets you everything you need to build great products.
+
+But if you're already leaning on another tool, switching can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+***
+
+## Advantages for everyone
+
+PostHog is one login and one bill.
+
+This means less headache for more power, with all your data available across a range of products that help you understand user behavior as it happens.
+
+You'll get a responsive team that cares about user needs, delivering improvements, and customer requests constantly.
+
+PostHog is completely agnostic to the language, framework, and stack you build your product with. You can adopt it incrementally, adding new functionality as needed.
+
+Best of all, PostHog is modern, constantly improving, and built so that you’ll actually enjoy using it.
+
+***
+
+## Persuading product teams
+
+PostHog gives product teams the power to understand users, improve adoption, and test assumptions. Your product teammates can dive in immediately without having to wait for engineers to write new code or hook up an integration.
+
+- **[Visualize anything](/docs/product-analytics/insights)** with charts, trend reporting, and [dashboards](/docs/product-analytics/dashboards) that are easy to build, but also deeply customizable for SQL enthusiasts.
+
+- **Learn anything you want** about everything the user touches in the product without manual instrumentation with [autocapture](/docs/product-analytics/autocapture).
+
+- **Get clarity about navigation** and user priorities with [heatmaps](/docs/toolbar/heatmaps).
+
+- Use [session replay](/docs/session-replay/installation) to **reveal bugs, expose friction, and help instantly answer questions** like “is this new design working?”
+
+- **Integrate revenue data** from [Stripe](/docs/cdp/sources/stripe) and other sources using data warehouse, so you can get a clear picture of what changes really move the needle.
+
+- **Send events and other details to any other tool**, powering automations and keeping data in sync, with setup you can accomplish in seconds, fully customizable for any API or webhook. [Data pipelines](/docs/cdp) makes it easy.
+
+- **Gather feedback and book user interviews** from exactly the users you want to reach with no-code [surveys](/docs/surveys/creating-surveys) that launch instantly.
+
+- **Get unblocked by PostHog’s helpful sales and support teams,** ensuring you get the insights and information you need quickly.
+
+***
+
+## Good news for engineering teams
+
+PostHog is designed for developers.
+
+The project is [developed in the open](https://github.com/PostHog/posthog), with a [public roadmap](/roadmap) and [dozens of pull requests landing](https://github.com/PostHog/posthog/pulls?q=is%3Apr+is%3Aclosed) each week. While other products are low-velocity black boxes, we’re constantly making PostHog better.
+
+ We’ve got a dedicated technical staff standing by to help keep you on track. When you reach out to support, you’ll be talking to someone who knows the technical details of the product really well.
+
+Giving other teams the data they want becomes much easier with PostHog in the mix, lowering the burden on engineering. Once a basic integration is in place, there are loads of features everyone can use without a developer's intervention.
+
+- **Consolidate the tools your company needs**, with one login, one integration, one bill.
+
+- **[Get comprehensive documentation](/docs)** developers love for every every stack, framework, and language.
+
+- **Get a data platform that encourages tinkering**: if something doesn’t fit quite right for your team, it’s easy to customize everything from visualizations to integrations with other services. We'll host all these customizations for you. You don't need to worry about infrastructure or uptime.
+
+- **Integrating PostHog with other tools or even your own services is easy**, thanks to [data pipelines](/docs/cdp).
+
+- **Roll features out gradually** using [feature flags](/docs/feature-flags/creating-feature-flags) that are easy to target with fine-grained queries across everything PostHog knows about your users.
+
+We also care about the technical details of switching over. No matter your stack or existing tools, **complete integration and [migration docs](/docs/migration)** mean a clear path instead of a puzzle to solve. Our experienced Sales and CS team can even provide backup for more complex cases.
+
+***
+
+## Make the case to executives
+
+We’re in this for a long-term relationship, so **PostHog wants you to spend as little money as possible**. Our sales team actually works with customers to reduce bills and optimize consumption. Instead of sneaky billing, we’d prefer to make more money as a result of you winning more business.
+
+There’s just no sneaky stuff going on here. You can get started immediately with no shenanigans, no calls with the sales team.
+
+- **Your team will like PostHog**. It’s fresh, always getting fixes, improvements and additional power. An investment in PostHog today means even more capabilities by next year.
+
+- **There's no per-seat charge**, so PostHog makes it easy for everyone on your team to make data-driven decisions. No matter how quickly you scale your team, your costs remain fixed to the actual usage of your product. 
+
+- **PostHog’s sales process is transparent and so is the whole company**: the company [handbook is public](/handbook), *even documenting the ways we can offer [discounts](/handbook/growth/sales/billing#coupons-and-discounts)*. Everything you want to know about pricing, processes and our product is publicly documented.
+
+- **You can have a free trial** to fully vet the costs and impact of your integration. Trying PostHog is low-risk, no cost, and fully reversible.
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: ivanagas
body: Who is this true for? Big customers or only those under our free plan?
created_at: 2025-04-09T18:53:20Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,132 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and simple integration gets you everything you need to build great products.
+
+But if you're already leaning on another tool, switching can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+***
+
+## Advantages for everyone
+
+PostHog is one login and one bill.
+
+This means less headache for more power, with all your data available across a range of products that help you understand user behavior as it happens.
+
+You'll get a responsive team that cares about user needs, delivering improvements, and customer requests constantly.
+
+PostHog is completely agnostic to the language, framework, and stack you build your product with. You can adopt it incrementally, adding new functionality as needed.
+
+Best of all, PostHog is modern, constantly improving, and built so that you’ll actually enjoy using it.
+
+***
+
+## Persuading product teams
+
+PostHog gives product teams the power to understand users, improve adoption, and test assumptions. Your product teammates can dive in immediately without having to wait for engineers to write new code or hook up an integration.
+
+- **[Visualize anything](/docs/product-analytics/insights)** with charts, trend reporting, and [dashboards](/docs/product-analytics/dashboards) that are easy to build, but also deeply customizable for SQL enthusiasts.
+
+- **Learn anything you want** about everything the user touches in the product without manual instrumentation with [autocapture](/docs/product-analytics/autocapture).
+
+- **Get clarity about navigation** and user priorities with [heatmaps](/docs/toolbar/heatmaps).
+
+- Use [session replay](/docs/session-replay/installation) to **reveal bugs, expose friction, and help instantly answer questions** like “is this new design working?”
+
+- **Integrate revenue data** from [Stripe](/docs/cdp/sources/stripe) and other sources using data warehouse, so you can get a clear picture of what changes really move the needle.
+
+- **Send events and other details to any other tool**, powering automations and keeping data in sync, with setup you can accomplish in seconds, fully customizable for any API or webhook. [Data pipelines](/docs/cdp) makes it easy.
+
+- **Gather feedback and book user interviews** from exactly the users you want to reach with no-code [surveys](/docs/surveys/creating-surveys) that launch instantly.
+
+- **Get unblocked by PostHog’s helpful sales and support teams,** ensuring you get the insights and information you need quickly.
+
+***
+
+## Good news for engineering teams
+
+PostHog is designed for developers.
+
+The project is [developed in the open](https://github.com/PostHog/posthog), with a [public roadmap](/roadmap) and [dozens of pull requests landing](https://github.com/PostHog/posthog/pulls?q=is%3Apr+is%3Aclosed) each week. While other products are low-velocity black boxes, we’re constantly making PostHog better.
+
+ We’ve got a dedicated technical staff standing by to help keep you on track. When you reach out to support, you’ll be talking to someone who knows the technical details of the product really well.
+
+Giving other teams the data they want becomes much easier with PostHog in the mix, lowering the burden on engineering. Once a basic integration is in place, there are loads of features everyone can use without a developer's intervention.
+
+- **Consolidate the tools your company needs**, with one login, one integration, one bill.
+
+- **[Get comprehensive documentation](/docs)** developers love for every every stack, framework, and language.
+
+- **Get a data platform that encourages tinkering**: if something doesn’t fit quite right for your team, it’s easy to customize everything from visualizations to integrations with other services. We'll host all these customizations for you. You don't need to worry about infrastructure or uptime.
+
+- **Integrating PostHog with other tools or even your own services is easy**, thanks to [data pipelines](/docs/cdp).
+
+- **Roll features out gradually** using [feature flags](/docs/feature-flags/creating-feature-flags) that are easy to target with fine-grained queries across everything PostHog knows about your users.
+
+We also care about the technical details of switching over. No matter your stack or existing tools, **complete integration and [migration docs](/docs/migration)** mean a clear path instead of a puzzle to solve. Our experienced Sales and CS team can even provide backup for more complex cases.
+
+***
+
+## Make the case to executives
+
+We’re in this for a long-term relationship, so **PostHog wants you to spend as little money as possible**. Our sales team actually works with customers to reduce bills and optimize consumption. Instead of sneaky billing, we’d prefer to make more money as a result of you winning more business.
+
+There’s just no sneaky stuff going on here. You can get started immediately with no shenanigans, no calls with the sales team.
+
+- **Your team will like PostHog**. It’s fresh, always getting fixes, improvements and additional power. An investment in PostHog today means even more capabilities by next year.
+
+- **There's no per-seat charge**, so PostHog makes it easy for everyone on your team to make data-driven decisions. No matter how quickly you scale your team, your costs remain fixed to the actual usage of your product. 
+
+- **PostHog’s sales process is transparent and so is the whole company**: the company [handbook is public](/handbook), *even documenting the ways we can offer [discounts](/handbook/growth/sales/billing#coupons-and-discounts)*. Everything you want to know about pricing, processes and our product is publicly documented.
+
+- **You can have a free trial** to fully vet the costs and impact of your integration. Trying PostHog is low-risk, no cost, and fully reversible.
+
+- **PostHog doesn’t require a contract**. You can save a bit of money with one, but it’s not a gate to getting started and trying things out.
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: ivanagas
body: ```suggestion
- **PostHog doesn’t require a contract**. You can save money with one, but it’s not a blocker to trying things out.
```
created_at: 2025-04-09T18:54:29Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,67 @@
+---
+title: Planning your pilot
+nextPage: ./migration-planning.mdx
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+We want you to love using PostHog. We’ve worked hard to craft a tool that can make you much more effective at giving your customers what they want.
+
+To get the most out of this, a little planning goes a long way. Here’s what you can do to make the most of a pilot.
path: contents/docs/new-to-posthog/switch-guide/planning-your-pilot.mdx
user: login: ivanagas
body: We can drop the cliche :)
```suggestion
To get the most out of this, here's what we suggest for making the most of a pilot.
```
created_at: 2025-04-09T18:55:33Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,67 @@
+---
+title: Planning your pilot
+nextPage: ./migration-planning.mdx
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+We want you to love using PostHog. We’ve worked hard to craft a tool that can make you much more effective at giving your customers what they want.
+
+To get the most out of this, a little planning goes a long way. Here’s what you can do to make the most of a pilot.
+
+## List out the people who care about user behavior, no matter their role
path: contents/docs/new-to-posthog/switch-guide/planning-your-pilot.mdx
user: login: ivanagas
body: This depends on what stage we expect people to be in here. 

If already signed up, we should make this more active. 
```suggestion
## Invite the people who care about user behavior, no matter their role
```
created_at: 2025-04-09T18:56:22Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,67 @@
+---
+title: Planning your pilot
+nextPage: ./migration-planning.mdx
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+We want you to love using PostHog. We’ve worked hard to craft a tool that can make you much more effective at giving your customers what they want.
+
+To get the most out of this, a little planning goes a long way. Here’s what you can do to make the most of a pilot.
+
+## List out the people who care about user behavior, no matter their role
+
+PostHog charges by how successful your product is, not how many people have a login.
+
+That means anyone and everyone on your crew can explore at no extra cost. As your integration comes online, think about who else you’d like to invite. You'll have the option to invite them during setup, and any time after that.
+
+## Get help if you want it
+
+For companies sized 25 and up, [we’ve got a team](/talk-to-a-human) who can answer questions and help you make a plan. But only if you want the help! They’re not going to pressure you or do anything corny, but their integration experience can save time and help you plan. They can also help you map PostHog features to your business goals and develop a mental model for using all our products.
path: contents/docs/new-to-posthog/switch-guide/planning-your-pilot.mdx
user: login: ivanagas
body: ```suggestion
For companies sized 25 and up, [we’ve got a team](/talk-to-a-human) who can answer questions and help you make a plan. 

But only if you want the help! They’re not going to pressure you or do anything corny, but their integration experience can save time and help you plan. They can also help you map PostHog features to your business goals and develop a mental model for using all our products.
```
created_at: 2025-04-09T18:57:56Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,67 @@
+---
+title: Planning your pilot
+nextPage: ./migration-planning.mdx
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+We want you to love using PostHog. We’ve worked hard to craft a tool that can make you much more effective at giving your customers what they want.
+
+To get the most out of this, a little planning goes a long way. Here’s what you can do to make the most of a pilot.
+
+## List out the people who care about user behavior, no matter their role
+
+PostHog charges by how successful your product is, not how many people have a login.
+
+That means anyone and everyone on your crew can explore at no extra cost. As your integration comes online, think about who else you’d like to invite. You'll have the option to invite them during setup, and any time after that.
+
+## Get help if you want it
+
+For companies sized 25 and up, [we’ve got a team](/talk-to-a-human) who can answer questions and help you make a plan. But only if you want the help! They’re not going to pressure you or do anything corny, but their integration experience can save time and help you plan. They can also help you map PostHog features to your business goals and develop a mental model for using all our products.
+
+But we’re not going to get in your way, either, because…
+
+## We want you to play around
+
+The most important job is getting familiar with PostHog in whatever way makes you most comfortable. A basic integration is fast, and we’ve got loads of documentation to support your journey if you want to explore on your own.
path: contents/docs/new-to-posthog/switch-guide/planning-your-pilot.mdx
user: login: ivanagas
body: That last bit sort of repeats itself 

```suggestion
The most important job is getting familiar with PostHog in whatever way makes you most comfortable. The most basic integration takes 5 minutes and we’ve got loads of documentation to support you exploring on your own.
```
created_at: 2025-04-09T18:59:19Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,67 @@
+---
+title: Planning your pilot
+nextPage: ./migration-planning.mdx
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+We want you to love using PostHog. We’ve worked hard to craft a tool that can make you much more effective at giving your customers what they want.
+
+To get the most out of this, a little planning goes a long way. Here’s what you can do to make the most of a pilot.
+
+## List out the people who care about user behavior, no matter their role
+
+PostHog charges by how successful your product is, not how many people have a login.
+
+That means anyone and everyone on your crew can explore at no extra cost. As your integration comes online, think about who else you’d like to invite. You'll have the option to invite them during setup, and any time after that.
+
+## Get help if you want it
+
+For companies sized 25 and up, [we’ve got a team](/talk-to-a-human) who can answer questions and help you make a plan. But only if you want the help! They’re not going to pressure you or do anything corny, but their integration experience can save time and help you plan. They can also help you map PostHog features to your business goals and develop a mental model for using all our products.
+
+But we’re not going to get in your way, either, because…
+
+## We want you to play around
+
+The most important job is getting familiar with PostHog in whatever way makes you most comfortable. A basic integration is fast, and we’ve got loads of documentation to support your journey if you want to explore on your own.
+
+## First two weeks: get data in, then look at it
+
+Job one is making sure PostHog is reliably ingesting your data and reporting the basics in a dashboard. Once this is working, take a break, order a pizza[^1].
+
+From here, you can get more sophisticated:
+
+- **Decide**: Your [North Star metric](/docs/new-to-posthog/getting-hogpilled)  
+- **Decide**: Make an event tracking plan, or rely on autocapture?  
path: contents/docs/new-to-posthog/switch-guide/planning-your-pilot.mdx
user: login: ivanagas
body: Do we have a tracking plan guide?
created_at: 2025-04-09T19:02:33Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,67 @@
+---
+title: Planning your pilot
+nextPage: ./migration-planning.mdx
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+We want you to love using PostHog. We’ve worked hard to craft a tool that can make you much more effective at giving your customers what they want.
+
+To get the most out of this, a little planning goes a long way. Here’s what you can do to make the most of a pilot.
+
+## List out the people who care about user behavior, no matter their role
+
+PostHog charges by how successful your product is, not how many people have a login.
+
+That means anyone and everyone on your crew can explore at no extra cost. As your integration comes online, think about who else you’d like to invite. You'll have the option to invite them during setup, and any time after that.
+
+## Get help if you want it
+
+For companies sized 25 and up, [we’ve got a team](/talk-to-a-human) who can answer questions and help you make a plan. But only if you want the help! They’re not going to pressure you or do anything corny, but their integration experience can save time and help you plan. They can also help you map PostHog features to your business goals and develop a mental model for using all our products.
+
+But we’re not going to get in your way, either, because…
+
+## We want you to play around
+
+The most important job is getting familiar with PostHog in whatever way makes you most comfortable. A basic integration is fast, and we’ve got loads of documentation to support your journey if you want to explore on your own.
+
+## First two weeks: get data in, then look at it
+
+Job one is making sure PostHog is reliably ingesting your data and reporting the basics in a dashboard. Once this is working, take a break, order a pizza[^1].
+
+From here, you can get more sophisticated:
+
+- **Decide**: Your [North Star metric](/docs/new-to-posthog/getting-hogpilled)  
+- **Decide**: Make an event tracking plan, or rely on autocapture?  
+- **Decide**: Use [identified or anonymous events](/docs/data/anonymous-vs-identified-events)?  
+- Configure a [reverse proxy](/docs/advanced/proxy) to improve reliability of event capture  
+- Experiment with measuring [activation](/docs/new-to-posthog/activation) and [retention](/docs/new-to-posthog/retention)  
+- [Watch some session replays](https://app.posthog.com/project/replay/home), see what you can learn  
+- Try out a [no-code survey](/docs/surveys/creating-surveys) to learn what customers are feeling about your product
+- Fire up [web analytics](/docs/web-analytics/getting-started), see if you like it better than your existing provider
+
+After two weeks to explore, check in with your teammates as well. See if there’s anything they want but aren't getting. If you can get them excited with you, you'll have a better chance of making this pilot turn into a full-on switch.
+
+## Assess costs
+
+After a couple weeks, you should have a decent picture of how much activity PostHog is tracking, and you can use that to understand your costs.
+
+From here there’s no sneaky stuff. All our [pricing is posted publicly](/pricing), and you can use our interactive calculator to project your monthly bill.
path: contents/docs/new-to-posthog/switch-guide/planning-your-pilot.mdx
user: login: ivanagas
body: ```suggestion
From here there’s no sneaky stuff. All our [pricing is posted publicly](/pricing), and you can see your project spend in [your billing settings](https://us.posthog.com/organization/billing). 

Think it's too much? Check out our guides on cutting costs for [product analytics](/docs/product-analytics/cutting-costs), [session replay](/docs/session-replay/cutting-costs), and [feature flags](/docs/feature-flags/cutting-costs).
```
created_at: 2025-04-09T19:04:28Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,67 @@
+---
+title: Planning your pilot
+nextPage: ./migration-planning.mdx
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+We want you to love using PostHog. We’ve worked hard to craft a tool that can make you much more effective at giving your customers what they want.
+
+To get the most out of this, a little planning goes a long way. Here’s what you can do to make the most of a pilot.
+
+## List out the people who care about user behavior, no matter their role
+
+PostHog charges by how successful your product is, not how many people have a login.
+
+That means anyone and everyone on your crew can explore at no extra cost. As your integration comes online, think about who else you’d like to invite. You'll have the option to invite them during setup, and any time after that.
+
+## Get help if you want it
+
+For companies sized 25 and up, [we’ve got a team](/talk-to-a-human) who can answer questions and help you make a plan. But only if you want the help! They’re not going to pressure you or do anything corny, but their integration experience can save time and help you plan. They can also help you map PostHog features to your business goals and develop a mental model for using all our products.
+
+But we’re not going to get in your way, either, because…
+
+## We want you to play around
+
+The most important job is getting familiar with PostHog in whatever way makes you most comfortable. A basic integration is fast, and we’ve got loads of documentation to support your journey if you want to explore on your own.
+
+## First two weeks: get data in, then look at it
+
+Job one is making sure PostHog is reliably ingesting your data and reporting the basics in a dashboard. Once this is working, take a break, order a pizza[^1].
+
+From here, you can get more sophisticated:
+
+- **Decide**: Your [North Star metric](/docs/new-to-posthog/getting-hogpilled)  
+- **Decide**: Make an event tracking plan, or rely on autocapture?  
+- **Decide**: Use [identified or anonymous events](/docs/data/anonymous-vs-identified-events)?  
+- Configure a [reverse proxy](/docs/advanced/proxy) to improve reliability of event capture  
+- Experiment with measuring [activation](/docs/new-to-posthog/activation) and [retention](/docs/new-to-posthog/retention)  
+- [Watch some session replays](https://app.posthog.com/project/replay/home), see what you can learn  
+- Try out a [no-code survey](/docs/surveys/creating-surveys) to learn what customers are feeling about your product
+- Fire up [web analytics](/docs/web-analytics/getting-started), see if you like it better than your existing provider
+
+After two weeks to explore, check in with your teammates as well. See if there’s anything they want but aren't getting. If you can get them excited with you, you'll have a better chance of making this pilot turn into a full-on switch.
+
+## Assess costs
+
+After a couple weeks, you should have a decent picture of how much activity PostHog is tracking, and you can use that to understand your costs.
+
+From here there’s no sneaky stuff. All our [pricing is posted publicly](/pricing), and you can use our interactive calculator to project your monthly bill.
+
+<CalloutBox icon="IconRocket" title="We guarantee your safe pilot" type="action">
+
+You don't need to worry about a surprise billing spike as you're getting started. If something unexpected happens, just [get in touch](/talk-to-a-human). We’ll work it out with you. We need your trust and enthusiasm way more than we need a month of charges you weren't expecting.
+
+We’re in this for the long-haul. If you want more time to evaluate, and our generous free tier isn’t going to cover your volume of usage, just tell us about it. We can offer you a longer no-cost trial so you can be completely confident in switching over.
path: contents/docs/new-to-posthog/switch-guide/planning-your-pilot.mdx
user: login: ivanagas
body: Again, what scale are we looking at for the no cost trial?
created_at: 2025-04-09T19:06:40Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,83 @@
+---
+title: What to expect as you migrate
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+With your team onboard and a successful pilot completed, you can turn your attention to **planning your migration**.
+
+## Technical planning
+
+PostHog provides tools and guides to support you making this switch. Check out our migration section for details on moving from Amplitude, Mixpanel, LaunchDarkly and others.
+
+Stumped on any detail of the process? If you’ve already signed up and started sending events with a forecasted bill of $500 or more, our **onboarding** team will reach out to help. If you haven’t heard from us yet, [drop us a line](/talk-to-a-human) with your migration questions!
+
+<CalloutBox title="Avoid common setup pitfalls" type="caution">
+
+Don’t create separate projects for mobile and web. PostHog works best when you can see user behavior across all versions of your products in one set of data and views.
+
+Healthy integrations have a few things in common. It can help to review the [health check](/handbook/growth/sales/health-checks) documentation used by our sales team to tackle the most common ways to keep your bill manageable and predictable.
+
+If your historical data is above 50 GB, you should [reach out to our sales team](/talk-to-a-human) or [open a support ticket](/docs/support-options) so we can make sure everything goes through smoothly.
path: contents/docs/new-to-posthog/switch-guide/migration-planning.mdx
user: login: ivanagas
body: I think there was a mention of 20M events in the past but that was removed. 
created_at: 2025-04-09T19:07:21Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,89 @@
+---
+title: What to expect as you migrate
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+With your team onboard and a successful pilot completed, you can turn your attention to **planning your migration**.
path: contents/docs/new-to-posthog/switch-guide/migration-planning.mdx
user: login: ivanagas
body: ```suggestion
With your team onboarded and a successful pilot completed, you can turn your attention to **planning your migration**.
```
created_at: 2025-04-09T19:07:32Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,89 @@
+---
+title: What to expect as you migrate
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+With your team onboard and a successful pilot completed, you can turn your attention to **planning your migration**.
+
+***
+
+## Technical planning
+
+PostHog provides tools and guides to support you making this switch. Check out our [migration docs](/docs/migrate) for details on moving from [Amplitude](/docs/migrate/migrate-from-amplitude), [Mixpanel](/docs/migrate/mixpanel), [LaunchDarkly](/docs/migrate/launchdarkly) and others.
+
+Stumped on any detail of the process? If you’ve already signed up and started sending events with a forecasted bill of $500 or more, our **onboarding** team will reach out to help. If you haven’t heard from us yet, [drop us a line](/talk-to-a-human) with your migration questions!
+
+<CalloutBox icon="IconWarning" title="Avoid common setup pitfalls" type="caution">
+
+Don’t create separate projects for mobile and web. PostHog works best when you can see user behavior across all versions of your products in one set of data and views.
+
+Healthy integrations have a few things in common. It can help to review the [health check](/handbook/growth/sales/health-checks) documentation used by our sales team to tackle the most common ways to keep your bill manageable and predictable.
+
+If your historical data is above 50 GB, you should [reach out to our sales team](/talk-to-a-human) or [open a support ticket](/docs/support-options) so we can make sure everything goes through smoothly.
path: contents/docs/new-to-posthog/switch-guide/migration-planning.mdx
user: login: ivanagas
body: ```suggestion
- Don’t create separate projects for mobile and web. PostHog works best when you can see user behavior across all versions of your products in one set of data and views.

- Healthy integrations have a few things in common. It can help to review the [health check](/handbook/growth/sales/health-checks) documentation used by our sales team to tackle the most common ways to keep your bill manageable and predictable.

- If your historical data is above 50 GB, you should [reach out to our sales team](/talk-to-a-human) or [open a support ticket](/docs/support-options) so we can make sure everything goes through smoothly.
```
created_at: 2025-04-09T19:08:32Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,89 @@
+---
+title: What to expect as you migrate
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+With your team onboard and a successful pilot completed, you can turn your attention to **planning your migration**.
+
+***
+
+## Technical planning
+
+PostHog provides tools and guides to support you making this switch. Check out our [migration docs](/docs/migrate) for details on moving from [Amplitude](/docs/migrate/migrate-from-amplitude), [Mixpanel](/docs/migrate/mixpanel), [LaunchDarkly](/docs/migrate/launchdarkly) and others.
+
+Stumped on any detail of the process? If you’ve already signed up and started sending events with a forecasted bill of $500 or more, our **onboarding** team will reach out to help. If you haven’t heard from us yet, [drop us a line](/talk-to-a-human) with your migration questions!
+
+<CalloutBox icon="IconWarning" title="Avoid common setup pitfalls" type="caution">
+
+Don’t create separate projects for mobile and web. PostHog works best when you can see user behavior across all versions of your products in one set of data and views.
+
+Healthy integrations have a few things in common. It can help to review the [health check](/handbook/growth/sales/health-checks) documentation used by our sales team to tackle the most common ways to keep your bill manageable and predictable.
+
+If your historical data is above 50 GB, you should [reach out to our sales team](/talk-to-a-human) or [open a support ticket](/docs/support-options) so we can make sure everything goes through smoothly.
+
+</CalloutBox>
+
+### Reducing disruption for your teammates
+
+New software can take a moment to click. One way to help your teammates get comfortable is making sure vital numbers are already waiting in your new PostHog setup.
+
+To support this, it can help to make a spreadsheet for people to request their most essential metrics. You want to know what data they need to keep making good decisions, and ensure those metrics are easy to find in PostHog. Capturing these requirements can also help you check that your technical implementation is handling everything necessary.
path: contents/docs/new-to-posthog/switch-guide/migration-planning.mdx
user: login: ivanagas
body: ```suggestion
To support this, make a spreadsheet for people to request their most essential metrics. Use it to create insights in PostHog and then add link them in the spreadsheet. You want to know what data they need to keep making good decisions, and ensure those metrics are easy to find in PostHog. 
```
created_at: 2025-04-09T20:35:13Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,89 @@
+---
+title: What to expect as you migrate
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+With your team onboard and a successful pilot completed, you can turn your attention to **planning your migration**.
+
+***
+
+## Technical planning
+
+PostHog provides tools and guides to support you making this switch. Check out our [migration docs](/docs/migrate) for details on moving from [Amplitude](/docs/migrate/migrate-from-amplitude), [Mixpanel](/docs/migrate/mixpanel), [LaunchDarkly](/docs/migrate/launchdarkly) and others.
+
+Stumped on any detail of the process? If you’ve already signed up and started sending events with a forecasted bill of $500 or more, our **onboarding** team will reach out to help. If you haven’t heard from us yet, [drop us a line](/talk-to-a-human) with your migration questions!
+
+<CalloutBox icon="IconWarning" title="Avoid common setup pitfalls" type="caution">
+
+Don’t create separate projects for mobile and web. PostHog works best when you can see user behavior across all versions of your products in one set of data and views.
+
+Healthy integrations have a few things in common. It can help to review the [health check](/handbook/growth/sales/health-checks) documentation used by our sales team to tackle the most common ways to keep your bill manageable and predictable.
+
+If your historical data is above 50 GB, you should [reach out to our sales team](/talk-to-a-human) or [open a support ticket](/docs/support-options) so we can make sure everything goes through smoothly.
+
+</CalloutBox>
+
+### Reducing disruption for your teammates
+
+New software can take a moment to click. One way to help your teammates get comfortable is making sure vital numbers are already waiting in your new PostHog setup.
+
+To support this, it can help to make a spreadsheet for people to request their most essential metrics. You want to know what data they need to keep making good decisions, and ensure those metrics are easy to find in PostHog. Capturing these requirements can also help you check that your technical implementation is handling everything necessary.
+
+While moving historical events over is straightforward, you’ll need to take some time rebuilding the views and dashboards your team relies on.
+
+### Conversion tracking
+
+An urgent need from marketing and product teams is **tracking conversions**. Getting clear on how to do this in PostHog can reduce frustration as everyone settles in. These docs on using **[funnels](/docs/product-analytics/funnels)** are a great starting point for this kind of reporting.
path: contents/docs/new-to-posthog/switch-guide/migration-planning.mdx
user: login: ivanagas
body: I think there is three parts to conversion tracking:

1. Web analytics conversion
2. Funnels
3. Sending conversion data to tools using pipelines

Do we want to cover all three here?
created_at: 2025-04-09T20:36:07Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,89 @@
+---
+title: What to expect as you migrate
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+With your team onboard and a successful pilot completed, you can turn your attention to **planning your migration**.
+
+***
+
+## Technical planning
+
+PostHog provides tools and guides to support you making this switch. Check out our [migration docs](/docs/migrate) for details on moving from [Amplitude](/docs/migrate/migrate-from-amplitude), [Mixpanel](/docs/migrate/mixpanel), [LaunchDarkly](/docs/migrate/launchdarkly) and others.
+
+Stumped on any detail of the process? If you’ve already signed up and started sending events with a forecasted bill of $500 or more, our **onboarding** team will reach out to help. If you haven’t heard from us yet, [drop us a line](/talk-to-a-human) with your migration questions!
+
+<CalloutBox icon="IconWarning" title="Avoid common setup pitfalls" type="caution">
+
+Don’t create separate projects for mobile and web. PostHog works best when you can see user behavior across all versions of your products in one set of data and views.
+
+Healthy integrations have a few things in common. It can help to review the [health check](/handbook/growth/sales/health-checks) documentation used by our sales team to tackle the most common ways to keep your bill manageable and predictable.
+
+If your historical data is above 50 GB, you should [reach out to our sales team](/talk-to-a-human) or [open a support ticket](/docs/support-options) so we can make sure everything goes through smoothly.
+
+</CalloutBox>
+
+### Reducing disruption for your teammates
+
+New software can take a moment to click. One way to help your teammates get comfortable is making sure vital numbers are already waiting in your new PostHog setup.
+
+To support this, it can help to make a spreadsheet for people to request their most essential metrics. You want to know what data they need to keep making good decisions, and ensure those metrics are easy to find in PostHog. Capturing these requirements can also help you check that your technical implementation is handling everything necessary.
+
+While moving historical events over is straightforward, you’ll need to take some time rebuilding the views and dashboards your team relies on.
+
+### Conversion tracking
+
+An urgent need from marketing and product teams is **tracking conversions**. Getting clear on how to do this in PostHog can reduce frustration as everyone settles in. These docs on using **[funnels](/docs/product-analytics/funnels)** are a great starting point for this kind of reporting.
+
+***
+
+## Providing demos
+
+A great way to help PostHog land well is to offer a quick demo to everyone who’s interested. Remember, we don’t charge by the seat, so anyone who’s curious about user behavior in your product can log in at no extra charge.
path: contents/docs/new-to-posthog/switch-guide/migration-planning.mdx
user: login: ivanagas
body: This second point is repetitive and doesn't really add anything. 
```suggestion
A great way to help PostHog land well is to offer a quick demo to everyone who’s interested.
```
created_at: 2025-04-09T20:37:04Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,89 @@
+---
+title: What to expect as you migrate
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+With your team onboard and a successful pilot completed, you can turn your attention to **planning your migration**.
+
+***
+
+## Technical planning
+
+PostHog provides tools and guides to support you making this switch. Check out our [migration docs](/docs/migrate) for details on moving from [Amplitude](/docs/migrate/migrate-from-amplitude), [Mixpanel](/docs/migrate/mixpanel), [LaunchDarkly](/docs/migrate/launchdarkly) and others.
+
+Stumped on any detail of the process? If you’ve already signed up and started sending events with a forecasted bill of $500 or more, our **onboarding** team will reach out to help. If you haven’t heard from us yet, [drop us a line](/talk-to-a-human) with your migration questions!
+
+<CalloutBox icon="IconWarning" title="Avoid common setup pitfalls" type="caution">
+
+Don’t create separate projects for mobile and web. PostHog works best when you can see user behavior across all versions of your products in one set of data and views.
+
+Healthy integrations have a few things in common. It can help to review the [health check](/handbook/growth/sales/health-checks) documentation used by our sales team to tackle the most common ways to keep your bill manageable and predictable.
+
+If your historical data is above 50 GB, you should [reach out to our sales team](/talk-to-a-human) or [open a support ticket](/docs/support-options) so we can make sure everything goes through smoothly.
+
+</CalloutBox>
+
+### Reducing disruption for your teammates
+
+New software can take a moment to click. One way to help your teammates get comfortable is making sure vital numbers are already waiting in your new PostHog setup.
+
+To support this, it can help to make a spreadsheet for people to request their most essential metrics. You want to know what data they need to keep making good decisions, and ensure those metrics are easy to find in PostHog. Capturing these requirements can also help you check that your technical implementation is handling everything necessary.
+
+While moving historical events over is straightforward, you’ll need to take some time rebuilding the views and dashboards your team relies on.
+
+### Conversion tracking
+
+An urgent need from marketing and product teams is **tracking conversions**. Getting clear on how to do this in PostHog can reduce frustration as everyone settles in. These docs on using **[funnels](/docs/product-analytics/funnels)** are a great starting point for this kind of reporting.
+
+***
+
+## Providing demos
+
+A great way to help PostHog land well is to offer a quick demo to everyone who’s interested. Remember, we don’t charge by the seat, so anyone who’s curious about user behavior in your product can log in at no extra charge.
+
+Here are some topics that might be worth covering. You know your teammates best, so be sure to adjust your demos to their needs and interests.
+
+### Events, persons, properties and the activity view
path: contents/docs/new-to-posthog/switch-guide/migration-planning.mdx
user: login: ivanagas
body: ```suggestion
### Events, persons, properties, and the activity view
```
created_at: 2025-04-09T20:37:41Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,89 @@
+---
+title: What to expect as you migrate
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+With your team onboard and a successful pilot completed, you can turn your attention to **planning your migration**.
+
+***
+
+## Technical planning
+
+PostHog provides tools and guides to support you making this switch. Check out our [migration docs](/docs/migrate) for details on moving from [Amplitude](/docs/migrate/migrate-from-amplitude), [Mixpanel](/docs/migrate/mixpanel), [LaunchDarkly](/docs/migrate/launchdarkly) and others.
+
+Stumped on any detail of the process? If you’ve already signed up and started sending events with a forecasted bill of $500 or more, our **onboarding** team will reach out to help. If you haven’t heard from us yet, [drop us a line](/talk-to-a-human) with your migration questions!
+
+<CalloutBox icon="IconWarning" title="Avoid common setup pitfalls" type="caution">
+
+Don’t create separate projects for mobile and web. PostHog works best when you can see user behavior across all versions of your products in one set of data and views.
+
+Healthy integrations have a few things in common. It can help to review the [health check](/handbook/growth/sales/health-checks) documentation used by our sales team to tackle the most common ways to keep your bill manageable and predictable.
+
+If your historical data is above 50 GB, you should [reach out to our sales team](/talk-to-a-human) or [open a support ticket](/docs/support-options) so we can make sure everything goes through smoothly.
+
+</CalloutBox>
+
+### Reducing disruption for your teammates
+
+New software can take a moment to click. One way to help your teammates get comfortable is making sure vital numbers are already waiting in your new PostHog setup.
+
+To support this, it can help to make a spreadsheet for people to request their most essential metrics. You want to know what data they need to keep making good decisions, and ensure those metrics are easy to find in PostHog. Capturing these requirements can also help you check that your technical implementation is handling everything necessary.
+
+While moving historical events over is straightforward, you’ll need to take some time rebuilding the views and dashboards your team relies on.
+
+### Conversion tracking
+
+An urgent need from marketing and product teams is **tracking conversions**. Getting clear on how to do this in PostHog can reduce frustration as everyone settles in. These docs on using **[funnels](/docs/product-analytics/funnels)** are a great starting point for this kind of reporting.
+
+***
+
+## Providing demos
+
+A great way to help PostHog land well is to offer a quick demo to everyone who’s interested. Remember, we don’t charge by the seat, so anyone who’s curious about user behavior in your product can log in at no extra charge.
+
+Here are some topics that might be worth covering. You know your teammates best, so be sure to adjust your demos to their needs and interests.
+
+### Events, persons, properties and the activity view
+
+![The activity explorer](https://res.cloudinary.com/dmukukwp6/image/upload/activity_2923c81b32.png)
+
+Events are the core of PostHog’s reporting. Explain how they work, and the properties you plan to attach to them as part of your integration. Show off the **[activity](https://app.posthog.com/project/activity/explore)** view so everyone can see new events pouring in. 
+
+If you’re identifying users in your integration, showing how **[person profiles](https://app.posthog.com/project/persons)** collect information can also be helpful.
+
+### Web analytics
+
+Everyone who wants the basics of an analytics dashboard will find it in our **[web analytics](https://app.posthog.com/project/web)** tab right out of the box.
+
+### Actions
+
+Actions let you group and rename events, making them easier to use in reporting. The more your teammates understand actions, the easier everyone’s life gets to be, so take a moment in **[data management](https://app.posthog.com/project/data-management/actions)** to explain.
+
+### Creating insights and dashboards
+
+Creating, editing and duplicating [insights](/docs/product-analytics/insights) is fast and easy, and so is adding these to dashboards. Make sure to give this part of the demo plenty of detail: playing with data is a big part of what makes PostHog fun. This is also a great time to explore **filters**, which are a common need.
path: contents/docs/new-to-posthog/switch-guide/migration-planning.mdx
user: login: ivanagas
body: ```suggestion
Creating, editing, and duplicating [insights](/docs/product-analytics/insights) is fast and easy, and so is adding these to dashboards. Make sure to give this part of the demo plenty of detail: playing with data is a big part of what makes PostHog fun. This is also a great time to explore **filters**, which are a common need.
```
created_at: 2025-04-09T20:38:10Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,89 @@
+---
+title: What to expect as you migrate
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+With your team onboard and a successful pilot completed, you can turn your attention to **planning your migration**.
+
+***
+
+## Technical planning
+
+PostHog provides tools and guides to support you making this switch. Check out our [migration docs](/docs/migrate) for details on moving from [Amplitude](/docs/migrate/migrate-from-amplitude), [Mixpanel](/docs/migrate/mixpanel), [LaunchDarkly](/docs/migrate/launchdarkly) and others.
+
+Stumped on any detail of the process? If you’ve already signed up and started sending events with a forecasted bill of $500 or more, our **onboarding** team will reach out to help. If you haven’t heard from us yet, [drop us a line](/talk-to-a-human) with your migration questions!
+
+<CalloutBox icon="IconWarning" title="Avoid common setup pitfalls" type="caution">
+
+Don’t create separate projects for mobile and web. PostHog works best when you can see user behavior across all versions of your products in one set of data and views.
+
+Healthy integrations have a few things in common. It can help to review the [health check](/handbook/growth/sales/health-checks) documentation used by our sales team to tackle the most common ways to keep your bill manageable and predictable.
+
+If your historical data is above 50 GB, you should [reach out to our sales team](/talk-to-a-human) or [open a support ticket](/docs/support-options) so we can make sure everything goes through smoothly.
+
+</CalloutBox>
+
+### Reducing disruption for your teammates
+
+New software can take a moment to click. One way to help your teammates get comfortable is making sure vital numbers are already waiting in your new PostHog setup.
+
+To support this, it can help to make a spreadsheet for people to request their most essential metrics. You want to know what data they need to keep making good decisions, and ensure those metrics are easy to find in PostHog. Capturing these requirements can also help you check that your technical implementation is handling everything necessary.
+
+While moving historical events over is straightforward, you’ll need to take some time rebuilding the views and dashboards your team relies on.
+
+### Conversion tracking
+
+An urgent need from marketing and product teams is **tracking conversions**. Getting clear on how to do this in PostHog can reduce frustration as everyone settles in. These docs on using **[funnels](/docs/product-analytics/funnels)** are a great starting point for this kind of reporting.
+
+***
+
+## Providing demos
+
+A great way to help PostHog land well is to offer a quick demo to everyone who’s interested. Remember, we don’t charge by the seat, so anyone who’s curious about user behavior in your product can log in at no extra charge.
+
+Here are some topics that might be worth covering. You know your teammates best, so be sure to adjust your demos to their needs and interests.
+
+### Events, persons, properties and the activity view
+
+![The activity explorer](https://res.cloudinary.com/dmukukwp6/image/upload/activity_2923c81b32.png)
+
+Events are the core of PostHog’s reporting. Explain how they work, and the properties you plan to attach to them as part of your integration. Show off the **[activity](https://app.posthog.com/project/activity/explore)** view so everyone can see new events pouring in. 
+
+If you’re identifying users in your integration, showing how **[person profiles](https://app.posthog.com/project/persons)** collect information can also be helpful.
+
+### Web analytics
+
+Everyone who wants the basics of an analytics dashboard will find it in our **[web analytics](https://app.posthog.com/project/web)** tab right out of the box.
+
+### Actions
+
+Actions let you group and rename events, making them easier to use in reporting. The more your teammates understand actions, the easier everyone’s life gets to be, so take a moment in **[data management](https://app.posthog.com/project/data-management/actions)** to explain.
+
+### Creating insights and dashboards
+
+Creating, editing and duplicating [insights](/docs/product-analytics/insights) is fast and easy, and so is adding these to dashboards. Make sure to give this part of the demo plenty of detail: playing with data is a big part of what makes PostHog fun. This is also a great time to explore **filters**, which are a common need.
+
+Popular insights include:
+
+- Trends: show change over time  
+- Funnels: track conversions and other sequential activity  
+- User paths: see how real people explore your sight
+
+### Replays
+
+[Replays](https://app.posthog.com/project/replay/home) are a hit across roles and teams. For engineers, they can be a way of catching layout problems and other bugs early. For product and design, they’re a way to make sure that new features and workflows are actually performing correctly. They’re a huge help to support, and even execs enjoy flipping through them.
+
+### Instant, no-code surveys
+
+If you’re talking to someone who really wants to hear from customers, [surveys](https://app.posthog.com/project/surveys) are going to be exciting. Walk through how to design and deploy one.
+
+### Toolbar
+
+This one is a visual crowd pleaser: launch your site’s PostHog [toolbar](https://app.posthog.com/project/toolbar) to show heatmap overlays and other stats directly on your site.
path: contents/docs/new-to-posthog/switch-guide/migration-planning.mdx
user: login: ivanagas
body: Why we don't have a docs page for this, I do not understand.
```suggestion
This one is a visual crowd pleaser: launch your site’s PostHog [toolbar](https://app.posthog.com/project/toolbar) to show heatmap overlays and other stats directly on your site. You can even use it to launch [hedgehog mode](/blog/aruba-hackathon#hedgehog-mode--toolbar--awesomeness).
```
created_at: 2025-04-09T20:40:06Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,132 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and simple integration gets you everything you need to build great products.
+
+But if you're already leaning on another tool, switching can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+***
+
+## Advantages for everyone
+
+PostHog is one login and one bill.
+
+This means less headache for more power, with all your data available across a range of products that help you understand user behavior as it happens.
+
+You'll get a responsive team that cares about user needs, delivering improvements, and customer requests constantly.
+
+PostHog is completely agnostic to the language, framework, and stack you build your product with. You can adopt it incrementally, adding new functionality as needed.
+
+Best of all, PostHog is modern, constantly improving, and built so that you’ll actually enjoy using it.
+
+***
+
+## Persuading product teams
+
+PostHog gives product teams the power to understand users, improve adoption, and test assumptions. Your product teammates can dive in immediately without having to wait for engineers to write new code or hook up an integration.
+
+- **[Visualize anything](/docs/product-analytics/insights)** with charts, trend reporting, and [dashboards](/docs/product-analytics/dashboards) that are easy to build, but also deeply customizable for SQL enthusiasts.
+
+- **Learn anything you want** about everything the user touches in the product without manual instrumentation with [autocapture](/docs/product-analytics/autocapture).
+
+- **Get clarity about navigation** and user priorities with [heatmaps](/docs/toolbar/heatmaps).
+
+- Use [session replay](/docs/session-replay/installation) to **reveal bugs, expose friction, and help instantly answer questions** like “is this new design working?”
+
+- **Integrate revenue data** from [Stripe](/docs/cdp/sources/stripe) and other sources using data warehouse, so you can get a clear picture of what changes really move the needle.
+
+- **Send events and other details to any other tool**, powering automations and keeping data in sync, with setup you can accomplish in seconds, fully customizable for any API or webhook. [Data pipelines](/docs/cdp) makes it easy.
+
+- **Gather feedback and book user interviews** from exactly the users you want to reach with no-code [surveys](/docs/surveys/creating-surveys) that launch instantly.
+
+- **Get unblocked by PostHog’s helpful sales and support teams,** ensuring you get the insights and information you need quickly.
+
+***
+
+## Good news for engineering teams
+
+PostHog is designed for developers.
+
+The project is [developed in the open](https://github.com/PostHog/posthog), with a [public roadmap](/roadmap) and [dozens of pull requests landing](https://github.com/PostHog/posthog/pulls?q=is%3Apr+is%3Aclosed) each week. While other products are low-velocity black boxes, we’re constantly making PostHog better.
+
+ We’ve got a dedicated technical staff standing by to help keep you on track. When you reach out to support, you’ll be talking to someone who knows the technical details of the product really well.
+
+Giving other teams the data they want becomes much easier with PostHog in the mix, lowering the burden on engineering. Once a basic integration is in place, there are loads of features everyone can use without a developer's intervention.
+
+- **Consolidate the tools your company needs**, with one login, one integration, one bill.
+
+- **[Get comprehensive documentation](/docs)** developers love for every every stack, framework, and language.
+
+- **Get a data platform that encourages tinkering**: if something doesn’t fit quite right for your team, it’s easy to customize everything from visualizations to integrations with other services. We'll host all these customizations for you. You don't need to worry about infrastructure or uptime.
+
+- **Integrating PostHog with other tools or even your own services is easy**, thanks to [data pipelines](/docs/cdp).
+
+- **Roll features out gradually** using [feature flags](/docs/feature-flags/creating-feature-flags) that are easy to target with fine-grained queries across everything PostHog knows about your users.
+
+We also care about the technical details of switching over. No matter your stack or existing tools, **complete integration and [migration docs](/docs/migration)** mean a clear path instead of a puzzle to solve. Our experienced Sales and CS team can even provide backup for more complex cases.
+
+***
+
+## Make the case to executives
+
+We’re in this for a long-term relationship, so **PostHog wants you to spend as little money as possible**. Our sales team actually works with customers to reduce bills and optimize consumption. Instead of sneaky billing, we’d prefer to make more money as a result of you winning more business.
+
+There’s just no sneaky stuff going on here. You can get started immediately with no shenanigans, no calls with the sales team.
+
+- **Your team will like PostHog**. It’s fresh, always getting fixes, improvements and additional power. An investment in PostHog today means even more capabilities by next year.
+
+- **There's no per-seat charge**, so PostHog makes it easy for everyone on your team to make data-driven decisions. No matter how quickly you scale your team, your costs remain fixed to the actual usage of your product. 
+
+- **PostHog’s sales process is transparent and so is the whole company**: the company [handbook is public](/handbook), *even documenting the ways we can offer [discounts](/handbook/growth/sales/billing#coupons-and-discounts)*. Everything you want to know about pricing, processes and our product is publicly documented.
+
+- **You can have a free trial** to fully vet the costs and impact of your integration. Trying PostHog is low-risk, no cost, and fully reversible.
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: daniloc
body: EFFECTIVELY, everyone. If you're small you're covered under the free tier anyway, if you're huge, sales will just hook you up.
created_at: 2025-04-09T20:51:04Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,67 @@
+---
+title: Planning your pilot
+nextPage: ./migration-planning.mdx
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+We want you to love using PostHog. We’ve worked hard to craft a tool that can make you much more effective at giving your customers what they want.
+
+To get the most out of this, a little planning goes a long way. Here’s what you can do to make the most of a pilot.
path: contents/docs/new-to-posthog/switch-guide/planning-your-pilot.mdx
user: login: daniloc
body: thank youuuuu
created_at: 2025-04-09T20:53:34Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,89 @@
+---
+title: What to expect as you migrate
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+With your team onboard and a successful pilot completed, you can turn your attention to **planning your migration**.
+
+***
+
+## Technical planning
+
+PostHog provides tools and guides to support you making this switch. Check out our [migration docs](/docs/migrate) for details on moving from [Amplitude](/docs/migrate/migrate-from-amplitude), [Mixpanel](/docs/migrate/mixpanel), [LaunchDarkly](/docs/migrate/launchdarkly) and others.
+
+Stumped on any detail of the process? If you’ve already signed up and started sending events with a forecasted bill of $500 or more, our **onboarding** team will reach out to help. If you haven’t heard from us yet, [drop us a line](/talk-to-a-human) with your migration questions!
+
+<CalloutBox icon="IconWarning" title="Avoid common setup pitfalls" type="caution">
+
+Don’t create separate projects for mobile and web. PostHog works best when you can see user behavior across all versions of your products in one set of data and views.
+
+Healthy integrations have a few things in common. It can help to review the [health check](/handbook/growth/sales/health-checks) documentation used by our sales team to tackle the most common ways to keep your bill manageable and predictable.
+
+If your historical data is above 50 GB, you should [reach out to our sales team](/talk-to-a-human) or [open a support ticket](/docs/support-options) so we can make sure everything goes through smoothly.
+
+</CalloutBox>
+
+### Reducing disruption for your teammates
+
+New software can take a moment to click. One way to help your teammates get comfortable is making sure vital numbers are already waiting in your new PostHog setup.
+
+To support this, it can help to make a spreadsheet for people to request their most essential metrics. You want to know what data they need to keep making good decisions, and ensure those metrics are easy to find in PostHog. Capturing these requirements can also help you check that your technical implementation is handling everything necessary.
+
+While moving historical events over is straightforward, you’ll need to take some time rebuilding the views and dashboards your team relies on.
+
+### Conversion tracking
+
+An urgent need from marketing and product teams is **tracking conversions**. Getting clear on how to do this in PostHog can reduce frustration as everyone settles in. These docs on using **[funnels](/docs/product-analytics/funnels)** are a great starting point for this kind of reporting.
+
+***
+
+## Providing demos
+
+A great way to help PostHog land well is to offer a quick demo to everyone who’s interested. Remember, we don’t charge by the seat, so anyone who’s curious about user behavior in your product can log in at no extra charge.
+
+Here are some topics that might be worth covering. You know your teammates best, so be sure to adjust your demos to their needs and interests.
+
+### Events, persons, properties and the activity view
path: contents/docs/new-to-posthog/switch-guide/migration-planning.mdx
user: login: daniloc
body: rueful that I could pick up the endash house style immediately, but my internal compiler doesn't even catch the oxfords, thank you
created_at: 2025-04-09T20:57:19Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,67 @@
+---
+title: Planning your pilot
+nextPage: ./migration-planning.mdx
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+We want you to love using PostHog. We’ve worked hard to craft a tool that can make you much more effective at giving your customers what they want.
+
+To get the most out of this, a little planning goes a long way. Here’s what you can do to make the most of a pilot.
+
+## List out the people who care about user behavior, no matter their role
+
+PostHog charges by how successful your product is, not how many people have a login.
+
+That means anyone and everyone on your crew can explore at no extra cost. As your integration comes online, think about who else you’d like to invite. You'll have the option to invite them during setup, and any time after that.
+
+## Get help if you want it
+
+For companies sized 25 and up, [we’ve got a team](/talk-to-a-human) who can answer questions and help you make a plan. But only if you want the help! They’re not going to pressure you or do anything corny, but their integration experience can save time and help you plan. They can also help you map PostHog features to your business goals and develop a mental model for using all our products.
+
+But we’re not going to get in your way, either, because…
+
+## We want you to play around
+
+The most important job is getting familiar with PostHog in whatever way makes you most comfortable. A basic integration is fast, and we’ve got loads of documentation to support your journey if you want to explore on your own.
+
+## First two weeks: get data in, then look at it
+
+Job one is making sure PostHog is reliably ingesting your data and reporting the basics in a dashboard. Once this is working, take a break, order a pizza[^1].
+
+From here, you can get more sophisticated:
+
+- **Decide**: Your [North Star metric](/docs/new-to-posthog/getting-hogpilled)  
+- **Decide**: Make an event tracking plan, or rely on autocapture?  
path: contents/docs/new-to-posthog/switch-guide/planning-your-pilot.mdx
user: login: daniloc
body: Hogpilled nudges you toward creating one but I think we're finding that a dedicated resource on this is going to be necessary
created_at: 2025-04-09T20:58:35Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,67 @@
+---
+title: Planning your pilot
+nextPage: ./migration-planning.mdx
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+We want you to love using PostHog. We’ve worked hard to craft a tool that can make you much more effective at giving your customers what they want.
+
+To get the most out of this, a little planning goes a long way. Here’s what you can do to make the most of a pilot.
+
+## List out the people who care about user behavior, no matter their role
+
+PostHog charges by how successful your product is, not how many people have a login.
+
+That means anyone and everyone on your crew can explore at no extra cost. As your integration comes online, think about who else you’d like to invite. You'll have the option to invite them during setup, and any time after that.
+
+## Get help if you want it
+
+For companies sized 25 and up, [we’ve got a team](/talk-to-a-human) who can answer questions and help you make a plan. But only if you want the help! They’re not going to pressure you or do anything corny, but their integration experience can save time and help you plan. They can also help you map PostHog features to your business goals and develop a mental model for using all our products.
+
+But we’re not going to get in your way, either, because…
+
+## We want you to play around
+
+The most important job is getting familiar with PostHog in whatever way makes you most comfortable. A basic integration is fast, and we’ve got loads of documentation to support your journey if you want to explore on your own.
+
+## First two weeks: get data in, then look at it
+
+Job one is making sure PostHog is reliably ingesting your data and reporting the basics in a dashboard. Once this is working, take a break, order a pizza[^1].
+
+From here, you can get more sophisticated:
+
+- **Decide**: Your [North Star metric](/docs/new-to-posthog/getting-hogpilled)  
+- **Decide**: Make an event tracking plan, or rely on autocapture?  
path: contents/docs/new-to-posthog/switch-guide/planning-your-pilot.mdx
user: login: daniloc
body: https://github.com/PostHog/posthog.com/issues/11243
created_at: 2025-04-09T21:00:11Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,89 @@
+---
+title: What to expect as you migrate
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+With your team onboard and a successful pilot completed, you can turn your attention to **planning your migration**.
+
+***
+
+## Technical planning
+
+PostHog provides tools and guides to support you making this switch. Check out our [migration docs](/docs/migrate) for details on moving from [Amplitude](/docs/migrate/migrate-from-amplitude), [Mixpanel](/docs/migrate/mixpanel), [LaunchDarkly](/docs/migrate/launchdarkly) and others.
+
+Stumped on any detail of the process? If you’ve already signed up and started sending events with a forecasted bill of $500 or more, our **onboarding** team will reach out to help. If you haven’t heard from us yet, [drop us a line](/talk-to-a-human) with your migration questions!
+
+<CalloutBox icon="IconWarning" title="Avoid common setup pitfalls" type="caution">
+
+Don’t create separate projects for mobile and web. PostHog works best when you can see user behavior across all versions of your products in one set of data and views.
+
+Healthy integrations have a few things in common. It can help to review the [health check](/handbook/growth/sales/health-checks) documentation used by our sales team to tackle the most common ways to keep your bill manageable and predictable.
+
+If your historical data is above 50 GB, you should [reach out to our sales team](/talk-to-a-human) or [open a support ticket](/docs/support-options) so we can make sure everything goes through smoothly.
+
+</CalloutBox>
+
+### Reducing disruption for your teammates
+
+New software can take a moment to click. One way to help your teammates get comfortable is making sure vital numbers are already waiting in your new PostHog setup.
+
+To support this, it can help to make a spreadsheet for people to request their most essential metrics. You want to know what data they need to keep making good decisions, and ensure those metrics are easy to find in PostHog. Capturing these requirements can also help you check that your technical implementation is handling everything necessary.
path: contents/docs/new-to-posthog/switch-guide/migration-planning.mdx
user: login: daniloc
body: NICE
created_at: 2025-04-09T21:07:40Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,89 @@
+---
+title: What to expect as you migrate
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+With your team onboard and a successful pilot completed, you can turn your attention to **planning your migration**.
+
+***
+
+## Technical planning
+
+PostHog provides tools and guides to support you making this switch. Check out our [migration docs](/docs/migrate) for details on moving from [Amplitude](/docs/migrate/migrate-from-amplitude), [Mixpanel](/docs/migrate/mixpanel), [LaunchDarkly](/docs/migrate/launchdarkly) and others.
+
+Stumped on any detail of the process? If you’ve already signed up and started sending events with a forecasted bill of $500 or more, our **onboarding** team will reach out to help. If you haven’t heard from us yet, [drop us a line](/talk-to-a-human) with your migration questions!
+
+<CalloutBox icon="IconWarning" title="Avoid common setup pitfalls" type="caution">
+
+Don’t create separate projects for mobile and web. PostHog works best when you can see user behavior across all versions of your products in one set of data and views.
+
+Healthy integrations have a few things in common. It can help to review the [health check](/handbook/growth/sales/health-checks) documentation used by our sales team to tackle the most common ways to keep your bill manageable and predictable.
+
+If your historical data is above 50 GB, you should [reach out to our sales team](/talk-to-a-human) or [open a support ticket](/docs/support-options) so we can make sure everything goes through smoothly.
+
+</CalloutBox>
+
+### Reducing disruption for your teammates
+
+New software can take a moment to click. One way to help your teammates get comfortable is making sure vital numbers are already waiting in your new PostHog setup.
+
+To support this, it can help to make a spreadsheet for people to request their most essential metrics. You want to know what data they need to keep making good decisions, and ensure those metrics are easy to find in PostHog. Capturing these requirements can also help you check that your technical implementation is handling everything necessary.
path: contents/docs/new-to-posthog/switch-guide/migration-planning.mdx
user: login: daniloc
body: But I do wanna keep this too, it's an important error correction/data loss prevention exercise:

> Capturing these requirements can also help you check that your technical implementation is handling everything necessary.
created_at: 2025-04-09T21:08:25Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,89 @@
+---
+title: What to expect as you migrate
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+With your team onboard and a successful pilot completed, you can turn your attention to **planning your migration**.
+
+***
+
+## Technical planning
+
+PostHog provides tools and guides to support you making this switch. Check out our [migration docs](/docs/migrate) for details on moving from [Amplitude](/docs/migrate/migrate-from-amplitude), [Mixpanel](/docs/migrate/mixpanel), [LaunchDarkly](/docs/migrate/launchdarkly) and others.
+
+Stumped on any detail of the process? If you’ve already signed up and started sending events with a forecasted bill of $500 or more, our **onboarding** team will reach out to help. If you haven’t heard from us yet, [drop us a line](/talk-to-a-human) with your migration questions!
+
+<CalloutBox icon="IconWarning" title="Avoid common setup pitfalls" type="caution">
+
+Don’t create separate projects for mobile and web. PostHog works best when you can see user behavior across all versions of your products in one set of data and views.
+
+Healthy integrations have a few things in common. It can help to review the [health check](/handbook/growth/sales/health-checks) documentation used by our sales team to tackle the most common ways to keep your bill manageable and predictable.
+
+If your historical data is above 50 GB, you should [reach out to our sales team](/talk-to-a-human) or [open a support ticket](/docs/support-options) so we can make sure everything goes through smoothly.
+
+</CalloutBox>
+
+### Reducing disruption for your teammates
+
+New software can take a moment to click. One way to help your teammates get comfortable is making sure vital numbers are already waiting in your new PostHog setup.
+
+To support this, it can help to make a spreadsheet for people to request their most essential metrics. You want to know what data they need to keep making good decisions, and ensure those metrics are easy to find in PostHog. Capturing these requirements can also help you check that your technical implementation is handling everything necessary.
+
+While moving historical events over is straightforward, you’ll need to take some time rebuilding the views and dashboards your team relies on.
+
+### Conversion tracking
+
+An urgent need from marketing and product teams is **tracking conversions**. Getting clear on how to do this in PostHog can reduce frustration as everyone settles in. These docs on using **[funnels](/docs/product-analytics/funnels)** are a great starting point for this kind of reporting.
path: contents/docs/new-to-posthog/switch-guide/migration-planning.mdx
user: login: daniloc
body: I think for this stage I just want to make sure that the conversion tracking isn't *lost*, and make that feel scoped and achievable

"Oh, you lost my conversion data" is a great way to freak out whoever gets choked if the conversions go down
created_at: 2025-04-09T21:10:27Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,89 @@
+---
+title: What to expect as you migrate
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+With your team onboard and a successful pilot completed, you can turn your attention to **planning your migration**.
+
+***
+
+## Technical planning
+
+PostHog provides tools and guides to support you making this switch. Check out our [migration docs](/docs/migrate) for details on moving from [Amplitude](/docs/migrate/migrate-from-amplitude), [Mixpanel](/docs/migrate/mixpanel), [LaunchDarkly](/docs/migrate/launchdarkly) and others.
+
+Stumped on any detail of the process? If you’ve already signed up and started sending events with a forecasted bill of $500 or more, our **onboarding** team will reach out to help. If you haven’t heard from us yet, [drop us a line](/talk-to-a-human) with your migration questions!
+
+<CalloutBox icon="IconWarning" title="Avoid common setup pitfalls" type="caution">
+
+Don’t create separate projects for mobile and web. PostHog works best when you can see user behavior across all versions of your products in one set of data and views.
+
+Healthy integrations have a few things in common. It can help to review the [health check](/handbook/growth/sales/health-checks) documentation used by our sales team to tackle the most common ways to keep your bill manageable and predictable.
+
+If your historical data is above 50 GB, you should [reach out to our sales team](/talk-to-a-human) or [open a support ticket](/docs/support-options) so we can make sure everything goes through smoothly.
path: contents/docs/new-to-posthog/switch-guide/migration-planning.mdx
user: login: daniloc
body: this ended up doing more harm than good, much as I like the premise

<img width="688" alt="Screenshot 2025-04-09 at 5 06 59 PM" src="https://github.com/user-attachments/assets/c36fd3ba-c320-41d1-b22c-d6f8ccfecb27" />

created_at: 2025-04-09T21:19:43Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,132 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and simple integration gets you everything you need to build great products.
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: andyvan-ph
body: ```suggestion
PostHog is an easy sell for new projects and companies: one login and simple integration gets you everything you need to build great products.
```
created_at: 2025-04-11T10:06:22Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,132 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and simple integration gets you everything you need to build great products.
+
+But if you're already leaning on another tool, switching can require some planning and diplomacy. We made you a cheatsheet to help make the case.
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: andyvan-ph
body: ```suggestion
But switching from another tool requires some planning and diplomacy. A little finesse. Our switching guide exists to help you on through the journey, starting with how to sell PostHog to your teammates, then [how to plan your pilot deployment](/docs/new-to-posthog/switch-guide/planning-your-pilot), and how to [nail your migration](/docs/new-to-posthog/switch-guide/migration-planning).

Don't ask us to explain PostHog to your parents, though. Seriously, we've been down this road already. It's a losing battle.
```

Feel free to omit the parents gag.
created_at: 2025-04-11T10:15:29Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,132 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and simple integration gets you everything you need to build great products.
+
+But if you're already leaning on another tool, switching can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+***
+
+## Advantages for everyone
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: andyvan-ph
body: ```suggestion
## Why everyone will love PostHog
```
created_at: 2025-04-11T10:17:14Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,132 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and simple integration gets you everything you need to build great products.
+
+But if you're already leaning on another tool, switching can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+***
+
+## Advantages for everyone
+
+PostHog is one login and one bill.
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: andyvan-ph
body: ```suggestion
Because PostHog is one login and one bill.
```
created_at: 2025-04-11T10:17:24Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,132 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and simple integration gets you everything you need to build great products.
+
+But if you're already leaning on another tool, switching can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+***
+
+## Advantages for everyone
+
+PostHog is one login and one bill.
+
+This means less headache for more power, with all your data available across a range of products that help you understand user behavior as it happens.
+
+You'll get a responsive team that cares about user needs, delivering on customer feedback constantly.
+
+PostHog is completely agnostic to the language, framework, and stack you build your product with. You can adopt it incrementally, adding new functionality as needed.
+
+Best of all, PostHog is built so that you’ll actually enjoy using it. We really want you to have a good time.
+
+***
+
+## Persuading product teams
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: andyvan-ph
body: ```suggestion
## Why your product teams will love PostHog
```
created_at: 2025-04-11T10:18:09Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,132 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and simple integration gets you everything you need to build great products.
+
+But if you're already leaning on another tool, switching can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+***
+
+## Advantages for everyone
+
+PostHog is one login and one bill.
+
+This means less headache for more power, with all your data available across a range of products that help you understand user behavior as it happens.
+
+You'll get a responsive team that cares about user needs, delivering on customer feedback constantly.
+
+PostHog is completely agnostic to the language, framework, and stack you build your product with. You can adopt it incrementally, adding new functionality as needed.
+
+Best of all, PostHog is built so that you’ll actually enjoy using it. We really want you to have a good time.
+
+***
+
+## Persuading product teams
+
+PostHog gives product teams the power to understand users, improve adoption, and test assumptions. Once PostHog is in place, your product teammates can dive in immediately, with loads of power that doesn't require further engineering intervention.
+
+- **[Visualize anything](/docs/product-analytics/insights)** with charts, trend reporting, and [dashboards](/docs/product-analytics/dashboards) that are easy to build, but also deeply customizable for SQL enthusiasts.
+
+- **Learn anything you want** about everything the user touches in the product without manual instrumentation with [autocapture](/docs/product-analytics/autocapture).
+
+- **Get clarity about navigation** and user priorities with [heatmaps](/docs/toolbar/heatmaps).
+
+- Use [session replay](/docs/session-replay/installation) to **reveal bugs, expose friction, and help instantly answer questions** like “is this new design working?”
+
+- **Integrate revenue data** from [Stripe](/docs/cdp/sources/stripe) and other sources using data warehouse, so you can get a clear picture of what changes really move the needle.
+
+- **Send events and other details to any other tool**, powering automations and keeping data in sync, with setup you can accomplish in seconds, fully customizable for any API or webhook. [Data pipelines](/docs/cdp) makes it easy.
+
+- **Gather feedback and book user interviews** from exactly the users you want to reach with no-code [surveys](/docs/surveys/creating-surveys) that deploy instantly.
+
+- **Get unblocked by PostHog’s helpful sales and support teams,** ensuring you get the insights and information you need quickly.
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: andyvan-ph
body: ```suggestion
**Visualize anything** with [charts and trend reporting](docs/product-analytics/insights), and [dashboards](/docs/product-analytics/dashboards) that are easy to build, but also deeply customizable for SQL enthusiasts.

**Learn anything you want** about everything the user touches in the product without manual instrumentation with [autocapture](/docs/product-analytics/autocapture).

**Get clarity about navigation** and user priorities with [heatmaps](/docs/toolbar/heatmaps).

**Use session replay to reveal bugs**, expose friction, and help instantly answer questions like “is this new design working?” We support both [web and mobile SDKS](/docs/session-replay/installation).

**Integrate revenue data** from [Stripe](/docs/cdp/sources/stripe) and other sources using data warehouse, so you can get a clear picture of what changes really move the needle.

**Send events and other details to any other tool**, powering automations and keeping data in sync, with setup you can accomplish in seconds, fully customizable for any API or webhook. [Data pipelines](/docs/cdp) makes it easy.

**Gather feedback and book user interviews** from exactly the users you want to reach with no-code [surveys](/docs/surveys/creating-surveys) that deploy instantly.

**Get unblocked by PostHog’s helpful sales and support teams**, ensuring you get the insights and information you need quickly.
```

Let's try paras until web folks can look at the spacing issue. May switch back if we decide it looks worse. 
created_at: 2025-04-11T10:29:13Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,132 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and simple integration gets you everything you need to build great products.
+
+But if you're already leaning on another tool, switching can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+***
+
+## Advantages for everyone
+
+PostHog is one login and one bill.
+
+This means less headache for more power, with all your data available across a range of products that help you understand user behavior as it happens.
+
+You'll get a responsive team that cares about user needs, delivering on customer feedback constantly.
+
+PostHog is completely agnostic to the language, framework, and stack you build your product with. You can adopt it incrementally, adding new functionality as needed.
+
+Best of all, PostHog is built so that you’ll actually enjoy using it. We really want you to have a good time.
+
+***
+
+## Persuading product teams
+
+PostHog gives product teams the power to understand users, improve adoption, and test assumptions. Once PostHog is in place, your product teammates can dive in immediately, with loads of power that doesn't require further engineering intervention.
+
+- **[Visualize anything](/docs/product-analytics/insights)** with charts, trend reporting, and [dashboards](/docs/product-analytics/dashboards) that are easy to build, but also deeply customizable for SQL enthusiasts.
+
+- **Learn anything you want** about everything the user touches in the product without manual instrumentation with [autocapture](/docs/product-analytics/autocapture).
+
+- **Get clarity about navigation** and user priorities with [heatmaps](/docs/toolbar/heatmaps).
+
+- Use [session replay](/docs/session-replay/installation) to **reveal bugs, expose friction, and help instantly answer questions** like “is this new design working?”
+
+- **Integrate revenue data** from [Stripe](/docs/cdp/sources/stripe) and other sources using data warehouse, so you can get a clear picture of what changes really move the needle.
+
+- **Send events and other details to any other tool**, powering automations and keeping data in sync, with setup you can accomplish in seconds, fully customizable for any API or webhook. [Data pipelines](/docs/cdp) makes it easy.
+
+- **Gather feedback and book user interviews** from exactly the users you want to reach with no-code [surveys](/docs/surveys/creating-surveys) that deploy instantly.
+
+- **Get unblocked by PostHog’s helpful sales and support teams,** ensuring you get the insights and information you need quickly.
+
+***
+
+## Good news for engineering teams
+
+PostHog is designed for developers.
+
+The project is [developed in the open](https://github.com/PostHog/posthog), with a [public roadmap](/roadmap) and [dozens of pull requests landing](https://github.com/PostHog/posthog/pulls?q=is%3Apr+is%3Aclosed) each week. While other products are low-velocity black boxes, we’re constantly making PostHog better.
+
+ We’ve got a dedicated technical staff standing by to help keep you on track. If you ever do need support, you’ll be talking to someone who knows the technical details of the product really well.
+
+Giving other teams the data they want becomes much easier with PostHog in the mix, lowering the burden on engineering. Once a basic integration is in place, there are loads of features everyone can use without a developer's intervention.
+
+- **Consolidate the tools your company needs**, with one login, one integration, one bill.
+
+- **[Get comprehensive documentation](/docs)** developers love for every every stack, framework, and language. You can also view [our source code directly](http://github.com/postHog/) if you can't find what you need. 
+
+- **Get a data platform that encourages tinkering**: if something doesn’t fit quite right for your team, it’s easy to customize everything from visualizations to integrations with other services. We'll host all these customizations for you. You don't need to worry about infrastructure or uptime.
+
+- **Integrating PostHog with other tools or even your own services is easy**, thanks to [data pipelines](/docs/cdp).
+
+- **Roll features out gradually** using [feature flags](/docs/feature-flags/creating-feature-flags) that are easy to target with fine-grained queries across everything PostHog knows about your users.
+
+We also care about the technical details of switching over. No matter your stack or existing tools, **complete integration and [migration docs](/docs/migration)** mean a clear path instead of a puzzle to solve. Our experienced Sales and CS team can even provide backup for more complex cases.
+
+***
+
+## Make the case to executives
+
+We’re in this for a long-term relationship, so **PostHog wants you to spend as little money as possible**. Our sales team actually works with customers to reduce bills and optimize consumption. Instead of sneaky billing, we’d prefer to make more money as a result of you winning more business.
+
+There’s just no sneaky stuff going on here. You can get started immediately with no shenanigans, no calls with the sales team if you don't want them.
+
+- **Your team will like PostHog**. It’s fresh, always getting fixes, improvements, and additional power. An investment in PostHog today means even more capabilities by next year.
+
+- **There's no per-seat charge**, so PostHog makes it easy for everyone on your team to make data-driven decisions. No matter how quickly you scale your team, your costs remain fixed to the actual usage of your product. 
+
+- **PostHog’s sales process is transparent and so is the whole company**: the company [handbook is public](/handbook), *even documenting the ways we can offer [discounts](/handbook/growth/sales/billing#coupons-and-discounts)*. Everything you want to know about pricing, processes, and our product is publicly documented.
+
+- **You can have a free trial** to fully vet the costs and impact of your integration. Trying PostHog is low-risk, no cost, and fully reversible.
+
+- **PostHog doesn’t require a contract**. You can save money with one, but it’s not a blocker to trying things out.
+
+***
+
+## Sharing social proof
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: andyvan-ph
body: I think this social proof would be way more powerful if they're embedded at the end of each of the above sections – i.e. each one would be social proof specific for that audience. At the moment, it's just feels a bit tacked on.
created_at: 2025-04-11T10:33:50Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,132 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and simple integration gets you everything you need to build great products.
+
+But if you're already leaning on another tool, switching can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+***
+
+## Advantages for everyone
+
+PostHog is one login and one bill.
+
+This means less headache for more power, with all your data available across a range of products that help you understand user behavior as it happens.
+
+You'll get a responsive team that cares about user needs, delivering on customer feedback constantly.
+
+PostHog is completely agnostic to the language, framework, and stack you build your product with. You can adopt it incrementally, adding new functionality as needed.
+
+Best of all, PostHog is built so that you’ll actually enjoy using it. We really want you to have a good time.
+
+***
+
+## Persuading product teams
+
+PostHog gives product teams the power to understand users, improve adoption, and test assumptions. Once PostHog is in place, your product teammates can dive in immediately, with loads of power that doesn't require further engineering intervention.
+
+- **[Visualize anything](/docs/product-analytics/insights)** with charts, trend reporting, and [dashboards](/docs/product-analytics/dashboards) that are easy to build, but also deeply customizable for SQL enthusiasts.
+
+- **Learn anything you want** about everything the user touches in the product without manual instrumentation with [autocapture](/docs/product-analytics/autocapture).
+
+- **Get clarity about navigation** and user priorities with [heatmaps](/docs/toolbar/heatmaps).
+
+- Use [session replay](/docs/session-replay/installation) to **reveal bugs, expose friction, and help instantly answer questions** like “is this new design working?”
+
+- **Integrate revenue data** from [Stripe](/docs/cdp/sources/stripe) and other sources using data warehouse, so you can get a clear picture of what changes really move the needle.
+
+- **Send events and other details to any other tool**, powering automations and keeping data in sync, with setup you can accomplish in seconds, fully customizable for any API or webhook. [Data pipelines](/docs/cdp) makes it easy.
+
+- **Gather feedback and book user interviews** from exactly the users you want to reach with no-code [surveys](/docs/surveys/creating-surveys) that deploy instantly.
+
+- **Get unblocked by PostHog’s helpful sales and support teams,** ensuring you get the insights and information you need quickly.
+
+***
+
+## Good news for engineering teams
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: andyvan-ph
body: ```suggestion
## Why your engineering teams will love PostHog
```

Open to other suggestions here, but I like the flow of a repeating format for these headings
created_at: 2025-04-11T10:46:24Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,132 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and simple integration gets you everything you need to build great products.
+
+But if you're already leaning on another tool, switching can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+***
+
+## Advantages for everyone
+
+PostHog is one login and one bill.
+
+This means less headache for more power, with all your data available across a range of products that help you understand user behavior as it happens.
+
+You'll get a responsive team that cares about user needs, delivering on customer feedback constantly.
+
+PostHog is completely agnostic to the language, framework, and stack you build your product with. You can adopt it incrementally, adding new functionality as needed.
+
+Best of all, PostHog is built so that you’ll actually enjoy using it. We really want you to have a good time.
+
+***
+
+## Persuading product teams
+
+PostHog gives product teams the power to understand users, improve adoption, and test assumptions. Once PostHog is in place, your product teammates can dive in immediately, with loads of power that doesn't require further engineering intervention.
+
+- **[Visualize anything](/docs/product-analytics/insights)** with charts, trend reporting, and [dashboards](/docs/product-analytics/dashboards) that are easy to build, but also deeply customizable for SQL enthusiasts.
+
+- **Learn anything you want** about everything the user touches in the product without manual instrumentation with [autocapture](/docs/product-analytics/autocapture).
+
+- **Get clarity about navigation** and user priorities with [heatmaps](/docs/toolbar/heatmaps).
+
+- Use [session replay](/docs/session-replay/installation) to **reveal bugs, expose friction, and help instantly answer questions** like “is this new design working?”
+
+- **Integrate revenue data** from [Stripe](/docs/cdp/sources/stripe) and other sources using data warehouse, so you can get a clear picture of what changes really move the needle.
+
+- **Send events and other details to any other tool**, powering automations and keeping data in sync, with setup you can accomplish in seconds, fully customizable for any API or webhook. [Data pipelines](/docs/cdp) makes it easy.
+
+- **Gather feedback and book user interviews** from exactly the users you want to reach with no-code [surveys](/docs/surveys/creating-surveys) that deploy instantly.
+
+- **Get unblocked by PostHog’s helpful sales and support teams,** ensuring you get the insights and information you need quickly.
+
+***
+
+## Good news for engineering teams
+
+PostHog is designed for developers.
+
+The project is [developed in the open](https://github.com/PostHog/posthog), with a [public roadmap](/roadmap) and [dozens of pull requests landing](https://github.com/PostHog/posthog/pulls?q=is%3Apr+is%3Aclosed) each week. While other products are low-velocity black boxes, we’re constantly making PostHog better.
+
+ We’ve got a dedicated technical staff standing by to help keep you on track. If you ever do need support, you’ll be talking to someone who knows the technical details of the product really well.
+
+Giving other teams the data they want becomes much easier with PostHog in the mix, lowering the burden on engineering. Once a basic integration is in place, there are loads of features everyone can use without a developer's intervention.
+
+- **Consolidate the tools your company needs**, with one login, one integration, one bill.
+
+- **[Get comprehensive documentation](/docs)** developers love for every every stack, framework, and language. You can also view [our source code directly](http://github.com/postHog/) if you can't find what you need. 
+
+- **Get a data platform that encourages tinkering**: if something doesn’t fit quite right for your team, it’s easy to customize everything from visualizations to integrations with other services. We'll host all these customizations for you. You don't need to worry about infrastructure or uptime.
+
+- **Integrating PostHog with other tools or even your own services is easy**, thanks to [data pipelines](/docs/cdp).
+
+- **Roll features out gradually** using [feature flags](/docs/feature-flags/creating-feature-flags) that are easy to target with fine-grained queries across everything PostHog knows about your users.
+
+We also care about the technical details of switching over. No matter your stack or existing tools, **complete integration and [migration docs](/docs/migration)** mean a clear path instead of a puzzle to solve. Our experienced Sales and CS team can even provide backup for more complex cases.
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: andyvan-ph
body: ```suggestion
**Consolidate the tools your company needs**, with one login, one integration, one bill.

**Comprehensive documentation** developers love for every every stack, framework, and language. You can also view [our source code directly](http://github.com/postHog/) if you can't find what you need. 

**Get a data platform that encourages tinkering**: if something doesn’t fit quite right for your team, it’s easy to customize everything. We'll host all these customizations for you. You don't need to worry about infrastructure or uptime.

**Integrating PostHog with other tools or even your own services is easy**, thanks to [data pipelines](/docs/cdp).

**Roll features out gradually** using [feature flags](/docs/feature-flags/creating-feature-flags) that are easy to target with fine-grained queries across everything PostHog knows about your users.

We also care about the technical details of switching over. 

No matter your stack or existing tools, **complete integration and [migration docs](/docs/migration)** mean a clear path instead of a puzzle to solve. Our experienced Sales and CS team can even provide backup for more complex cases.
```
created_at: 2025-04-11T10:51:56Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,132 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and simple integration gets you everything you need to build great products.
+
+But if you're already leaning on another tool, switching can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+***
+
+## Advantages for everyone
+
+PostHog is one login and one bill.
+
+This means less headache for more power, with all your data available across a range of products that help you understand user behavior as it happens.
+
+You'll get a responsive team that cares about user needs, delivering on customer feedback constantly.
+
+PostHog is completely agnostic to the language, framework, and stack you build your product with. You can adopt it incrementally, adding new functionality as needed.
+
+Best of all, PostHog is built so that you’ll actually enjoy using it. We really want you to have a good time.
+
+***
+
+## Persuading product teams
+
+PostHog gives product teams the power to understand users, improve adoption, and test assumptions. Once PostHog is in place, your product teammates can dive in immediately, with loads of power that doesn't require further engineering intervention.
+
+- **[Visualize anything](/docs/product-analytics/insights)** with charts, trend reporting, and [dashboards](/docs/product-analytics/dashboards) that are easy to build, but also deeply customizable for SQL enthusiasts.
+
+- **Learn anything you want** about everything the user touches in the product without manual instrumentation with [autocapture](/docs/product-analytics/autocapture).
+
+- **Get clarity about navigation** and user priorities with [heatmaps](/docs/toolbar/heatmaps).
+
+- Use [session replay](/docs/session-replay/installation) to **reveal bugs, expose friction, and help instantly answer questions** like “is this new design working?”
+
+- **Integrate revenue data** from [Stripe](/docs/cdp/sources/stripe) and other sources using data warehouse, so you can get a clear picture of what changes really move the needle.
+
+- **Send events and other details to any other tool**, powering automations and keeping data in sync, with setup you can accomplish in seconds, fully customizable for any API or webhook. [Data pipelines](/docs/cdp) makes it easy.
+
+- **Gather feedback and book user interviews** from exactly the users you want to reach with no-code [surveys](/docs/surveys/creating-surveys) that deploy instantly.
+
+- **Get unblocked by PostHog’s helpful sales and support teams,** ensuring you get the insights and information you need quickly.
+
+***
+
+## Good news for engineering teams
+
+PostHog is designed for developers.
+
+The project is [developed in the open](https://github.com/PostHog/posthog), with a [public roadmap](/roadmap) and [dozens of pull requests landing](https://github.com/PostHog/posthog/pulls?q=is%3Apr+is%3Aclosed) each week. While other products are low-velocity black boxes, we’re constantly making PostHog better.
+
+ We’ve got a dedicated technical staff standing by to help keep you on track. If you ever do need support, you’ll be talking to someone who knows the technical details of the product really well.
+
+Giving other teams the data they want becomes much easier with PostHog in the mix, lowering the burden on engineering. Once a basic integration is in place, there are loads of features everyone can use without a developer's intervention.
+
+- **Consolidate the tools your company needs**, with one login, one integration, one bill.
+
+- **[Get comprehensive documentation](/docs)** developers love for every every stack, framework, and language. You can also view [our source code directly](http://github.com/postHog/) if you can't find what you need. 
+
+- **Get a data platform that encourages tinkering**: if something doesn’t fit quite right for your team, it’s easy to customize everything from visualizations to integrations with other services. We'll host all these customizations for you. You don't need to worry about infrastructure or uptime.
+
+- **Integrating PostHog with other tools or even your own services is easy**, thanks to [data pipelines](/docs/cdp).
+
+- **Roll features out gradually** using [feature flags](/docs/feature-flags/creating-feature-flags) that are easy to target with fine-grained queries across everything PostHog knows about your users.
+
+We also care about the technical details of switching over. No matter your stack or existing tools, **complete integration and [migration docs](/docs/migration)** mean a clear path instead of a puzzle to solve. Our experienced Sales and CS team can even provide backup for more complex cases.
+
+***
+
+## Make the case to executives
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: andyvan-ph
body: ```suggestion
## Why your exec team will love PostHog
```
created_at: 2025-04-11T10:53:33Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,132 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and simple integration gets you everything you need to build great products.
+
+But if you're already leaning on another tool, switching can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+***
+
+## Advantages for everyone
+
+PostHog is one login and one bill.
+
+This means less headache for more power, with all your data available across a range of products that help you understand user behavior as it happens.
+
+You'll get a responsive team that cares about user needs, delivering on customer feedback constantly.
+
+PostHog is completely agnostic to the language, framework, and stack you build your product with. You can adopt it incrementally, adding new functionality as needed.
+
+Best of all, PostHog is built so that you’ll actually enjoy using it. We really want you to have a good time.
+
+***
+
+## Persuading product teams
+
+PostHog gives product teams the power to understand users, improve adoption, and test assumptions. Once PostHog is in place, your product teammates can dive in immediately, with loads of power that doesn't require further engineering intervention.
+
+- **[Visualize anything](/docs/product-analytics/insights)** with charts, trend reporting, and [dashboards](/docs/product-analytics/dashboards) that are easy to build, but also deeply customizable for SQL enthusiasts.
+
+- **Learn anything you want** about everything the user touches in the product without manual instrumentation with [autocapture](/docs/product-analytics/autocapture).
+
+- **Get clarity about navigation** and user priorities with [heatmaps](/docs/toolbar/heatmaps).
+
+- Use [session replay](/docs/session-replay/installation) to **reveal bugs, expose friction, and help instantly answer questions** like “is this new design working?”
+
+- **Integrate revenue data** from [Stripe](/docs/cdp/sources/stripe) and other sources using data warehouse, so you can get a clear picture of what changes really move the needle.
+
+- **Send events and other details to any other tool**, powering automations and keeping data in sync, with setup you can accomplish in seconds, fully customizable for any API or webhook. [Data pipelines](/docs/cdp) makes it easy.
+
+- **Gather feedback and book user interviews** from exactly the users you want to reach with no-code [surveys](/docs/surveys/creating-surveys) that deploy instantly.
+
+- **Get unblocked by PostHog’s helpful sales and support teams,** ensuring you get the insights and information you need quickly.
+
+***
+
+## Good news for engineering teams
+
+PostHog is designed for developers.
+
+The project is [developed in the open](https://github.com/PostHog/posthog), with a [public roadmap](/roadmap) and [dozens of pull requests landing](https://github.com/PostHog/posthog/pulls?q=is%3Apr+is%3Aclosed) each week. While other products are low-velocity black boxes, we’re constantly making PostHog better.
+
+ We’ve got a dedicated technical staff standing by to help keep you on track. If you ever do need support, you’ll be talking to someone who knows the technical details of the product really well.
+
+Giving other teams the data they want becomes much easier with PostHog in the mix, lowering the burden on engineering. Once a basic integration is in place, there are loads of features everyone can use without a developer's intervention.
+
+- **Consolidate the tools your company needs**, with one login, one integration, one bill.
+
+- **[Get comprehensive documentation](/docs)** developers love for every every stack, framework, and language. You can also view [our source code directly](http://github.com/postHog/) if you can't find what you need. 
+
+- **Get a data platform that encourages tinkering**: if something doesn’t fit quite right for your team, it’s easy to customize everything from visualizations to integrations with other services. We'll host all these customizations for you. You don't need to worry about infrastructure or uptime.
+
+- **Integrating PostHog with other tools or even your own services is easy**, thanks to [data pipelines](/docs/cdp).
+
+- **Roll features out gradually** using [feature flags](/docs/feature-flags/creating-feature-flags) that are easy to target with fine-grained queries across everything PostHog knows about your users.
+
+We also care about the technical details of switching over. No matter your stack or existing tools, **complete integration and [migration docs](/docs/migration)** mean a clear path instead of a puzzle to solve. Our experienced Sales and CS team can even provide backup for more complex cases.
+
+***
+
+## Make the case to executives
+
+We’re in this for a long-term relationship, so **PostHog wants you to spend as little money as possible**. Our sales team actually works with customers to reduce bills and optimize consumption. Instead of sneaky billing, we’d prefer to make more money as a result of you winning more business.
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: andyvan-ph
body: ```suggestion
We’re in this for a long-term relationship, so **PostHog wants you to spend as little money as possible**. 

Our sales team actually works with customers to reduce bills and optimize consumption. Instead of sneaky billing, we’d prefer to make more money as a result of you winning more business.
```
created_at: 2025-04-11T10:53:45Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,132 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and simple integration gets you everything you need to build great products.
+
+But if you're already leaning on another tool, switching can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+***
+
+## Advantages for everyone
+
+PostHog is one login and one bill.
+
+This means less headache for more power, with all your data available across a range of products that help you understand user behavior as it happens.
+
+You'll get a responsive team that cares about user needs, delivering on customer feedback constantly.
+
+PostHog is completely agnostic to the language, framework, and stack you build your product with. You can adopt it incrementally, adding new functionality as needed.
+
+Best of all, PostHog is built so that you’ll actually enjoy using it. We really want you to have a good time.
+
+***
+
+## Persuading product teams
+
+PostHog gives product teams the power to understand users, improve adoption, and test assumptions. Once PostHog is in place, your product teammates can dive in immediately, with loads of power that doesn't require further engineering intervention.
+
+- **[Visualize anything](/docs/product-analytics/insights)** with charts, trend reporting, and [dashboards](/docs/product-analytics/dashboards) that are easy to build, but also deeply customizable for SQL enthusiasts.
+
+- **Learn anything you want** about everything the user touches in the product without manual instrumentation with [autocapture](/docs/product-analytics/autocapture).
+
+- **Get clarity about navigation** and user priorities with [heatmaps](/docs/toolbar/heatmaps).
+
+- Use [session replay](/docs/session-replay/installation) to **reveal bugs, expose friction, and help instantly answer questions** like “is this new design working?”
+
+- **Integrate revenue data** from [Stripe](/docs/cdp/sources/stripe) and other sources using data warehouse, so you can get a clear picture of what changes really move the needle.
+
+- **Send events and other details to any other tool**, powering automations and keeping data in sync, with setup you can accomplish in seconds, fully customizable for any API or webhook. [Data pipelines](/docs/cdp) makes it easy.
+
+- **Gather feedback and book user interviews** from exactly the users you want to reach with no-code [surveys](/docs/surveys/creating-surveys) that deploy instantly.
+
+- **Get unblocked by PostHog’s helpful sales and support teams,** ensuring you get the insights and information you need quickly.
+
+***
+
+## Good news for engineering teams
+
+PostHog is designed for developers.
+
+The project is [developed in the open](https://github.com/PostHog/posthog), with a [public roadmap](/roadmap) and [dozens of pull requests landing](https://github.com/PostHog/posthog/pulls?q=is%3Apr+is%3Aclosed) each week. While other products are low-velocity black boxes, we’re constantly making PostHog better.
+
+ We’ve got a dedicated technical staff standing by to help keep you on track. If you ever do need support, you’ll be talking to someone who knows the technical details of the product really well.
+
+Giving other teams the data they want becomes much easier with PostHog in the mix, lowering the burden on engineering. Once a basic integration is in place, there are loads of features everyone can use without a developer's intervention.
+
+- **Consolidate the tools your company needs**, with one login, one integration, one bill.
+
+- **[Get comprehensive documentation](/docs)** developers love for every every stack, framework, and language. You can also view [our source code directly](http://github.com/postHog/) if you can't find what you need. 
+
+- **Get a data platform that encourages tinkering**: if something doesn’t fit quite right for your team, it’s easy to customize everything from visualizations to integrations with other services. We'll host all these customizations for you. You don't need to worry about infrastructure or uptime.
+
+- **Integrating PostHog with other tools or even your own services is easy**, thanks to [data pipelines](/docs/cdp).
+
+- **Roll features out gradually** using [feature flags](/docs/feature-flags/creating-feature-flags) that are easy to target with fine-grained queries across everything PostHog knows about your users.
+
+We also care about the technical details of switching over. No matter your stack or existing tools, **complete integration and [migration docs](/docs/migration)** mean a clear path instead of a puzzle to solve. Our experienced Sales and CS team can even provide backup for more complex cases.
+
+***
+
+## Make the case to executives
+
+We’re in this for a long-term relationship, so **PostHog wants you to spend as little money as possible**. Our sales team actually works with customers to reduce bills and optimize consumption. Instead of sneaky billing, we’d prefer to make more money as a result of you winning more business.
+
+There’s just no sneaky stuff going on here. You can get started immediately with no shenanigans, no calls with the sales team if you don't want them.
+
+- **Your team will like PostHog**. It’s fresh, always getting fixes, improvements, and additional power. An investment in PostHog today means even more capabilities by next year.
+
+- **There's no per-seat charge**, so PostHog makes it easy for everyone on your team to make data-driven decisions. No matter how quickly you scale your team, your costs remain fixed to the actual usage of your product. 
+
+- **PostHog’s sales process is transparent and so is the whole company**: the company [handbook is public](/handbook), *even documenting the ways we can offer [discounts](/handbook/growth/sales/billing#coupons-and-discounts)*. Everything you want to know about pricing, processes, and our product is publicly documented.
+
+- **You can have a free trial** to fully vet the costs and impact of your integration. Trying PostHog is low-risk, no cost, and fully reversible.
+
+- **PostHog doesn’t require a contract**. You can save money with one, but it’s not a blocker to trying things out.
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: andyvan-ph
body: ```suggestion
**Your team will like PostHog**. It’s fresh, always getting fixes, improvements, and additional power. An investment in PostHog today means even more capabilities by next year.

**There's no per-seat charge**, so PostHog makes it easy for everyone on your team to make data-driven decisions. No matter how quickly you scale your team, your costs remain fixed to the actual usage of your product. 

**PostHog’s sales process is transparent and so is the whole company**: the company [handbook is public](/handbook), *even documenting the ways we can offer [discounts](/handbook/growth/sales/billing#coupons-and-discounts)*. Everything you want to know about pricing, processes, and our product is publicly documented.

**You can have a free trial** to fully vet the costs and impact of your integration. Trying PostHog is low-risk, no cost, and fully reversible.

**PostHog doesn’t require a contract**. You can save money with one, but it’s not a blocker to trying things out.
```
created_at: 2025-04-11T10:54:21Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,71 @@
+---
+title: Planning your pilot
+nextPage: ./migration-planning.mdx
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+We want you to love using PostHog. We’ve worked hard to craft a tool that can make you much more effective at giving your customers what they want.
path: contents/docs/new-to-posthog/switch-guide/planning-your-pilot.mdx
user: login: andyvan-ph
body: ```suggestion
We want you to love using PostHog. 

We’ve worked hard to craft a tool that can make you much more effective at giving your customers what they want.
```
created_at: 2025-04-11T11:01:48Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,71 @@
+---
+title: Planning your pilot
+nextPage: ./migration-planning.mdx
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+We want you to love using PostHog. We’ve worked hard to craft a tool that can make you much more effective at giving your customers what they want.
+
+Here's how to get the most out of a pilot test with your team.
+
+## Invite the people who care about user behavior, no matter their role
path: contents/docs/new-to-posthog/switch-guide/planning-your-pilot.mdx
user: login: andyvan-ph
body: ```suggestion
## Invite anyone who cares about user behavior
```
created_at: 2025-04-11T11:04:02Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,71 @@
+---
+title: Planning your pilot
+nextPage: ./migration-planning.mdx
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+We want you to love using PostHog. We’ve worked hard to craft a tool that can make you much more effective at giving your customers what they want.
+
+Here's how to get the most out of a pilot test with your team.
+
+## Invite the people who care about user behavior, no matter their role
+
+PostHog charges by how successful your product is, not how many people have a login.
+
+That means anyone and everyone on your crew can explore at no extra cost. As your integration comes online, think about who else you’d like to invite. You'll have the option to invite them during setup, and any time after that.
path: contents/docs/new-to-posthog/switch-guide/planning-your-pilot.mdx
user: login: andyvan-ph
body: ```suggestion
It doesn't matter what their specific role is. We charge by how successful your product is, not how many people have a login. We're building a product everyone will find useful.

That means anyone and everyone on your crew can explore at no extra cost. As your integration comes online, think about who else you’d like to invite. You'll have the option to invite them during setup, and any time after that.
```
created_at: 2025-04-11T11:04:49Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,71 @@
+---
+title: Planning your pilot
+nextPage: ./migration-planning.mdx
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+We want you to love using PostHog. We’ve worked hard to craft a tool that can make you much more effective at giving your customers what they want.
+
+Here's how to get the most out of a pilot test with your team.
+
+## Invite the people who care about user behavior, no matter their role
+
+PostHog charges by how successful your product is, not how many people have a login.
+
+That means anyone and everyone on your crew can explore at no extra cost. As your integration comes online, think about who else you’d like to invite. You'll have the option to invite them during setup, and any time after that.
+
+## Get help if you want it
path: contents/docs/new-to-posthog/switch-guide/planning-your-pilot.mdx
user: login: andyvan-ph
body: ```suggestion
## Ask for help if you want it
```
created_at: 2025-04-11T11:04:58Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,71 @@
+---
+title: Planning your pilot
+nextPage: ./migration-planning.mdx
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+We want you to love using PostHog. We’ve worked hard to craft a tool that can make you much more effective at giving your customers what they want.
+
+Here's how to get the most out of a pilot test with your team.
+
+## Invite the people who care about user behavior, no matter their role
+
+PostHog charges by how successful your product is, not how many people have a login.
+
+That means anyone and everyone on your crew can explore at no extra cost. As your integration comes online, think about who else you’d like to invite. You'll have the option to invite them during setup, and any time after that.
+
+## Get help if you want it
+
+For companies sized 25 and up, [we’ve got a team](/talk-to-a-human) who can answer questions and help you make a plan.
+
+But only if you want the help! They’re not going to pressure you or do anything corny, but their integration experience can save time and trouble. They can also help you map PostHog features to your business goals, developing a useful mental model for using all our products.
+
+But we’re not going to get in your way, either, because…
path: contents/docs/new-to-posthog/switch-guide/planning-your-pilot.mdx
user: login: andyvan-ph
body: ```suggestion
But we’re not going to get in your way, either, because...
```
created_at: 2025-04-11T11:06:29Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,71 @@
+---
+title: Planning your pilot
+nextPage: ./migration-planning.mdx
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+We want you to love using PostHog. We’ve worked hard to craft a tool that can make you much more effective at giving your customers what they want.
+
+Here's how to get the most out of a pilot test with your team.
+
+## Invite the people who care about user behavior, no matter their role
+
+PostHog charges by how successful your product is, not how many people have a login.
+
+That means anyone and everyone on your crew can explore at no extra cost. As your integration comes online, think about who else you’d like to invite. You'll have the option to invite them during setup, and any time after that.
+
+## Get help if you want it
+
+For companies sized 25 and up, [we’ve got a team](/talk-to-a-human) who can answer questions and help you make a plan.
+
+But only if you want the help! They’re not going to pressure you or do anything corny, but their integration experience can save time and trouble. They can also help you map PostHog features to your business goals, developing a useful mental model for using all our products.
+
+But we’re not going to get in your way, either, because…
+
+## We want you to play around
+
+The most important job is getting familiar with PostHog in whatever way makes you most comfortable. The most basic integration takes 5 minutes and we’ve got loads of documentation to support you exploring on your own.
path: contents/docs/new-to-posthog/switch-guide/planning-your-pilot.mdx
user: login: andyvan-ph
body: ```suggestion
The most important job is getting familiar with PostHog in whatever way makes you most comfortable. 

The most [basic integration takes 5 minutes](/docs/getting-started/install?tab=snippet) and we’ve got loads of documentation to support you exploring on your own.
```
created_at: 2025-04-11T11:07:13Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,71 @@
+---
+title: Planning your pilot
+nextPage: ./migration-planning.mdx
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+We want you to love using PostHog. We’ve worked hard to craft a tool that can make you much more effective at giving your customers what they want.
+
+Here's how to get the most out of a pilot test with your team.
+
+## Invite the people who care about user behavior, no matter their role
+
+PostHog charges by how successful your product is, not how many people have a login.
+
+That means anyone and everyone on your crew can explore at no extra cost. As your integration comes online, think about who else you’d like to invite. You'll have the option to invite them during setup, and any time after that.
+
+## Get help if you want it
+
+For companies sized 25 and up, [we’ve got a team](/talk-to-a-human) who can answer questions and help you make a plan.
+
+But only if you want the help! They’re not going to pressure you or do anything corny, but their integration experience can save time and trouble. They can also help you map PostHog features to your business goals, developing a useful mental model for using all our products.
+
+But we’re not going to get in your way, either, because…
+
+## We want you to play around
+
+The most important job is getting familiar with PostHog in whatever way makes you most comfortable. The most basic integration takes 5 minutes and we’ve got loads of documentation to support you exploring on your own.
+
+## First two weeks: get data in, then look at it
+
+Job one is making sure PostHog is reliably ingesting your data and reporting the basics in a dashboard. Once this is working, take a break, order a pizza[^1].
+
+From here, you can get more sophisticated:
+
+- **Decide**: Your [North Star metric](/docs/new-to-posthog/getting-hogpilled)  
+- **Decide**: Make an event tracking plan, or rely on autocapture?  
+- **Decide**: Use [identified or anonymous events](/docs/data/anonymous-vs-identified-events)?  
+- Configure a [reverse proxy](/docs/advanced/proxy) to improve reliability of event capture  
+- Experiment with measuring [activation](/docs/new-to-posthog/activation) and [retention](/docs/new-to-posthog/retention)  
+- [Watch some session replays](https://app.posthog.com/project/replay/home), see what you can learn  
+- Try out a [no-code survey](/docs/surveys/creating-surveys) to learn what customers are feeling about your product
+- Fire up [web analytics](/docs/web-analytics/getting-started), see if you like it better than your existing provider
+
+After two weeks to explore, check in with your teammates as well. See if there’s anything they want but aren't getting. If you can get them excited with you, you'll have a better chance of making this pilot turn into a full-on switch.
path: contents/docs/new-to-posthog/switch-guide/planning-your-pilot.mdx
user: login: andyvan-ph
body: Could we split off the things you need to decide into their own headed section and add a bit more context? We don't need anything super in-depth, just a bit more meat on what you should decide these things and the implications. We could even have some recommendations – e.g. on anon vs identified users, the default setting is probably fine for *most* use cases, right?

My core thing about this page I find hard is I instinctively feel like I want a more opinionated take on the timeline here. For example: 
- When should someone start inviting people? Is this the first thing you do after a basic integration, or should you setup some basic stuff (like a dashboard or two), so people have something to play with?
- Do we really need to decide on a north star early on? If so, does this come before or after setting up a reverse proxy?

In the interests of shipping a V1 this is ok atm, but I think we should explore a format that's more like:

- Things you should do one day 1
- Things you should do in the first week
- Things you need to decide in the first two weeks
- Common problems people run into and what to do about them

Right now, we call this "Planning your pilot" but this page isn't structured like a plan, it's more like a series of things you need to think about, which feels more stressful than "here's a structured plan you can just follow step-by-step".

Obviously there needs to be flexibility, but I think people will have a better experience if we give them an opinionated take on what to do and when, which they can tweak.


created_at: 2025-04-11T11:43:25Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,91 @@
+---
+title: What to expect as you migrate
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+With your team onboarded and a successful pilot completed, you can turn your attention to **planning your migration**.
+
+***
path: contents/docs/new-to-posthog/switch-guide/migration-planning.mdx
user: login: andyvan-ph
body: ```suggestion
```
created_at: 2025-04-11T11:53:49Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,91 @@
+---
+title: What to expect as you migrate
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+With your team onboarded and a successful pilot completed, you can turn your attention to **planning your migration**.
+
+***
+
+## Technical planning
+
+PostHog provides tools and guides to support you making this switch. Check out our [migration docs](/docs/migrate) for details on moving from [Amplitude](/docs/migrate/migrate-from-amplitude), [Mixpanel](/docs/migrate/mixpanel), [LaunchDarkly](/docs/migrate/launchdarkly) and others.
+
+Stumped on any detail of the process? If you’ve already signed up and started sending events with a forecasted bill of $500 or more, our **onboarding** team will reach out to help. If you haven’t heard from us yet, [drop us a line](/talk-to-a-human) with your migration questions!
path: contents/docs/new-to-posthog/switch-guide/migration-planning.mdx
user: login: andyvan-ph
body: ```suggestion
Stumped on any detail of the process? If you’ve already signed up and started sending events with a forecasted bill of $500 or more, our **onboarding** team will reach out to help. 

If you haven’t heard from us yet, [drop us a line](/talk-to-a-human) with your migration questions!
```
created_at: 2025-04-11T11:54:13Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,91 @@
+---
+title: What to expect as you migrate
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+With your team onboarded and a successful pilot completed, you can turn your attention to **planning your migration**.
+
+***
+
+## Technical planning
+
+PostHog provides tools and guides to support you making this switch. Check out our [migration docs](/docs/migrate) for details on moving from [Amplitude](/docs/migrate/migrate-from-amplitude), [Mixpanel](/docs/migrate/mixpanel), [LaunchDarkly](/docs/migrate/launchdarkly) and others.
+
+Stumped on any detail of the process? If you’ve already signed up and started sending events with a forecasted bill of $500 or more, our **onboarding** team will reach out to help. If you haven’t heard from us yet, [drop us a line](/talk-to-a-human) with your migration questions!
+
+<CalloutBox icon="IconWarning" title="Avoid common setup pitfalls" type="caution">
+
+Don’t create separate projects for mobile and web. PostHog works best when you can see user behavior across all versions of your products in one set of data and views.
+
+Healthy integrations have a few things in common. It can help to review the [health check](/handbook/growth/sales/health-checks) documentation used by our sales team to tackle the most common ways to keep your bill manageable and predictable.
+
+If your historical data is above 100 GB or 200 million events, you should [reach out to our sales team](/talk-to-a-human) or [open a support ticket](/docs/support-options) so we can make sure everything imports smoothly.
+
+</CalloutBox>
path: contents/docs/new-to-posthog/switch-guide/migration-planning.mdx
user: login: andyvan-ph
body: A couple of important setup traps to avoid here:

1. Don’t create separate projects for mobile and web. PostHog works best when you can see user behavior across all versions of your products in one set of data and views.

2. Healthy integrations have a few things in common. It can help to review the [health check](/handbook/growth/sales/health-checks) documentation used by our sales team to tackle the most common ways to keep your bill manageable and predictable.

```suggestion
<CalloutBox icon="IconWarning" title="When to talk to us about your migration" type="caution">

If your historical data is above 100 GB or 200 million events, you should [reach out to our sales team](/talk-to-a-human) or [open a support ticket](/docs/support-options) so we can make sure everything imports smoothly.

</CalloutBox>
```

This last point is pretty important, so I think it's better to have that in the callout and split out the rest. It's also just a lot of stuff to have in a "caution".
created_at: 2025-04-11T11:59:08Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,91 @@
+---
+title: What to expect as you migrate
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+With your team onboarded and a successful pilot completed, you can turn your attention to **planning your migration**.
+
+***
+
+## Technical planning
+
+PostHog provides tools and guides to support you making this switch. Check out our [migration docs](/docs/migrate) for details on moving from [Amplitude](/docs/migrate/migrate-from-amplitude), [Mixpanel](/docs/migrate/mixpanel), [LaunchDarkly](/docs/migrate/launchdarkly) and others.
+
+Stumped on any detail of the process? If you’ve already signed up and started sending events with a forecasted bill of $500 or more, our **onboarding** team will reach out to help. If you haven’t heard from us yet, [drop us a line](/talk-to-a-human) with your migration questions!
+
+<CalloutBox icon="IconWarning" title="Avoid common setup pitfalls" type="caution">
+
+Don’t create separate projects for mobile and web. PostHog works best when you can see user behavior across all versions of your products in one set of data and views.
+
+Healthy integrations have a few things in common. It can help to review the [health check](/handbook/growth/sales/health-checks) documentation used by our sales team to tackle the most common ways to keep your bill manageable and predictable.
+
+If your historical data is above 100 GB or 200 million events, you should [reach out to our sales team](/talk-to-a-human) or [open a support ticket](/docs/support-options) so we can make sure everything imports smoothly.
+
+</CalloutBox>
+
+### Reducing disruption for your teammates
+
+New software can take a moment to click. One way to help your teammates get comfortable is making sure vital numbers are already waiting in your new PostHog setup.
+
+To support this, it can help to make a spreadsheet for people to request their most essential metrics. Use it to create insights in PostHog, then link them in the spreadsheet.
+
+You want to know what data your teammates need to keep making good decisions, and ensure those metrics are easy to find in PostHog. Capturing these requirements can also help you check that your technical implementation is capturing all necessary events and properties.
+
+While moving historical events over is straightforward, you’ll need plan for some time rebuilding the views and dashboards your team relies on.
+
+### Conversion tracking
+
+An urgent need from marketing and product teams is **tracking conversions**. Getting clear on how to do this in PostHog can reduce frustration as everyone settles in. These docs on using **[funnels](/docs/product-analytics/funnels)** are a great starting point for this kind of reporting.
+
+***
+
+## Providing demos
path: contents/docs/new-to-posthog/switch-guide/migration-planning.mdx
user: login: andyvan-ph
body: Not important for shipping V1, but I think "How to demo to your teammates" might better as it's own page. More than half this is page is about this, rather than the nuts and bolts of migrating. It get they're related, but as we build this out I think we can split them up.
created_at: 2025-04-11T12:04:50Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,91 @@
+---
+title: What to expect as you migrate
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+With your team onboarded and a successful pilot completed, you can turn your attention to **planning your migration**.
+
+***
+
+## Technical planning
+
+PostHog provides tools and guides to support you making this switch. Check out our [migration docs](/docs/migrate) for details on moving from [Amplitude](/docs/migrate/migrate-from-amplitude), [Mixpanel](/docs/migrate/mixpanel), [LaunchDarkly](/docs/migrate/launchdarkly) and others.
+
+Stumped on any detail of the process? If you’ve already signed up and started sending events with a forecasted bill of $500 or more, our **onboarding** team will reach out to help. If you haven’t heard from us yet, [drop us a line](/talk-to-a-human) with your migration questions!
+
+<CalloutBox icon="IconWarning" title="Avoid common setup pitfalls" type="caution">
+
+Don’t create separate projects for mobile and web. PostHog works best when you can see user behavior across all versions of your products in one set of data and views.
+
+Healthy integrations have a few things in common. It can help to review the [health check](/handbook/growth/sales/health-checks) documentation used by our sales team to tackle the most common ways to keep your bill manageable and predictable.
+
+If your historical data is above 100 GB or 200 million events, you should [reach out to our sales team](/talk-to-a-human) or [open a support ticket](/docs/support-options) so we can make sure everything imports smoothly.
+
+</CalloutBox>
+
+### Reducing disruption for your teammates
+
+New software can take a moment to click. One way to help your teammates get comfortable is making sure vital numbers are already waiting in your new PostHog setup.
+
+To support this, it can help to make a spreadsheet for people to request their most essential metrics. Use it to create insights in PostHog, then link them in the spreadsheet.
+
+You want to know what data your teammates need to keep making good decisions, and ensure those metrics are easy to find in PostHog. Capturing these requirements can also help you check that your technical implementation is capturing all necessary events and properties.
+
+While moving historical events over is straightforward, you’ll need plan for some time rebuilding the views and dashboards your team relies on.
+
+### Conversion tracking
+
+An urgent need from marketing and product teams is **tracking conversions**. Getting clear on how to do this in PostHog can reduce frustration as everyone settles in. These docs on using **[funnels](/docs/product-analytics/funnels)** are a great starting point for this kind of reporting.
+
+***
+
+## Providing demos
+
+A great way to help PostHog land well is to offer a quick demo to everyone who’s interested.
+
+Here are some topics that might be worth covering. You know your teammates best, so be sure to adjust your demos to their needs and interests.
+
+### Events, persons, properties, and the activity view
+
+![The activity explorer](https://res.cloudinary.com/dmukukwp6/image/upload/activity_2923c81b32.png)
+
+Events are the core of PostHog’s reporting. Explain how they work, and the properties you plan to attach to them as part of your integration. Show off the **[activity](https://app.posthog.com/project/activity/explore)** view so everyone can see new events pouring in. 
+
+If you’re identifying users in your integration, showing how **[person profiles](https://app.posthog.com/project/persons)** collect information can also be helpful.
+
+### Web analytics
+
+Everyone who wants the basics of an analytics dashboard will find it in our **[web analytics](https://app.posthog.com/project/web)** tab right out of the box.
+
+### Actions
+
+Actions let you group and rename events, making them easier to use in reporting. The more your teammates understand actions, the easier everyone’s life gets to be, so take a moment in **[data management](https://app.posthog.com/project/data-management/actions)** to explain.
+
+### Creating insights and dashboards
+
+Creating, editing, and duplicating [insights](/docs/product-analytics/insights) is fast and easy, and so is adding these to dashboards. Make sure to give this part of the demo plenty of detail: playing with data is a big part of what makes PostHog fun. This is also a great time to explore **filters**, which are a common need.
+
+Popular insights include:
+
+- Trends: show change over time  
+- Funnels: track conversions and other sequential activity  
+- User paths: see how real people explore your sight
+
+### Replays
+
+[Replays](https://app.posthog.com/project/replay/home) are a hit across roles and teams. For engineers, they can be a way of catching layout problems and other bugs early. For product and design, they’re a way to make sure that new features and workflows are actually performing correctly. They’re a huge help to support, and even execs enjoy flipping through them.
+
+### Instant, no-code surveys
+
+If you’re talking to someone who really wants to hear from customers, [surveys](https://app.posthog.com/project/surveys) are going to be exciting. Walk through how to design and deploy one.
+
+### Toolbar
+
+This one is a visual crowd pleaser: launch your site’s PostHog [toolbar](https://app.posthog.com/project/toolbar) to show heatmap overlays and other stats directly on your site. You can even use it to launch [hedgehog mode](/blog/aruba-hackathon#hedgehog-mode--toolbar--awesomeness).
+
+***
+
+## Get more help
+
+Again, we’ve got your back here. We never want to waste your time with a call, so a self-serve migration is an open invitation. But if any part of this feels more daunting than fun, just [get in touch](/talk-to-a-human). We’re able to help accounts with $500 in projected monthly spending with onboarding, along with ongoing support for companies 25 people and up.
path: contents/docs/new-to-posthog/switch-guide/migration-planning.mdx
user: login: andyvan-ph
body: change this to a callout box at the end? I think it would look neater.
created_at: 2025-04-11T12:05:38Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,91 @@
+---
+title: What to expect as you migrate
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+With your team onboarded and a successful pilot completed, you can turn your attention to **planning your migration**.
+
+***
+
+## Technical planning
+
+PostHog provides tools and guides to support you making this switch. Check out our [migration docs](/docs/migrate) for details on moving from [Amplitude](/docs/migrate/migrate-from-amplitude), [Mixpanel](/docs/migrate/mixpanel), [LaunchDarkly](/docs/migrate/launchdarkly) and others.
+
+Stumped on any detail of the process? If you’ve already signed up and started sending events with a forecasted bill of $500 or more, our **onboarding** team will reach out to help. If you haven’t heard from us yet, [drop us a line](/talk-to-a-human) with your migration questions!
+
+<CalloutBox icon="IconWarning" title="Avoid common setup pitfalls" type="caution">
+
+Don’t create separate projects for mobile and web. PostHog works best when you can see user behavior across all versions of your products in one set of data and views.
+
+Healthy integrations have a few things in common. It can help to review the [health check](/handbook/growth/sales/health-checks) documentation used by our sales team to tackle the most common ways to keep your bill manageable and predictable.
+
+If your historical data is above 100 GB or 200 million events, you should [reach out to our sales team](/talk-to-a-human) or [open a support ticket](/docs/support-options) so we can make sure everything imports smoothly.
+
+</CalloutBox>
path: contents/docs/new-to-posthog/switch-guide/migration-planning.mdx
user: login: daniloc
body: fair enough!
created_at: 2025-04-14T14:49:09Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,71 @@
+---
+title: Planning your pilot
+nextPage: ./migration-planning.mdx
+---
+
+import { CalloutBox } from 'components/Docs/CalloutBox'
+
+We want you to love using PostHog. We’ve worked hard to craft a tool that can make you much more effective at giving your customers what they want.
+
+Here's how to get the most out of a pilot test with your team.
+
+## Invite the people who care about user behavior, no matter their role
+
+PostHog charges by how successful your product is, not how many people have a login.
+
+That means anyone and everyone on your crew can explore at no extra cost. As your integration comes online, think about who else you’d like to invite. You'll have the option to invite them during setup, and any time after that.
+
+## Get help if you want it
+
+For companies sized 25 and up, [we’ve got a team](/talk-to-a-human) who can answer questions and help you make a plan.
+
+But only if you want the help! They’re not going to pressure you or do anything corny, but their integration experience can save time and trouble. They can also help you map PostHog features to your business goals, developing a useful mental model for using all our products.
+
+But we’re not going to get in your way, either, because…
+
+## We want you to play around
+
+The most important job is getting familiar with PostHog in whatever way makes you most comfortable. The most basic integration takes 5 minutes and we’ve got loads of documentation to support you exploring on your own.
+
+## First two weeks: get data in, then look at it
+
+Job one is making sure PostHog is reliably ingesting your data and reporting the basics in a dashboard. Once this is working, take a break, order a pizza[^1].
+
+From here, you can get more sophisticated:
+
+- **Decide**: Your [North Star metric](/docs/new-to-posthog/getting-hogpilled)  
+- **Decide**: Make an event tracking plan, or rely on autocapture?  
+- **Decide**: Use [identified or anonymous events](/docs/data/anonymous-vs-identified-events)?  
+- Configure a [reverse proxy](/docs/advanced/proxy) to improve reliability of event capture  
+- Experiment with measuring [activation](/docs/new-to-posthog/activation) and [retention](/docs/new-to-posthog/retention)  
+- [Watch some session replays](https://app.posthog.com/project/replay/home), see what you can learn  
+- Try out a [no-code survey](/docs/surveys/creating-surveys) to learn what customers are feeling about your product
+- Fire up [web analytics](/docs/web-analytics/getting-started), see if you like it better than your existing provider
+
+After two weeks to explore, check in with your teammates as well. See if there’s anything they want but aren't getting. If you can get them excited with you, you'll have a better chance of making this pilot turn into a full-on switch.
path: contents/docs/new-to-posthog/switch-guide/planning-your-pilot.mdx
user: login: daniloc
body: Yeah I think this is a great shout, will rework a bit to provide more structure
created_at: 2025-04-14T16:29:07Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,132 @@
+---
+title: "Switching to PostHog"
+nextPage: ./planning-your-pilot.mdx
+---
+
+For new projects and companies, PostHog is an easy sell: one login and simple integration gets you everything you need to build great products.
+
+But if you're already leaning on another tool, switching can require some planning and diplomacy. We made you a cheatsheet to help make the case.
+
+***
+
+## Advantages for everyone
+
+PostHog is one login and one bill.
+
+This means less headache for more power, with all your data available across a range of products that help you understand user behavior as it happens.
+
+You'll get a responsive team that cares about user needs, delivering on customer feedback constantly.
+
+PostHog is completely agnostic to the language, framework, and stack you build your product with. You can adopt it incrementally, adding new functionality as needed.
+
+Best of all, PostHog is built so that you’ll actually enjoy using it. We really want you to have a good time.
+
+***
+
+## Persuading product teams
+
+PostHog gives product teams the power to understand users, improve adoption, and test assumptions. Once PostHog is in place, your product teammates can dive in immediately, with loads of power that doesn't require further engineering intervention.
+
+- **[Visualize anything](/docs/product-analytics/insights)** with charts, trend reporting, and [dashboards](/docs/product-analytics/dashboards) that are easy to build, but also deeply customizable for SQL enthusiasts.
+
+- **Learn anything you want** about everything the user touches in the product without manual instrumentation with [autocapture](/docs/product-analytics/autocapture).
+
+- **Get clarity about navigation** and user priorities with [heatmaps](/docs/toolbar/heatmaps).
+
+- Use [session replay](/docs/session-replay/installation) to **reveal bugs, expose friction, and help instantly answer questions** like “is this new design working?”
+
+- **Integrate revenue data** from [Stripe](/docs/cdp/sources/stripe) and other sources using data warehouse, so you can get a clear picture of what changes really move the needle.
+
+- **Send events and other details to any other tool**, powering automations and keeping data in sync, with setup you can accomplish in seconds, fully customizable for any API or webhook. [Data pipelines](/docs/cdp) makes it easy.
+
+- **Gather feedback and book user interviews** from exactly the users you want to reach with no-code [surveys](/docs/surveys/creating-surveys) that deploy instantly.
+
+- **Get unblocked by PostHog’s helpful sales and support teams,** ensuring you get the insights and information you need quickly.
+
+***
+
+## Good news for engineering teams
+
+PostHog is designed for developers.
+
+The project is [developed in the open](https://github.com/PostHog/posthog), with a [public roadmap](/roadmap) and [dozens of pull requests landing](https://github.com/PostHog/posthog/pulls?q=is%3Apr+is%3Aclosed) each week. While other products are low-velocity black boxes, we’re constantly making PostHog better.
+
+ We’ve got a dedicated technical staff standing by to help keep you on track. If you ever do need support, you’ll be talking to someone who knows the technical details of the product really well.
+
+Giving other teams the data they want becomes much easier with PostHog in the mix, lowering the burden on engineering. Once a basic integration is in place, there are loads of features everyone can use without a developer's intervention.
+
+- **Consolidate the tools your company needs**, with one login, one integration, one bill.
+
+- **[Get comprehensive documentation](/docs)** developers love for every every stack, framework, and language. You can also view [our source code directly](http://github.com/postHog/) if you can't find what you need. 
+
+- **Get a data platform that encourages tinkering**: if something doesn’t fit quite right for your team, it’s easy to customize everything from visualizations to integrations with other services. We'll host all these customizations for you. You don't need to worry about infrastructure or uptime.
+
+- **Integrating PostHog with other tools or even your own services is easy**, thanks to [data pipelines](/docs/cdp).
+
+- **Roll features out gradually** using [feature flags](/docs/feature-flags/creating-feature-flags) that are easy to target with fine-grained queries across everything PostHog knows about your users.
+
+We also care about the technical details of switching over. No matter your stack or existing tools, **complete integration and [migration docs](/docs/migration)** mean a clear path instead of a puzzle to solve. Our experienced Sales and CS team can even provide backup for more complex cases.
+
+***
+
+## Make the case to executives
+
+We’re in this for a long-term relationship, so **PostHog wants you to spend as little money as possible**. Our sales team actually works with customers to reduce bills and optimize consumption. Instead of sneaky billing, we’d prefer to make more money as a result of you winning more business.
+
+There’s just no sneaky stuff going on here. You can get started immediately with no shenanigans, no calls with the sales team if you don't want them.
+
+- **Your team will like PostHog**. It’s fresh, always getting fixes, improvements, and additional power. An investment in PostHog today means even more capabilities by next year.
+
+- **There's no per-seat charge**, so PostHog makes it easy for everyone on your team to make data-driven decisions. No matter how quickly you scale your team, your costs remain fixed to the actual usage of your product. 
+
+- **PostHog’s sales process is transparent and so is the whole company**: the company [handbook is public](/handbook), *even documenting the ways we can offer [discounts](/handbook/growth/sales/billing#coupons-and-discounts)*. Everything you want to know about pricing, processes, and our product is publicly documented.
+
+- **You can have a free trial** to fully vet the costs and impact of your integration. Trying PostHog is low-risk, no cost, and fully reversible.
+
+- **PostHog doesn’t require a contract**. You can save money with one, but it’s not a blocker to trying things out.
+
+***
+
+## Sharing social proof
path: contents/docs/new-to-posthog/switch-guide/switching-to-posthog.mdx
user: login: daniloc
body: I'd like to keep it in the pitch guide to **hype the reader up** for the diplomacy they're about to do.

"No one ever got fired for picking Microsoft" kind of thing
created_at: 2025-04-14T16:37:09Z
author_association: CONTRIBUTOR

PR comments:
user: login: vercel[bot]
created_at: 2025-04-04T16:13:33Z
body: [vc]: #YZ4ZwTA3sSj/75Kk5Bz4ICJEBLkFZhpxAdW5DwMTWNI=:eyJpc01vbm9yZXBvIjp0cnVlLCJ0eXBlIjoiZ2l0aHViIiwicHJvamVjdHMiOlt7Im5hbWUiOiJwb3N0aG9nIiwiaW5zcGVjdG9yVXJsIjoiaHR0cHM6Ly92ZXJjZWwuY29tL3Bvc3QtaG9nL3Bvc3Rob2cvMzFoOHlVVHI4cnBQYm9TaVhiTW5SWFpHc01KNCIsInByZXZpZXdVcmwiOiJwb3N0aG9nLWdpdC1hZGQtc3dpdGNoaW5nLWd1aWRlLXBvc3QtaG9nLnZlcmNlbC5hcHAiLCJuZXh0Q29tbWl0U3RhdHVzIjoiREVQTE9ZRUQiLCJyb290RGlyZWN0b3J5IjpudWxsfV19
**The latest updates on your projects**. Learn more about [Vercel for Git ↗︎](https://vercel.link/github-learn-more)

| Name | Status | Preview | Updated (UTC) |
| :--- | :----- | :------ | :------ |
| **posthog** | ✅ Ready ([Inspect](https://vercel.com/post-hog/posthog/31h8yUTr8rpPboSiXbMnRXZGsMJ4)) | [Visit Preview](https://posthog-git-add-switching-guide-post-hog.vercel.app) | Apr 15, 2025 2:45pm |


author_association: NONE
user: login: daniloc
created_at: 2025-04-08T23:00:11Z
body: Spruced up the intro page with the pull quote elements, and added some more explicit sectioning. As a result I think it breathes a lot better now.

<img width="706" alt="Screenshot 2025-04-08 at 6 56 01 PM" src="https://github.com/user-attachments/assets/73ad9e4b-8914-40c5-8fcc-85e7564fe98a" />

The pilot planning page is lightweight enough.

The migration planning page is now three basic sections:

- what you should prepare for technically
- what you should demo to get people excited
- an appeal to reach out to onboarding/sales

I've also given it another line-level pass. @andyvan-ph @ivanagas, let me know what else you think this could use.
author_association: CONTRIBUTOR
user: login: daniloc
created_at: 2025-04-09T18:36:23Z
body: @ivanagas thanks for wading in! This was so helpful. Reworked and reflowed per your suggestions. The new ResearchGate quote really wraps it up nicely, glad to go to three.
author_association: CONTRIBUTOR
user: login: ivanagas
created_at: 2025-04-10T17:16:07Z
body: I do feel this is useful to have in docs and is in roughly the right place. 

- Realistically, convincing your teammates and building your PostHog mental models is a critical part of succeeding with PostHog. 
- Seeing as this comes from the sales and CS teams, I trust that it is what larger customers actually care about which matters a lot. 
- There is a lot of pages for "simple install" and individual usage before this that people can always swap to.

Maybe "Switching to PostHog" is the wrong frame and we are being clear enough who this guide is written for, but I do think it is pretty close.  
author_association: CONTRIBUTOR
user: login: daniloc
created_at: 2025-04-10T17:38:08Z
body: Let me start with this piece, because it's crucial:

> would a developer expect clicking 'Switching to PostHog' to take them to a page about convincing their teammates? 

And the answer is that regardless of the *expectation*, if we have a developer who *wants their company to switch*, job one is convincing the rest of the team that this is a good idea.

Now, I have been in the position in my career as a developer where I KNEW a tool was way better than what we were using, but it lived across too many functional boundaries for me to translate the benefits.

And so: I gave up.

So we start from the position that the problem of convincing your team is solvable, and here are the details.

> I worry this guide makes switching to PostHog sound hard

Here's the thing: switching to PostHog, **if you are already wedded to a different tool**, is hard. I mean, it's a whole engineering project to do it, by definition.

Right now our docs story on that is: here's a migration tool, good luck.

Which burns because there's a bunch of new stuff to learn, but more than that, your biggest problems are actually operational, not technical. You've got so much org-level work to do to make it happen.

The way I see it, we can document that fact and arm our champion with as much detail and planning fundamentals as possible, or they can discover it by accident and then churn.

If we're building the best **new approach**, I think we have to think hard about how we build scaffolds for the many people who are marooned in the old one. Right now, their path into the light has to be either discovered entirely by them or painstakingly constructed, manually, over and over by sales.

# Docscollateral 

Now this brings me to my central insight from a quarter of working with the sales crew:

The docs *are* sales collateral. Our *whole deal* is that you don't have to get on a call with sales to get started. And people love this. It wins us credibility. But we also know that people who work with sales are going to benefit from:

- structure and planning
- insight into the product
- experience across many customers

So we want artifacts in the docs that not only scale that wisdom, but get people into the sales conversation when necessary.

We're still figuring it out and it'll be awkward. Let's ship the awkward baby anyway. That's my argument. If I'm wrong, no one reads it and it's fine. I'm also very into a more fleshed out switching resource in the future.

But if we ship this now, I'll get bandwidth back to continue adding to it – next week is migrating your team's mental model from Amplitood – and the more of it that's complete, the clearer our decisions for making the next iteration.
author_association: CONTRIBUTOR