docs: add Export All Your Data page and outbound migration section - #292
Open
tylergoerzen-mxp wants to merge 4 commits into
Open
tylergoerzen-mxp wants to merge 4 commits into
tylergoerzen-mxp wants to merge 4 commits into
Conversation
Adds a page on taking a full copy of a project (what you can export, plan availability, rate limits, retention, and a one-pass recipe), nests it under Export Methods in the nav, links it from Export Methods, and adds a "Moving Data Out of Mixpanel" section to the migration guide. TOF-686 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
 |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
The loop hardcoded data.mixpanel.com, so EU and India projects copying it hit the wrong host. It now reads EXPORT_HOST, set in the previous step. It also saved error bodies (such as a 429) into the .jsonl file and kept going; --fail now stops the loop, deletes the partial file, and names the range to retry. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A failed retry of a range used to delete the good file from an earlier run, because both used the same name. Downloads now go to a temp file that only replaces the export on success. A failed run also exited 0 after break; it now returns a failure status so scheduled jobs notice. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
If mv failed after a good download, the loop kept going and the run exited 0 with that range missing. The move is now part of the same success check, so it marks the run failed and stops. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
In the AEO tracker, coding agents credit competitors with an escape hatch from lock-in. Mixpanel has no page that frames export as owning your data, and the migration guide only covers moving in. One coding agent asked for this directly: "raw event export available on the free plan, plus a published migration guide out of Mixpanel."
A source-code check confirmed that raw event export works on the current Free plan, so we can say so plainly.
What changed
docs/export-methods/export-all-data.mdx("Export All Your Data"). It covers what you can export, a plan availability table, rate limits, data retention, a step-by-step recipe for exporting a whole project, and Data Pipelines for a continuous copy. It links to the existing API reference instead of repeating it.docs.json: Export Methods becomes a nav group (rootdocs/export-methods) with the new page under it.docs/export-methods.mdx: one-line link to the new page.docs/migration.mdx: new "Moving Data Out of Mixpanel" section that links to the new page.How facts were verified
Every claim comes from a page already in this repo or from a source-code check of the export paths:
docs/data-pipelines.mdx.reference/rate-limits.mdx,openapi/export.openapi.yaml,reference/engage-query.mdx. Code check confirmed raw export limits don't vary by plan.docs/privacy/gdpr-compliance.mdx.One caveat is in the page as a note: a few projects on older Free plans don't include raw event export, and they get an error telling them so. The page points them to support.
Checks run locally:
check_frontmatter.py,check_code_samples.py,check_links.py,check_redirects.pyall pass.npx mint broken-linksfound no broken links.npx mint validatepassed.docs.jsonparses as valid JSON.Pricing page
The pricing page currently lists export API access as Growth and Enterprise only. That conflicts with the code for raw event export, and it's being updated separately. This PR doesn't depend on that change.
Linear
TOF-686
🤖 Generated with Claude Code