Interrupting a large WordPress import can corrupt your database and cause hours of cleanup. Learn why this happens and discover three robust solutions, from a quick plugin fix to the professional-grade WP-CLI method, to ensure your data migration is safe and reliable.

Can I Turn Off My PC During a WordPress Import? A Senior Engineer’s Take

I remember it like it was yesterday. It was 2 AM, the night before a huge e-commerce client’s Black Friday launch. A junior engineer was tasked with a “simple” final product import—about 50,000 SKUs with complex variations. He kicked it off from his browser, saw the progress bar moving, and figured he could head home and let it run. An hour later, I get a frantic call. The site is throwing 500 errors. Turns out, his laptop went to sleep, the connection dropped, and the import process died halfway through, leaving the `wp_posts` and `wp_postmeta` tables in a horrifyingly corrupt state. We spent the next four hours restoring a database backup and re-running the import the right way. That night taught me a valuable lesson: never, ever trust a browser connection for a critical, long-running task.

The “Why”: What’s Actually Happening on the Server?

When you click “Run Import” in the WordPress admin dashboard, you’re not running the process on your computer. Your browser is just sending a request to your web server (like Apache or Nginx) telling it to start a PHP script. This script is what reads your CSV or XML file and inserts data into the database.

The problem is that this entire process is tied to your browser’s connection. Here’s the chain of failure:

• Your PC goes to sleep, you close the tab, or your Wi-Fi hiccups.
• The connection between your browser and the server is broken.
• The web server, sensing the client has “hung up,” eventually kills the PHP process to free up resources. This is governed by server settings like `max_execution_time`.
• Your import script stops abruptly, midway through creating a product or updating metadata, leaving your database in an inconsistent, corrupted state.

So, how do we run these tasks reliably without babysitting a browser window? Here are the solutions, from the quick-and-dirty to the way we do it on our production environments.

Solution 1: The Quick Fix – Use the Plugin’s Cron Processing

Most good import plugins, including WP All Import, have a built-in mechanism to handle this. Instead of running the entire import in one go, they can break it into smaller chunks and process them every few minutes. This is designed to be triggered by the WordPress cron system (`wp-cron.php`). You’re essentially telling the plugin, “Hey, you handle this in the background, I’m going to close my browser now.”

You’ll typically find this in the import settings, often under an “Advanced” or “Scheduling” tab. It will give you a couple of URLs to use. While this is better than nothing, it has a major weakness.

Warning: WordPress cron isn’t a “true” cron. It only runs when someone visits your website. If you have a low-traffic site, your import could sit there for hours between chunks, or stall completely overnight. It’s convenient but not reliable for time-sensitive or mission-critical tasks.

Solution 2: The Permanent Fix – A Real Server-Side Cron Job

This is the next level up and the first step toward a professional setup. Instead of relying on site visitors to trigger `wp-cron`, we’ll tell the server itself to trigger the import processing on a reliable schedule. This requires command-line access to your server.

First, get the cron command URL from your import plugin’s settings. It will look something like this: http://your-site.com/wp-cron.php?import_id=1&import_key=yoursecretkey&action=processing.

Next, SSH into your server and edit the crontab:

ssh myuser@my-server-ip
crontab -e

Then, add a line that tells the server to fetch that URL every five minutes. We use `wget` or `curl` for this and pipe the output to `/dev/null` so it doesn’t generate useless log files.

# Run the WP All Import processor every 5 minutes
*/5 * * * * wget -q -O - "http://your-site.com/wp-cron.php?import_id=1&import_key=yoursecretkey&action=processing" > /dev/null 2>&1

Now, the server itself will ensure your import chunks are processed reliably, every five minutes, whether you have site traffic or not. You can safely turn off your PC.

Solution 3: The ‘Nuclear’ Option – WP-CLI in a Detachable Session

This is how we handle all major data operations at TechResolve. It’s the most robust, direct, and transparent method. It completely bypasses the web server (and its timeouts) and runs the PHP script directly. This requires that you have WP-CLI and the plugin’s WP-CLI add-on installed on your server.

The magic ingredient here is a terminal multiplexer like `screen` or `tmux`. These tools create a persistent terminal session on the server that you can detach from and re-attach to later. The session, and any command running inside it, will keep going even after you disconnect your SSH session.

Here’s the workflow:

1. SSH into your server:

   ssh myadmin@prod-web-01

2. Start a new `screen` session: We give it a descriptive name so we know what it is later.

   screen -S product_import

3. Navigate to your WordPress directory and run the import: Use the WP-CLI command for your plugin. You’ll need the import ID from the plugin’s UI.

   cd /var/www/html
   wp all-import run 5 --allow-root

4. Watch the progress! You will see the script’s direct output in your terminal. No more guessing.
5. Detach and go home: Once you see it running smoothly, press Ctrl+A, then press d. This detaches you from the `screen` session, but leaves it running on the server. You can now safely log out and shut down your computer.
6. Check on it later (optional): If you want to see how it’s doing, SSH back in and re-attach to the session:

   screen -r product_import

Pro Tip: Using WP-CLI with `screen` or `tmux` is a fundamental DevOps skill. It’s not just for imports; it’s perfect for any long-running command-line task, like database migrations, file syncing with `rsync`, or running complex build scripts.

Which Method Should You Choose?

So, can you turn off your PC? Absolutely—as long as you’ve handed off the responsibility from your fragile browser connection to a durable, server-side process. Don’t be the engineer who takes down a site before a big launch. Learn to use the right tools for the job.

Darian Vance

Lead Cloud Architect & DevOps Strategist

With over 12 years in system architecture and automation, Darian specializes in simplifying complex cloud infrastructures. An advocate for open-source solutions, he founded TechResolve to provide engineers with actionable, battle-tested troubleshooting guides and robust software alternatives.

🤖 Frequently Asked Questions