Migration Guide: Move to Postion Seamlessly
Move your content from platforms like WordPress, Substack, or Medium into Postion with a cleaner migration plan for content, domain, structure, and audience continuity.
This doc was refreshed on March 31, 2026 to better reflect the current product workflow and implementation details.
- Reframed the guide around migration planning rather than just export steps.
- Added pre-migration and post-migration checklists to reduce avoidable mistakes.
- Tightened platform-specific instructions so the guide works better as a transition playbook.
TL;DR
- A strong migration is not just an import. It is a transition plan for content, URLs, audience communication, and future growth.
- The safest workflow is export first, import into Postion, review the imported library, then handle domain and structure changes deliberately.
- Most migration problems come from rushing redirects, skipping content review, or treating old and new information architecture as the same thing.
- Post-migration work matters just as much as the import itself if you want to preserve trust and search value.
Best for
- Creators moving from WordPress, Substack, Medium, or a patchwork publishing stack.
- Teams planning a content migration without losing control over domain, structure, and audience continuity.
- Operators who need a practical checklist before switching the public-facing site.
What a Good Migration Actually Includes
Migration is not only about moving files from one platform to another.
A good migration also protects:
- your content library,
- your audience relationship,
- your information architecture,
- and your future search and monetization potential.
Use this guide to plan the move in three phases:
- prepare the archive,
- import and review,
- switch the public-facing experience carefully.
Before You Migrate
Do these steps before uploading anything.
1. Decide What You Are Moving
Separate your content into three groups:
- keep and improve,
- keep with light cleanup,
- do not bring forward yet.
Migration is a good time to prune weak, outdated, or off-strategy content instead of importing every artifact by default.
2. Protect Your Source Data
Before making changes:
- export the full archive from the current platform,
- keep a local backup,
- and save any subscriber or audience data you are allowed to export.
Treat the source export as a recovery point, not a disposable file.
3. Map Critical URLs and Assets
Identify:
- your highest-traffic pages,
- your best-converting pages,
- your most-linked pages,
- and any evergreen assets that must survive the transition cleanly.
Those pages deserve the most careful review after import.
Platform-Specific Export Paths
WordPress
Typical flow:
- Open the WordPress export tools.
- Export the content archive.
- Save the export file locally before importing it into Postion.
This is usually the best option when your WordPress site is the current source of truth.
Substack
Typical flow:
- Request the export from your Substack settings.
- Download the archive when it is ready.
- Extract the relevant content file before importing into Postion.
If subscriber continuity is part of your plan, make sure you separately review what audience data can be exported and how it should be handled.
Medium
Typical flow:
- Request your account export from Medium.
- Download and unpack the archive.
- Use the exported post files as the import source.
Medium migrations often need a closer formatting review after import, so budget time for cleanup.
Importing into Postion
Once the export files are ready:
- Open the import area in your Postion dashboard.
- Choose the source platform that matches your archive.
- Upload the required file or files.
- Wait for the import process to complete.
- Review the imported library before changing your public domain or announcing the move.
The import step moves content, but it does not automatically decide how your new site should be structured.
Review the Imported Library Before Going Live
This is the step many people rush.
After import, review:
- post titles,
- slugs,
- formatting,
- images and embeds,
- internal links,
- tags or categories,
- and any premium or gated content logic.
If the imported content is messy, publishing it immediately only moves the mess to a new domain.
A Safer Post-Migration Setup Sequence
Step 1: Clean the Structure
Organize the imported library so related assets connect clearly.
This is a good time to:
- merge thin duplicates,
- clarify ambiguous titles,
- and group posts into stronger topic paths.
Step 2: Set Up the Domain Intentionally
If the new site is becoming your main public property, connect the domain after the content review is in good shape.
Use:
Step 3: Rebuild the Growth Layer
Once the content is stable, strengthen:
- internal links,
- SEO structure,
- email capture,
- and monetization paths.
Useful next reads:
Migration Checklist
Before Import
- export the full archive,
- save a local backup,
- identify high-value pages,
- and decide what should or should not come over yet.
After Import
- review formatting and images,
- check internal links,
- rework the content structure,
- and confirm your key pages still support the business goals of the new site.
Before Public Launch
- connect the correct domain,
- check canonical public URLs,
- verify the main navigation,
- and make sure top pages are ready for discovery and conversion.
Common Migration Mistakes
- importing everything without reviewing quality,
- treating old structure as automatically correct for the new site,
- switching the domain before reviewing key pages,
- forgetting to reconnect monetization and audience systems,
- and announcing the move before the new experience is ready.
Recommended Next Reads
A useful migration rule: first make the new site accurate, then make it public, then make it loud. The order matters.