Introduction
Many agencies and SMEs face the same issue: years of content history, scheduled social posts and a dense approval workflow scattered across SaaS editorial calendars — with limited exportability, little control over data and dependency on the provider. Migrating to a self‑hosted platform like Marqentra allows you to consolidate all content, assets and workflows into a central system running on your own server. This guide pragmatically describes how to securely export posts, schedules, media and approvals from cloud tools and import them into Marqentra — including account and rights mapping as well as necessary fallback checks.
1. Preparation: Define Audit and Migration Scope
Start with a clear audit: which content should be migrated (published posts, scheduled posts, drafts, campaigns, media library, approval logs)? Record the source systems, file types, user lists and existing integrations. Decide whether the migration should be staged (e.g., social posts first, then blog articles) or performed as a cutover.
Create a backup strategy: full export from the SaaS tool and separate backup of media files. Set up a staging instance of Marqentra on your server to run tests completely isolated from production. If your website uses WordPress, also evaluate the Marqentra for WordPress option for simplified synchronization.
2. Export from the SaaS Tool: What You Need
Export the following data groups from the source system:
- Posts/entries: title, body/HTML, excerpts, slugs, permalinks
- Metadata: publication date or scheduled date, status (published/scheduled/draft), categories, tags, campaigns
- Authors: name, email, user ID
- Media: all linked files (images, PDFs, videos) as well as filenames and, if applicable, checksums
- Approval logs and comment threads: approvers, timestamps, status changes
- Social mappings: channel IDs, channel names, associated accounts
Technically: prefer structured exports (CSV or JSON) or use the SaaS tool's API for complete dumps. For media, a separate bulk download via API or ZIP export is recommended. If the tool only offers CSV, ensure clean CSV columns and consistent time zones in date fields.
3. Standardized Export Template and Field Mapping
Prepare a unified mapping so Marqentra can import the data correctly. A sensible column structure (example) is:
- post_id
- title
- slug
- body_html
- excerpt
- publish_date (ISO‑8601)
- status (published/scheduled/draft/archived)
- author_email
- tags (comma-separated)
- categories
- campaign
- media_filenames (comma-separated)
- approval_status
- created_at, updated_at
Important: standardize date formats and time zones during export. Document the source IDs for authors and channels so they can be unambiguously mapped later.
4. Data Cleansing and User Mapping
Before importing, you should cleanse data: remove duplicate posts, archive outdated drafts, and merge inconsistent tags/categories. Create a user-mapping table that assigns each source user ID or email to a Marqentra user. If an email does not yet exist in Marqentra, plan for automatic invitation or creation of a placeholder account.
Recommendation for roles: start with restrictive permissions (e.g., Reviewer/Author) and raise permissions gradually after the migration is verified. Note any special roles from the SaaS tool that need to be represented in Marqentra (e.g., Campaign Manager, Social Publisher).
5. Asset Import: Check Media and Relink
First upload all media to the media library of your Marqentra instance. Ensure you preserve filenames and folder structures or reassign them systematically. To avoid broken links, replace all old media URLs in the post bodies with the new paths in Marqentra. Use checksums (e.g., MD5) for identity verification when available.
If you have large files or many assets, perform uploads in batches and check server storage limits as well as possible CDN integrations on the server.
6. Import into Marqentra: Order and Practice
Import in the following order to ensure consistency:
- Create or invite user accounts and assign roles.
- Import media and document media IDs.
- Import posts with field mapping (post_id → external_id, author_email → user, media_filenames → media_relations).
- Import schedules and social-channel assignments.
- Attach approval and audit logs as post metadata.
Use the staging instance first for a trial run with a selection of posts (e.g., 20 posts in different statuses). Check preview, media linking, scheduling, and approval history.
For WordPress pages, Marqentra for WordPress simplifies synchronization: posts can be linked directly so changes can be controlled centrally in Marqentra.
7. Mapping Social Accounts and Publishing Rights
Export channel details (e.g., Facebook page, LinkedIn company, Twitter account) and securely store their access credentials in Marqentra. Test each account in a protected mode (test posting or private channel). Assign publishing rights only to roles that should actively post; initially leave reviewers and editors without publishing permission.
8. Fallback checks and go-live test
Before you switch definitively, go through a checklist:
- Keep a complete backup of the SaaS data until the migration has been verified.
- Dry run: simulate scheduled posts in staging and verify actual publication to test channels.
- Spot checks: compare content, metadata, media links, approval logs and timestamps.
- Set up monitoring: closely watch the first 48–72 hours after go-live for failed publications, 404 links or incorrect metadata.
- Rollback plan: define how individual posts or the entire publish flow can be retracted in case of critical errors.
9. After go-live: processes and governance
Train your team in using the Marqentra instance: user management, new workflows, reporting and backup processes. Establish responsibilities for media management and tagging so the media library remains clear. Plan regular reviews of integrations (e.g., Analytics, CRM, Social APIs), as credentials occasionally need renewal.
Why Marqentra for this migration?
Marqentra's self-hosted approach gives you control over your data and infrastructure, while the platform simultaneously consolidates topic discovery, AI-assisted content creation, media management, editorial planning, automated publishing and analytics in one system. For WordPress users, Marqentra for WordPress is a direct bridge to consistently synchronize posts and publishing processes.
Conclusion and next step
Migration from SaaS editorial calendars to a self-hosted platform is plannable and safe if you proceed step by step: audit, export cleanly, consolidate, import in the correct order and test comprehensively. Start with a small test set, validate in staging and only perform the go-live after successful fallback checks.
Discover Marqentra and try a demo: https://marqentra.com
If you wish, we can create a custom migration checklist template for you or accompany the trial run on your staging instance—get in touch with us.
Next step
Try Marqentra yourself
Marqentra combines topic discovery, AI-assisted content creation, media management, editorial planning, automatic publishing and analytics in a central system. The standalone Marqentra software runs on your own webspace or server. For WordPress, Marqentra for WordPress is also available.