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:

Go to WordPress Admin → Plugins → Install Simply Static
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)
Go to Simply Static → Generate, click Generate Static Files
Download the ZIP file and send it to inblog

Ghost to inblog

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

Medium to inblog

Go to Medium account settings
Select Download your information
Receive a ZIP file via email
Extract and locate .html files in the posts/ folder
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.

When the Naver Import Won't Start

The input field already shows a blog.naver.com/ prefix, so enter only the blog ID — not the full URL. Pasting https://blog.naver.com/mycompanyblog in full leaves the start button disabled.

If the start button is greyed out and won't click

The button only becomes clickable when both conditions are met. If you get no error message and the button simply won't respond, check these two:

ID format — only letters, digits, _, and - are accepted. Pasting a full URL, or including spaces, /, ., or non-Latin characters, leaves the button disabled.
Ownership checkbox — you must tick I confirm that this is my own blog.

If you see Naver blog not found. Please check the blog ID.

The format is valid, but https://blog.naver.com/<your-id> doesn't load. Re-check the actual blog ID in your browser's address bar. A private or closed blog — or a temporary failure on Naver's side — produces the same message, so if you're sure the ID is right, try again shortly.

If neither applies but the import still doesn't run, send us the blog ID you entered and the time it failed over chat.

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:

In the Imweb admin panel, open your board (content list).
Copy the title, body, and publish date for each post into the migration template.
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 (308 recommended)

If your domain or URL structure changes (for example, blog.example.com → example.com/blog), set up a permanent redirect from each old URL to its matching new page. We recommend 308 for new permanent redirects. See 308 vs 301 for the difference and when to keep 301.

Your team must configure redirects from the old domain on the server, CDN, or reverse proxy that receives requests for that address, with DNS and HTTPS configured there. Changing the domain connected to inblog does not automatically redirect the old custom domain. inblog’s redirect rules apply to paths on the connected blog; they cannot handle requests that do not reach inblog.

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?

Will changing blog URLs affect SEO?

Rankings and traffic may fluctuate while search engines process the move. Permanent redirects help them discover the new URLs, but do not guarantee rankings or traffic.

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.

What about internal links within posts?

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.

308 vs 301

For new permanent moves, inblog recommends 308. Both codes indicate a permanent move; the difference is how the redirected request is sent.

Code	Request behavior
301	The client may change POST to GET, dropping the request body.
308	Preserves the request method and body: POST remains POST.

For normal GET requests to blog posts, both serve the same permanent-move purpose. Google treats both as permanent redirects, so 308 is not inherently better for SEO. Keep an existing 301 that works correctly; 301 is also suitable for blog page moves if your hosting only supports it. For forms or APIs, check that the destination accepts the preserved method and body before using 308.

The request behavior is defined in RFC 9110: 301 and 308.

Last updated 2026-09-08

PreviousGetting Started with inblog NextBlog Settings Overview