How to Move Content Between Blogger Blogs Safely

If you need to transfer Blogger content to another blog, do not start by importing it directly into a blog that is already public. The safe process is to identify the correct source and destination blogs, back up the content and theme separately, import the file into the destination blog in draft mode when review is needed, and then check each data group before allowing readers to access it.

By the end of this article, you will have a checklist you can apply to data under your control. The example SaibABC Blog is only a planned illustrative project on Blogger; the article does not claim that this blog has been created, has a real address, or contains actual content.

Before transferring, identify the correct source, destination, and usage rights

Transfer data only when you own the content or have the right to manage it—for example, your own posts, a backup of a blog you administer, or data that the owner has authorized you to transfer. Content that is publicly available on another Blogspot site does not automatically become content you are permitted to import and republish.

Write down the following four details before you begin:

Source blog: the blog containing the posts, pages, and comments to be transferred.
Destination blog: the blog that will receive the data.
Administrator account: the Google Account with permission to manage both blogs, or the appropriate permission on each blog.
Transfer objective: whether you are archiving, reviewing, moving content to a new blog, or republishing it.

Do not use SaibABC.Com as the practice source or destination. It is a WordPress website used to publish the series, whereas SaibABC Blog is an illustrative Blogger project. A WordPress export should not be treated as a file that can be imported directly into Blogger: Blogger’s documentation instructs users to import a file feed.atom from Google Takeout or a file .xml from a Blogger backup. This is a format distinction, not a claim that all XML files are compatible with one another (according to support.google.com).

Back up the content and theme as two separate files

Blogger separates content backups from theme backups. Therefore, a theme file is not a copy of the blog’s posts, pages, or comments; conversely, a content backup does not restore the blog’s layout and theme code.

Back up the source blog’s content

Sign in to Blogger and select the correct source blog in the upper-left corner.
Open Settings and find the Manage blogsection.
Select Back up content and download the backup file to your computer.
Rename the file using a recognizable naming scheme, such as blog-nguon-noi-dung-2026-09-22. Change only the part before the period; do not modify the file extension.
Store the file in at least two locations under your control, such as your computer and a separate storage drive.

For a copy obtained through Google Takeout, find the file feed.atom in the Blogger folder for the corresponding blog. An older Blogger backup file .xml can also be imported through the same workflow. If you use Google Takeout, verify the correct blog before selecting the file; the folder or file name does not replace cross-checking the source blog.

Back up the source blog’s theme

In Blogger, select the correct source blog.
Open Theme.
Next to the Customize, then open the options menu.
Select Backup and download the theme file.
Clearly label this as a theme backup, not a content backup.

You need a theme backup if your goal is to recreate the blog’s appearance or keep a restore point before making changes. However, do not apply the source theme to the destination blog immediately; first check its compatibility with the new layout, gadgets, and content (according to support.google.com).

Prepare the destination blog for a safe import

Confirm the destination blog before selecting the file. Choosing the wrong blog is a serious error because the import may send data to an address other than the one you intended.

Select the destination blog from the Blogger list.
Check the blog name, address, and account profile picture.
Record the destination blog’s current state: number of posts, number of pages, main labels, and active theme.
If possible, use a test blog or a destination blog that is not yet public for the initial check.
Do not delete existing posts from the destination blog until you know that the import file works correctly.

If the destination blog is public, consider temporarily restricting reader access while you perform the checks. Blogger provides a Reader access setting that lets you make the blog public or limit access to authors; being able to see the blog while signed in does not prove that signed-out visitors can also view it (according to support.google.com).

Grant administrator access only to people who genuinely need it. Administrators can change settings, themes, and posts; authors have more limited permissions. If you are transferring content within a collaborative team, you can also review the Blogger permissions guide for collaborative teams to verify access rights before proceeding.

Import posts, pages, and comments using the correct file format

On the destination blog, prepare a file feed.atom from Google Takeout or a .xml Blogger backup file. Do not change a file extension just to make a different format look like XML.

Sign in to Blogger and select the destination blog.
Open Settings.
Under Manage blog, select Import content and then select Import.
Review the Automatically publish all imported posts and pagesoption.
If you need to review the content first, turn off automatic publishing.
Select the file feed.atom or .xml from your computer, then open the file.
Wait for the import to finish, and do not publish the content immediately afterward.

Blogger’s official documentation confirms that this workflow imports posts, pages, and comments. The documentation also states that there is a daily limit on the number of files that can be imported, but does not specify a file-size limit in the referenced guidance. Therefore, if you need to perform multiple imports, divide the plan into clearly documented batches instead of repeatedly clicking Import without control.

Check six data groups before publishing

A successful import only confirms that Blogger accepted the file. It does not prove that all content is displayed correctly or that every link is still appropriate for the destination blog. Check the results using the table below.

