When the next server migration or data incident is looming: Why it needs to become concrete now
Many freelancers, marketing teams and agencies know the scene: a CMS update breaks something, a service announces API access termination, or the agency changes hosting partners. Suddenly the question arises: How do I back up all posts, images, metadata and versions without content gaps or lost author attributions? For operators of a self‑hosted instance, data portability is not a nice extra but an operational fundamental right.
What you specifically need — and how Marqentra helps
For reliable backups and migrations you need four building blocks: complete post exports, media library snapshots, metadata export including taxonomies and author information, and the version history. Marqentra bundles these steps into a central interface so you can schedule, execute and reimport export packages — on your own server and under your control.
Post exports: Securing holistic content
What to watch for: Export not only the text but also all associated fields: title, slug, publication status, categories/tags, author IDs, publication date and any embedded references to media or external links. Marqentra provides an export feature that lets you filter posts by timeframe, channel or status and export them as a package.
Practical tip: Create a short validation checklist before an export: Are all desired channels selected? Does the package include all relevant languages and variants? First export a small test dataset and check structure and readability.
Media library snapshots: Consistently securing images, videos and attachments
The media library is often the biggest risk in data loss. A snapshot captures the file inventory, folder structure, metadata (e.g. alt text, copyright) and links to posts. Marqentra allows creating media library snapshots that you can store compressed or split into multiple parts depending on size.
Practical tip: Keep at least two snapshot generations: a short‑term one (last 30 days) and a long‑term one (monthly archive). Use different storage locations for retention (local + offsite).
Metadata & version history: Context and recoverability
Without metadata, content loses its association and traceability. Export taxonomies, author profiles, custom fields and the version history of individual posts. This not only allows content to be restored but also makes change histories traceable.
Practical tip: Export version history with comments or change notes — this makes remapping to new authors or systems easier during imports.
Step‑by‑step: Backup workflow with Marqentra
- Preparation: Define a backup plan (e.g., daily post exports, weekly media library snapshots, monthly full backup).
- Start export: In Marqentra's export dialog, choose the desired scope (posts, media library, metadata, versions) and the output format.
- Check integrity: Open the export file locally and inspect samples (e.g., 5 posts, 10 media items) for completeness.
- Encryption & transfer: Encrypt sensitive export packages and transfer them to an offsite medium (S3, external NAS, encrypted archive).
- Retention & rotation: Maintain a simple rotation (e.g., 7 days, 4 weeks, 12 months) and document storage locations.
- Automation: Enable scheduled exports so backups run regularly without manual intervention.
Recovery and Migration Checklists
Below you will find two compact checklists that you can work through on site — from emergency recovery to migration between instances.
Recovery Checklist (Emergency Recovery)
- Verify: Identify current export packages and the date of the last successful backup.
- Isolation: Take the defective instance offline to prevent further inconsistencies.
- Restore media: Unpack the media library snapshot and create the file paths on the server.
- Import posts: Import the post export, first testing in a staging environment.
- Apply metadata and versions: Import taxonomies and version history, remap IDs if necessary.
- Integrity check: Perform random checks (media links, links, author assignments).
- Go-live: After successful tests, switch back to the production environment and enable monitoring.
Migration between Servers/Instances
- Preparation: Configure the target system (webspace, PHP/database version) and provision the Marqentra instance.
- Export: Create a complete package (posts + media library + metadata + version history).
- Transfer: Move the package securely to the target server (SFTP, secure cloud storage).
- Import sequence: Media first, then posts, and finally metadata and versions.
- URL/Permalink check: Verify slugs and internal links; implement redirects if necessary.
- Acceptance: Content owners perform spot checks to ensure all content and meta information were transferred.
Further Practical Tips for Secure Exports
- Perform test restores regularly: A backup is only reliable once you have successfully restored it.
- Least privilege: Restrict export and import rights to a small number of administrators.
- Documentation: Maintain a backup log with date, scope and responsible person.
- Offsite and versioning: Keep copies at at least two locations and ensure versions are traceable.
How Marqentra for WordPress fits into the process
If you use WordPress, the complementary component Marqentra for WordPress simplifies publishing and taking over content: you can publish content from your self-hosted instance directly to WordPress or prepare content for migrations in the other direction. This makes portability between your own webspace and WordPress installations more transparent and reproducible.
Conclusion: Data portability as an operational hygiene measure
Backups and export processes are not a luxury but part of the daily operation of your content production. With structured post-exports, media library snapshots, complete metadata and version history you build a resilient system for emergencies and migrations. Marqentra's self-hosted approach ensures you retain control over your content and that exports and restorations occur according to your rules.
Ready to standardize your export and backup processes? Marqentra supports you with centralized export workflows, automated snapshots and integrations with your existing infrastructure. Discover Marqentra and test a demo: https://marqentra.com
Next step
Try Marqentra yourself
Marqentra combines topic discovery, AI-assisted content creation, media management, editorial planning, automated publishing and analytics in a single central system. The standalone Marqentra software runs on your own webspace or server. Marqentra for WordPress is additionally available for WordPress.