Why Migrate to TravelFeed?
Considering a switch? Here’s why migrating to TravelFeed from WordPress is a smart choice:
- Affordable Pricing: Get a TravelFeed account with monetization or managed hosting from $15/month, whereas WordPress managed hosting starts from $35/month with added costs for plugins and themes.
- Built-in SEO: TravelFeed is SEO-ready out of the box. With WordPress, you need extra plugins.
- Social Integration: TravelFeed is not only a blogging software, but also a social network that gets your content seen by many travel blog readers, a feature missing in WordPress.
- Speedy Performance: Experience faster load times with TravelFeed, while WordPress can lag behind.
- Your destinations organize themselves: pin a post to a place and TravelFeed generates the country, region and city pages for it, linked to each other and ready for search. On WordPress that structure is categories and menus you groom by hand, one post at a time.
- Superior Security: TravelFeed offers a secure, maintenance-free experience, in contrast to the regular vulnerabilities in WordPress.
- Travel blocks, not plugins: interactive maps, photo galleries and day-by-day itineraries are built into the editor, and every post gets share cards made for it, including the vertical pin Pinterest wants. On WordPress each of those is a plugin to research, buy and keep compatible.
- AI Blogger: Drafts from your own photos and an interview about the trip, never from thin air. Included, where other tools require costly subscriptions.
- Built in Monetization: TravelFeed is fully integrated with Hive for easy monetization and a great community
Migrating to TravelFeed gives you specialized tools and a smoother experience tailored for travel bloggers. For an in-depth comparison, see our detailed post.
Step 1: Prepare the WordPress Export File
To move your content from WordPress, an Export File (.xml) is needed.
- Go to your WordPress Dashboard.
- Select: Tools > Export.
- Choose 'All content' and click ‘Download Export File’.
Ensure the file is in .xml format. If it’s a zip file, extract the .xml file before proceeding.
Step 2: Importing to TravelFeed
Navigate and manage your import with these steps:
- Access the TravelFeed Dashboard.
- Click on 'Drafts' (in the sidebar).
- Click 'Import' (in the tabs right beside 'Published'). On mobile, it's a green import icon.
- Select 'WordPress'.
- Upload your .xml Export File.
Import Details
- What’s Imported: Posts, drafts, and pages from WordPress, with their formatting.
- What’s Not Imported: Comments.
Your images need one sentence of explanation. Imported posts arrive still pointing at the images where they live today, on your old WordPress host. Once you publish a post on TravelFeed, we keep a permanent copy of every image in it and serve that copy from then on.
What that means in practice: publish your imported posts before you cancel your old hosting, and your archive keeps working after that server goes away. It also covers the slower version of the same problem, where an old host quietly loses files years later. If your archive is large, contact us before you switch and we will keep an eye on it; help with the move is included with every plan.
Post-Import Actions
All selected posts/pages/drafts are imported as unpublished HTML drafts.
To publish a post, just open the draft and review it ("preview" button on the top right) to check that the formatting is correct. Generally, the formatting should look good as long as it follows standard HTML, but if you are using some plugins in WordPress within posts that use their own short codes, these need to be edited manually. Add locations to your posts and ensure that all data is imported correctly and finalize your post settings according to your preferences.
If you are posting to Hive, be aware that Hive has a limit of one new post every 5 minutes - if you post more often than that, the post will still be published on TravelFeed and your own domain (if you use TravelFeed Hosting), but for Hive, if posting fails due to the 5 minute limit, our system will retry posting an hour later - if you publish too many posts at once, some might not go out to Hive.