Data group to check	How to check it	Signs that require attention
Posts	Open the Posts list and check the titles, content, dates, status, and URLs of several posts.	Duplicate posts, an incorrect status, missing sections, or unusual displayed dates.
Pages	Open Pages and check the About, Contact, or overview pages, if present.	A page was imported as a post, links within the page still point to the source blog, or placeholders remain.
Comments	Open several posts with comments and compare the number of comments, display names, and moderation status.	Comments are missing, unexpectedly awaiting moderation, or the destination blog’s comment settings are inappropriate.
Images	Open the post in preview mode and at a test public URL; check the featured image, images within the content, and thumbnails.	Images do not load, have incorrect dimensions, point to an inaccessible source, or lack alternative text.
Labels	Open the label list and posts with labels; check capitalization, Vietnamese diacritics, and content grouping.	Labels have been split into multiple variants, such as “Blogger” and “blogger,” or assigned to the wrong posts.
Links	Click internal links, menu links, and links within posts in a private window.	Links still lead to the source blog, placeholder URLs, 404 pages, or unwanted redirects.

For the SaibABC Blog example, you can use the sample post “5 Things to Prepare Before Creating a Personal Blog” as test data if you have the right to manage that post. Check its five main content areas: defining the objective, choosing the audience, selecting a topic, preparing the blog name, and planning a publishing schedule. This is project example data, not evidence that the post has been imported into SaibABC Blog.

Publish in stages instead of publishing the entire batch at once

If you disabled automatic publishing, keep the data in draft status during the review phase. Review one or several representative posts first, including posts with images, labels, links, and comments.

Publish only after confirming that:

You are working in the correct destination blog.
The required posts are present and no unexpected duplicates have been created.
Images display correctly, links open the right destinations, and labels are assigned appropriately.
Static pages no longer point to the wrong source blog.
The blog’s reader-access settings and each post’s status match your objective.

After publishing a test post, open its URL in a private window or a browser where you are not signed in. If the blog or post still requires sign-in, check Reader access and the post status instead of concluding that the import file is faulty. Checking outside the administration panel is important because the dashboard may show you content that ordinary readers are not permitted to view.

Handle errors and undo changes without losing the original

The file is not recognized or the import fails

Check that you selected the correct destination blog and the correct file.
Open the backup to confirm that it contains feed.atom or a .xml suitable file.
Do not change the file extension or edit the file with a text editor.
Record the error message and the time of the attempt.
If you have imported the file multiple times, stop to avoid creating additional duplicates.

Posts were published unexpectedly

Immediately open the Posts list in the destination blog, filter for the recently imported posts, and change them to drafts or unpublish them individually. Then check the blog’s reader-access settings again. Do not delete the backup file or the posts on the source blog until you have confirmed that the destination blog contains the correct copy.

Images or links are broken

Do not make bulk edits before identifying the cause. For images, record the affected post and the image’s location, then replace it with a file you are authorized to use when you have the original. For links, classify them as internal links that still point to the source blog, dead external links, or placeholder URLs. Fix each group, then reopen the public URL to verify the result.

You want to return to the state before the import

The safest rollback point is the content backup together with notes recording the destination blog’s state before the import. If the destination blog is used only for testing, you can delete the imported posts by the recorded batch; do not delete the entire blog just because one group of posts is faulty. Blogger states that permanently deleting a blog makes its information, posts, and pages unrecoverable, so this is not the default rollback step (according to support.google.com).

Blogger content transfer completion checklist

I identified the correct source blog, destination blog, and account with management permissions.
The transferred content is under my control or I have clear permission to use it.
I saved separate backups of the content and the theme.
I used feed.atom or .xml as appropriate, and did not use a WordPress file as though it were a Blogger file.
I disabled automatic publishing when a preliminary review was needed.
I reviewed posts, pages, comments, images, labels, and links.
I opened at least one URL in a private window or a browser where I was not signed in.
I recorded the transfer date, file name, destination blog, and any remaining errors.

Practice exercise and next steps

Use a test blog or a small amount of data under your control. Record the destination blog’s state, import the file with automatic publishing disabled, select three representative posts to review, and then complete the table below:

Item	Expected result	Actual result	Action required
Post with images	Images open correctly without breaking the layout	[điền kết quả]	[giữ nguyên/thay ảnh/sửa kích thước]
Post with labels	Labels have the correct names, and their post lists open correctly	[điền kết quả]	[điền việc cần làm]
Post with links	Links lead to the correct destinations	[điền kết quả]	[điền việc cần làm]

Once the checklist is complete, publish in batches and retain the backup file and migration log. If your goal is to obtain content from another Blogspot site rather than move a backup under your management, the next step is to distinguish among RSS, quotations, links, permitted republication, and importing a backup file in Using Content from Another Blogspot: RSS, Quotes, or Republishing?. These are not the same thing: being able to import a backup does not mean that you have permission to republish someone else’s content.

Reference source

Back up or import your blog — Blogger Help.
Use themes to change how your blog looks — Blogger Help.
Manage your blog’s settings — Blogger Help.
Control access to your blog — Blogger Help.
Delete or restore your blog — Blogger Help.

Move Content Between Blogger Blogs: Back Up, Import, and Verify