Moving a Document Archive into WordPress Safely: Back Up, Import, Check Storage
Importing hundreds of Word documents changes a WordPress site more than any single post. How to back up first, import in batches, and check what the import did to your disk space.
By the BackupScope team4 min read
Somebody has decided that the shared drive full of Word documents (course notes, procedures, case studies, nine years of client reports) belongs on the website.
The import itself is the easy part. The parts that go wrong are around it: no backup when a batch goes badly, and a hosting plan that is suddenly 80% full a week later because every document brought its images with it.
This guide covers those parts. For the import itself, see the step-by-step guides linked at the end.
Why an archive import is different
Publishing one post a week changes a site slowly. Importing an archive changes it all at once:
- Hundreds of new posts in the database, with their categories, tags and authors.
- Thousands of new files in
wp-content/uploads, because every image in every document is uploaded, and WordPress makes several resized copies of each. - Settings you might change on the way, such as a new category structure, a new post type or a new permalink pattern.
If any of that turns out wrong, you want to be able to go back to exactly where you started. That means a backup, taken before the first document goes in.
Step 1: Back up the whole site first
Take a full backup: files and database. Not just the database: the import writes to both.
With BackupScope (free), that is one Full Backup. It scans the site first, so you see what will be included and how big it is, and it verifies the archive before it counts it as done. Large sites are backed up step by step, so a server time limit does not stop it.
Then:
- Download the backup and keep it off the server. A backup that only exists on the same server does not help if the server is the problem.
- Keep it until the archive is checked, not just until the import finishes. Problems with imported content often show up days later.
If you want this to happen on a schedule rather than by hand, and copied off-site automatically, that is what BackupScope Pro adds.
Step 2: Measure storage before you start
Write down how much space the site uses before the import. It takes a minute and turns "the hosting plan is full, why?" into a simple comparison later.
BackupScope Storage Insights is a free, read-only plugin for this. One analysis shows media, plugins, themes, the database and stored backups as a chart, with details per folder and table. Run it once now. After the import, run it again, and it shows the change since the previous analysis.
Pay attention to two numbers:
- Media (uploads): this is where the import will land.
- Free space on the server or plan: how much room the import has.
Step 3: Import in batches
Do not import the whole archive in one go. Batches of 20 to 50 documents are a good size:
- Import a batch.
- Check a few posts properly: headings, lists, tables, images and links.
- Fix whatever is wrong in the source documents or the import settings, not post by post.
- Then start the next batch.
A mistake found in batch one costs one batch. Found in batch ten, it costs ten.
For Word and Markdown files, DocxToWP imports documents with their formatting and images as real WordPress blocks. The free plugin does one document at a time with a preview; DocxToWP Pro imports up to 100 at once and can roll a whole import back. The archive migration guide on docxtowp.com covers naming, post types, batching and publishing schedules in detail.
Step 4: Check what the import did to your storage
When the last batch is in, run the storage analysis again and compare:
- How much did media grow? Divide by the number of documents to get a figure per document. It tells you what the rest of the archive will cost if you are not done yet.
- Which upload folders grew? Media is stored by year and month, so the import shows up as one or two very large month folders.
- Are there unexpectedly large files? A document with an embedded high-resolution photo or scan can bring a 10 MB image with it. The largest files list makes these easy to spot.
If the numbers are higher than you expected, Keep your media library lean when publishing from Word explains where the space goes and what to do about it.
Step 5: Back up again
Once the archive is imported and checked, take a new full backup. This is now your new known-good state. Keep the "before" backup as well until you are sure you will not need it.
A short checklist
| Step | Done |
|---|---|
| Full backup (files and database), downloaded off the server | ☐ |
| Storage measured before the import | ☐ |
| First batch imported and checked | ☐ |
| Remaining batches imported, one at a time | ☐ |
| Storage measured again, and compared | ☐ |
| New full backup of the finished site | ☐ |
None of these steps takes long. Together they mean the archive can only go one way: onto your site, with a way back if it does not.
Frequently asked questions
Do I need a backup if my import tool can undo an import?
Yes. An undo removes the posts the import created. It does not cover anything else that changed on the site at the same time, and it cannot help if the server itself has a problem. A backup covers the whole site.
How much will the import add to my disk space?
Mostly images. Each picture in a document is uploaded to the Media Library, and WordPress then creates several resized copies of it. Text adds very little. Measure before and after rather than guessing.
Should I import everything at once?
No. Batches of 20 to 50 documents are easier to check, and a mistake in the first batch is cheap to fix.
Backup your site. Understand your storage. Clean it safely.
BackupScope makes full, verified backups of your files and database, built for large sites. Pro adds schedules, off-site copies, restore, storage analytics and safe cleanup.