A small community and a large archive need different amounts of work. We look at your data before agreeing the scope, cost and timing.
Read our migration guideJatra / Community migration
Your community deserves a better home. Moving it needs a plan.
Years of conversations, member relationships and useful answers are worth taking care of. Work directly with us to plan your move to Jatra and check the details before your members arrive.
Work with the person doing the move
You do not have to figure out the import yourself.
Jatra founder Kaustubh Katdare handles migrations directly, with experience moving communities from vBulletin, XenForo and Discourse. We review your current setup with you, scope the work and handle the agreed import and redirect mapping.
Start with what you already have
Agree what comes across before making the move.
The source platform and its export determine what is available. Together, we review the parts your community depends on.
- Members and access
- Review member records, roles and private spaces. Plan how people will sign in to their new community.
- Conversations and files
- Check posts, replies, authorship, dates and attachments. Agree how the available content maps to Jatra.
- Links people already use
- Review existing URLs and important search landing pages. Build the redirect mapping included in your migration scope.
A move you can review
Check the work before changing the address.
We agree the sequence around your source platform, data and launch needs.
- Review the source
- Look at your community, export options, content volume and anything that needs special handling.
- Map the move
- Agree the content mapping, access rules, redirects, responsibilities and cutover plan.
- Import and check
- Review imported content, attachments, permissions and links together before opening the new community.
- Prepare the switch
- Plan the final transfer, domain change and member communication around the agreed launch date.
The people behind the records
Help members feel at home after the switch.
A successful import is only part of the move. Members need to know what is changing, how to sign in and where to find familiar conversations.
- Explain the change early
- Give members time to prepare, especially if they will need to reset their password.
- Let regulars try it first
- A preview with your core members can reveal confusing navigation or access issues before the wider launch.
- Plan the first few weeks
- Decide who will answer questions, check links and help returning members find their way.
Before we scope the work
A few questions about moving.
Can you move a community from my platform?
Share the platform name, community URL and any available export details. We will review what can be moved and identify anything that needs a different approach before agreeing the work.
How much does migration cost, and how long does it take?
Every migration is scoped individually. Content volume, export quality, attachments, redirects and custom requirements affect the work. We agree the cost and timing after reviewing your setup.
Will members keep their passwords?
Password portability depends on the source platform and how its authentication works. If passwords cannot transfer, we plan the sign-in and reset steps so members know what to expect.
What happens to our existing links and search traffic?
We review your URLs and agree a redirect plan for the move. Redirects help readers and search engines reach the corresponding pages, but a platform change can still affect search traffic. Checking links and monitoring the transition belong in the plan.
What should I bring to the first conversation?
Your community URL, current platform, approximate member and post counts, desired timing and any integrations or private areas we should know about. You do not need a completed export to start the conversation.
Start with your current community
Let’s work out what your move needs.
Show us where your community lives today and what you want to improve. We will review the migration with you.