Create project-migration.md #1489
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
link out project migration playbook
|
The Migration section is under "Data In" which is focused on migrating from other third-party tools into Mixpanel. This article is about migrating data from one project to another project within Mixpanel which makes more sense under Orgs & Projects in the Admin section. What do you think? |
|
I agree that it makes more sense under the admin section. I can move it! |
|
please add the image into this pull request |
kurbycchua
left a comment
kurbycchua
left a comment
There was a problem hiding this comment.
Also generally thinking maybe this page should just be under Guides instead of Docs since this is like best practice and playbooks. Overtime as we build more playbooks they should not be mixed with Docs
|
Hi @carolinephilbin , did you get a chance to review the feedback from Kurby? |
updated with kurby's feedback
|
Yes, the most recent commit has updates with Kurby's feedback.
…On Tue, Oct 22, 2024 at 4:57 PM myronkaifung ***@***.***> wrote:
Hi @carolinephilbin <https://github.com/carolinephilbin> , did you get a
chance to review the feedback from Kurby?
—
Reply to this email directly, view it on GitHub
<#1489 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AINXAHIYGSFDPGZB6GZVGQTZ43Q5JAVCNFSM6AAAAABPMF7LE6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZQGUZDMNRXGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
*Caroline Philbin*
Strategic Customer Success Architect | LinkedIn
<https://www.linkedin.com/in/caroline-philbin-3ba20552/>
unsubscribe <https://discover.mixpanel.com/UnsubscribePage.html> | privacy
statement <https://mixpanel.com/legal/privacy-policy/>
* <https://docs.mixpanel.com/changelogs>*
|
|
hey @carolinephilbin @myronkaifung I was added as a reviewer automatically, but saw you were collaborating and then that @kurbycchua was added as a reviewer (I was also out for most of the initial time). Are you looking to also have another pair of eyes review it? or with the checks that Kurby did, you want to have it out? |
|
hey @argenisf i think we should be all set with @kurbycchua's review, thank you! |
argenisf
left a comment
argenisf
left a comment
There was a problem hiding this comment.
Chatted with Caroline and giving my OK after Kurby's review
Consolidating the two Analytics Strategy pages
Reverting back consolidation of Analytics Strategy pages
updated jsx to py
adding playbooks
analytics strategy redirect
retaining event depth section from analytics strategy section that was removed
kurbycchua
left a comment
kurbycchua
left a comment
There was a problem hiding this comment.
just one small link that needs update and I'm good with the rest!
pages/docs/migration.md
Outdated
| - Load a limited subset of the data into a test project (for example, a single day or data or a sample of the entire dataset) to get started. This will help you identify any errors in the end to end process before you do a full historical data load. | ||
| - Load a year’s worth (or less) of historical data during your migration. This will allow your team to review year-over-year trends easily and do historical analysis as needed, without sending a bunch of data which is stale and unlikely to be used. | ||
|
|
||
| For a more in-depth look into the steps required for a successful project migration, check out our [project migration playbook](/docs/pages/guides/plan/project-migration). |
There was a problem hiding this comment.
this should now be /docs/pages/guides/playbooks/project-migration
update URL
No description provided.