> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stackshift.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Import an existing WordPress site

> Bring an existing WordPress site onto StackShift by uploading a content-and-database archive; StackShift provisions a native site and migrates your content into it.

<Warning>
  **Live with caveats.** This area is real and usable, but the docs intentionally call out operational or UX limits that still matter.
</Warning>

## Goal

Migrate an existing WordPress site onto StackShift’s native runtime instead of rebuilding it by hand.

## Prerequisites

* An export of your current site as a wp-content + database archive (a single zip)
* The source site URL the export came from
* The WordPress version the export was taken from

## Workflow

<Steps>
  <Step>
    Export your current site as a content-and-database archive (wp-content plus a database dump) and zip it.
  </Step>

  <Step>
    Start an import: provide a name, the source site URL, the WordPress version, and upload the archive.
  </Step>

  <Step>
    StackShift provisions a fresh native WordPress site (managed MySQL + runtime) and migrates your package into it.
  </Step>

  <Step>
    After the migration completes, reset the admin password and point your domain at the new site.
  </Step>
</Steps>

## Supported import format

Import currently accepts one format: a wp-content-and-database archive (the wp-content directory plus a database dump, packaged as a zip). Other migration formats are not accepted today.

## What you provide

* A site name.
* The source site URL (an absolute http or https URL) so links can be remapped.
* The WordPress version the export came from — this is required for import.
* The archive package itself.

## How the import runs

Under the hood an import creates a normal native WordPress site and then restores your package into it, so you end up with the same managed-MySQL, native-runtime shape as a fresh deploy. The site is created with a temporary import admin user, so after migration you reset the admin password and update the site URL to your real domain.

## Limitations

* Multisite import is not supported in v4. To move an existing network, create a fresh multisite network on StackShift and migrate its content separately.

## Expected result

<Check>
  Your existing WordPress content runs on StackShift’s native runtime, backed by a managed MySQL database.
</Check>

## Common failures

<Warning>
  * Uploading an unsupported format — only the wp-content-and-database archive is accepted.
  * Omitting the source site URL or the WordPress version (both required for import).
  * Attempting a multisite import — not supported in v4.
</Warning>

## Related guides

<CardGroup cols={2}>
  <Card title="Deploy WordPress on StackShift" href="/wordpress/deploy-wordpress-on-stackshift">
    Launch single-site WordPress on the native Apache + PHP runtime with an auto-provisioned managed MySQL database and persistent storage.
  </Card>

  <Card title="Connect a custom domain to WordPress" href="/wordpress/connect-a-custom-domain-to-wordpress">
    Understand how StackShift routing and WordPress site URLs interact before and after first boot.
  </Card>

  <Card title="WordPress Control Surface" href="/wordpress/wordpress-control-surface">
    A first-class operational surface for direct WordPress projects: overview, narrow safe actions, diagnostics, and recent history.
  </Card>
</CardGroup>