How to Switch Your Blog from WordPress, Ghost, or Medium to inblog
Choose the Right Migration Path
inblog supports two migration paths. The right one depends on your current platform and whether its export format is available in the dashboard.
Import directly from the dashboard: CSV, Ghost, Naver Blog, and Tistory are available under Settings → Advanced → Import Content.
Team-supported migration: WordPress, Medium, Markdown, and other formats that are not available in the dashboard can be migrated with help from the inblog team.
Direct import is available to Team or Enterprise plan blogs and blogs in an active Team trial at no additional cost. Team-supported migration is available to paying customers.
Naver Blog and Tistory import options appear for Korean-language blogs or when the dashboard language is Korean.
Before You Start
Make an export or backup of your current blog before changing domains, URL paths, or publishing status. Build a URL inventory that includes each post's current URL, intended inblog slug, title, publish date, meta title, meta description, and canonical URL.
If you need team-supported migration, complete the migration template linked in the official documentation and send it to contact@email.inblog.ai. Team-supported migrations typically take 1–2 business days and may take up to five days depending on complexity.
Platform-by-Platform Instructions
Ghost
In Ghost Admin, go to Settings → Advanced → Import/Export.
Export your content as a JSON file.
In inblog, go to Settings → Advanced → Import Content → Ghost Import.
Enter the existing Ghost blog URL and upload the JSON file.
Review titles, slugs, publish dates, tags, images, and formatting before launch.
CSV
Use Settings → Advanced → Import Content and choose CSV Import. Match the required columns to the template shown in the dashboard, then review a small sample before importing the full file.
Naver Blog and Tistory
Open Settings → Advanced → Import Content and choose the relevant importer. For Naver Blog, enter the blog ID from the public blog URL, such as https://blog.naver.com/your-blog-id. The public blog ID can differ from the Naver login ID.
WordPress
WordPress migration is handled through team support rather than the dashboard importer. Prepare a static export or the files requested in the official migration guide, preserve your existing URL list, and send the completed migration template to the inblog team.
Medium
Request your Medium data export from account settings, unzip the downloaded file, and keep the HTML files in the posts folder. Provide the files and URL mapping through the team-supported migration process.
Other Platforms
For Webflow, Imweb, Markdown, or another CMS, use the migration template format and include each post's title, body, publish date, slug, and metadata. The team will confirm whether the source format can be migrated and whether additional preparation is needed.
Images Are Copied During Migration
When supported content is migrated, images inside the posts are copied to inblog's servers and their URLs are rewritten to inblog addresses. This prevents migrated posts from depending on the old blog for image delivery.
Keep your original export until you have verified the migrated posts. Do not delete the old site before checking image loading, captions, alt text, and formatting on representative desktop and mobile pages.
Redirects Are Your Team's Responsibility
If the domain or URL structure changes, configure permanent redirects from every old URL to its new inblog URL. These redirects must be configured on the server, website platform, reverse proxy, or domain infrastructure that controls the old URLs.
inblog cannot configure redirects on your old domain on your behalf. The redirect manager inside inblog can manage routes served by an inblog-connected blog, but it cannot take control of URLs still served by WordPress, Ghost, Medium, Naver, or another provider.
Keep the same slugs where practical. If you are moving from blog.example.com/post to example.com/blog/post, map every old URL explicitly and test the redirect response before decommissioning the old site.
Post-Migration SEO Checklist
Compare URL inventories: every old indexable URL should have a matching destination or an intentional removal decision.
Check permanent redirects: verify that old URLs resolve directly to the correct new URL without redirect chains.
Review metadata: confirm titles, descriptions, canonical URLs, publish dates, headings, and image alt text.
Check internal links: update links that still point to old hosts or obsolete URL structures.
Submit the sitemap: connect Google Search Console and submit the sitemap for the final blog domain.
Monitor indexing: review coverage, crawl errors, impressions, and traffic after launch.
A platform migration does not guarantee unchanged rankings. Correct URL mapping, redirects, metadata, content quality, and ongoing monitoring reduce avoidable risk while search engines recrawl the new setup.
Ready to Migrate?
Start by confirming whether your source is available in Settings → Advanced → Import Content. If it is not, review the official migration documentation and contact the inblog team with your export format and URL inventory.