Migrating Your Blog to inblog

Import CSV, Ghost, Naver Blog, and Tistory directly from the dashboard, or migrate WordPress, Medium, and other platforms with team support.

inblog supports two migration paths:

  • Import directly from the dashboard: CSV, Ghost, Naver Blog, and Tistory are available under Settings → Advanced → Import Content. Direct import is available to Team or Enterprise plan blogs and active trials at no additional cost. Naver Blog and Tistory appear for Korean-language blogs or when the dashboard language is Korean.
  • 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.

Team-supported migration is available to paying customers only.

Turnaround for team-supported migration: Typically within 1–2 business days

Migration Template

Download and complete the migration template, then email it to contact@email.inblog.ai.

If your posts are already in CSV format, you can instead download the sample CSV from Settings → Advanced → Import Content → CSV Import and upload the completed file directly.

WordPress to inblog

Export posts using the Simply Static plugin:

  1. Go to WordPress Admin → Plugins → Install Simply Static
  2. Navigate to Simply Static → Settings and configure:
    • Delivery Method: "Download ZIP" or "Save to local directory"
    • URL Type: Choose Relative URLs (e.g. ./about.html)
  3. Go to Simply Static → Generate, click Generate Static Files
  4. Download the ZIP file and send it to inblog

Ghost to inblog

  1. Go to Ghost Admin → Settings → Advanced → Import/Export
  2. Click Export to download a .json file
  3. In the inblog dashboard, go to Settings → Advanced → Import Content → Ghost Import
  4. Enter your existing Ghost blog URL and upload the exported JSON file

Medium to inblog

  1. Go to Medium account settings
  2. Select Download your information
  3. Receive a ZIP file via email
  4. Extract and locate .html files in the posts/ folder
  5. Provide URLs and HTML files for migration

You can migrate your Naver Blog directly from Settings → Advanced → Import Content in the inblog dashboard. Enter your Naver Blog ID to start importing your posts. If you run into problems or need additional support, contact us via chat.

Note: Your Naver Blog URL is in the format https://blog.naver.com/your-blog-id. This blog ID may differ from your Naver login ID. For example, your login may be kim1234 while your blog URL is https://blog.naver.com/mycompanyblog. Check the address bar in your browser to confirm the correct blog ID before entering it in the dashboard.

Tistory to inblog

You can migrate Tistory directly from Settings → Advanced → Import Content → Tistory Blog Import. Enter your own Tistory URL in the format https://your-blog-id.tistory.com to start importing posts.

Note: The importer currently accepts the standard *.tistory.com URL format. If you use a custom domain or run into a problem, contact us via chat.

Other Platforms (Wix, Webflow, custom CMS, Imweb)

Use the migration template format for unsupported platforms.

Imweb to inblog

Imweb has limited built-in content export options. To prepare your content for migration:

  1. In the Imweb admin panel, open your board (content list).
  2. Copy the title, body, and publish date for each post into the migration template.
  3. Email the completed template to contact@email.inblog.ai and the team will handle the migration.

Post-Migration Checklist

1. Check Content Display

Verify that buttons, tables, and images display correctly within inblog's format.

2. Redirect Old URLs (301 Redirects)

Set up 301 redirects if your domain or URL structure changed (e.g., blog.example.com to example.com/blog) to preserve SEO.

Redirects must be configured on your own domain server.

inblog cannot manage redirects on your behalf.

Example: From /category/post-name → /post-name.

3. Backup Your Old Blog

During migration, images in your content are copied to inblog's own servers, and their URLs are automatically updated to inblog addresses. As a result, closing or unpublishing your old blog (WordPress, etc.) will not break the images in your migrated posts.

Even so, we recommend backing up your original content—especially the original image files—locally before deleting the old blog, just in case.

Frequently Asked Questions (FAQ)

Will my blog formatting be preserved?

Content will be styled according to inblog's design system and templates. Tables, buttons, and elements will be adapted for consistency.

How long does team-supported migration take?

Team-supported migration usually takes 1–2 business days, or up to 5 days depending on complexity.

Do you configure redirects for me?

No, 301 redirects must be set up by your team on your server or domain provider.

Will changing blog URLs affect SEO?

Temporarily, yes. Rankings and traffic may drop briefly as search engines re-index pages. "301 redirects help preserve SEO value and minimize losses."

Do you offer post-migration QA or reviews?

No. Clients are responsible for reviewing and confirming migrated content.

What is inblog's default URL slug structure?

Posts are published under: /[post-slug]

If your old structure used /[category]/[post-slug], set up redirects from the old format.

If your old blog used internal links, either:

  • Set up domain-level redirects from old to new blog URLs
  • Or provide updated internal URLs in migration files

Where are migrated images stored? Can I close my old blog?

During migration, images in your posts are copied to inblog's servers and their URLs are automatically rewritten to inblog addresses. Once migration is complete, you can unpublish or shut down your old blog (WordPress, Naver, etc.) without breaking the images in your migrated posts. We still recommend backing up your original data once before deleting the old blog, just to be safe.

Last updated 2026-07-23