Source: https://docs.amadalis.ai/content/imports-and-transfer/

# Import and site transfer

In the site admin, open **Settings** > **Transfer** for EmDash site packages. Read the import distinction below before choosing a WordPress migration route.

Checked against the product’s code on 7 November 2026.

Praxis includes EmDash’s **Import from WordPress** and **Transfer** screens. They are separate from the **Migration** workspace used to review a move with Amadalis.

## EmDash’s WordPress import

You need an Admin role for EmDash’s WordPress import. This is separate from **Migration**.

1.  Choose **Import** in the site admin navigation.
2.  Check that **Import from WordPress** is the intended screen.
3.  Choose the agreed source: a WordPress address and migration key, or a WordPress [export](https://docs.amadalis.ai/reference/glossary/#export) file.

The importer can show connection, review, import and media stages. The migration key is the connection credential supplied by EmDash’s exporter.

Before starting:

1.  Review the collections and fields the importer proposes.
2.  Review author mapping.
3.  Review menus.
4.  Review [taxonomies](https://docs.amadalis.ai/reference/glossary/#taxonomy).
5.  Review settings.

If the importer proposes a block field, which holds structured page components, the hosted site refuses the step and nothing is changed; choose another field type, such as formatted rich text.

For a move being handled by Amadalis, follow [Migration as a service](https://docs.amadalis.ai/agencies/migration-as-a-service/) and use the agreed source route. EmDash’s importer and the Praxis Migration workspace have different review and recovery flows. Do not run both over the same work without agreeing the plan.

## Export a site package

Only an Admin can export. The package carries all content, drafts and trash included, media files and site settings, and each author’s name and email address. Store and share the file as carefully as the site itself.

1.  Open **Settings**.
2.  Open **Transfer**.
3.  In **Export**, read **What the package includes**.
4.  Read **What it leaves out**.
5.  Choose whether to **Include comments**.
6.  Choose **Export site**.

Keep the page open while the export advances. If you leave, return to continue it.

1.  Read whether the export is ready, failed or expired.
2.  When it is ready, use **Download package** or **Download as one file**, as offered.

Review failed or expired exports before relying on a download.

The package is an EmDash transfer package file. It is not the same as the visitor datasets exported through **Privacy & Data** > **Exports**.

## Hosted import boundary

Importing a whole site transfer package into a hosted Praxis site is refused. Export remains available. A Dashboard import suggestion does not override that restriction. Ask Amadalis to review a move that needs whole site replacement.