Who This Is For / When to Use
Use this guide if you are importing a WordPress site into Kyrios and encounter errors such as File Corrupted, Plugin Corrupted, or Unknown Error during the import or migration process.
Understanding WordPress Import Errors in Kyrios
Kyrios performs validation checks when importing a WordPress site. If corrupted files or plugins are detected, the import is stopped to prevent incomplete or unstable site migrations.
Error: File Corrupted
What This Means
The uploaded WordPress export file (such as a .wpress file) is damaged or incomplete. This corruption may originate from:
The current WordPress installation
A previous source installation used to generate the export
How to Fix
Delete the corrupted import file from Kyrios.
Return to the source WordPress site.
Re-export the site using the recommended migration plugin.
Upload the newly generated file and retry the import.
Error: Plugin Is Corrupted
Example Error Message
Plugin named “yith-topbar-countdown” is corrupted.
What This Means
A plugin included in the WordPress export package is corrupted or incompatible. This may exist in:
The current WordPress installation, or
The source installation where the export file was created
How to Fix
Log in to the source WordPress admin panel.
Locate the corrupted plugin (for example, yith-topbar-countdown).
Delete the plugin completely.
Re-export the WordPress site.
Upload the new file to Kyrios and retry the import.
If needed, reinstall the plugin later after migration using a fresh version.
Error: Unknown Error (Plugin or File Conflict)
What This Means
An unknown error typically indicates both plugin and file corruption.
How Kyrios Detects This
Kyrios first checks for plugin-related issues and displays a specific plugin error if found.
After the plugin issue is resolved, Kyrios re-evaluates the file.
If file corruption still exists, the error message updates to File Corrupted.
How to Fix
Remove any plugins flagged as corrupted.
Re-export the WordPress site.
If the error persists, delete the corrupted file.
Create a fresh export and retry the import.
Best Practices to Prevent Import Errors
Disable unnecessary plugins before exporting.
Update WordPress core and plugins before migration.
Use only supported migration plugins.
Avoid interrupting the export process.
Do not reuse old or previously failed export files.
Frequently Asked Questions
What should I do when I see a file corruption error?
Delete the corrupted file and generate a new export from the source WordPress site.
How do I fix corrupted plugin errors?
Remove the corrupted plugin, re-export the site, and reinstall the plugin after migration if needed.
What if both plugin and file errors appear?
Always resolve plugin issues first. If the error then changes to file corruption, delete and regenerate the export file.
Can plugin conflicts cause these errors?
Yes. Conflicting or outdated plugins can corrupt exports. Disable all plugins and re-enable them one by one to identify the cause.
Where does the corruption usually come from?
Corruption may originate from the current WordPress installation or the source installation used to create the export file.