What moves where

A post is served at its WordPress address, such as /2025/12/hello/, when you keep the addresses and the source's posts share a structure. A category is served at its chain of parents, as WordPress writes it. See Choose how post addresses move.

A post keeps its title, slug, content, excerpt and featured image. A sticky post becomes featured. A post that is pending review, private, password-protected or scheduled at the source comes in as a draft, and its item says so, such as Private at the source, so a draft. A post is in the language the source names for it, and the posts that are translations of each other are joined as one group. A post whose language the site does not publish in waits for your decision.

A category or a tag the site already has waits for your decision. It is found by the slug the Blog stores, so it is matched exactly. Connect to the existing record makes the item that record: nothing is written, the posts that name it are linked to it, and it is kept as it is. Import as new with another slug writes it as its own, with its source id after its slug. See Settle what needs your decision.

A page's path is the path of its address at the source, without the host and the trailing slash. Each segment is written in Latin letters, so /Café is /cafe, and a segment with no Latin letter is written as page- and eight generated characters. See How slugs and page addresses are made. Its content is converted to the CMS's markup. Pieces the importer cannot convert are offered to plugins, and what no plugin converts is kept as text. A page built with Elementor widgets the CMS has no equivalent for waits for your decision.

A file is downloaded from the host you named, and its name and folder are made as the CMS names them. A file on another host, such as a CDN, is skipped with Its file is not on the source's own site, so it is left there. A file whose type or size Media does not take is skipped with the reason. The CMS checks that a file's first bytes are the type its name says. Two files with the same content are found only when they are downloaded, so only the import can ask you about them.

Each menu waits for you to say where it goes: Header links, Footer links, A component or Leave out. A menu with groups becomes a group in the bar. If the site's header or footer already has links, the menu asks whether to keep the site's own or replace it.

Every address a WordPress visitor knows is a redirect item: a post's, a category's, a tag's, a page's and a file's address, the old slugs of a post, the feeds, the sitemaps, the list pages, the day archives, the pages of a paged list and each author's archive. A rule sends the address with a 301 to where the site serves what it points at. A feed or a day archive goes to the Blog's list of posts, and a sitemap goes to the site's own /sitemap.xml.

A redirect is written only to an address the site serves. An item is skipped, with the reason, when:

• the source gives no address for it: No public address at the source;
• what it points at was not imported: What it points at was not imported, or Its post was not imported;
• no visitor can open what it points at, such as a draft: What it points at is not public on the site, so it has no redirect;
• the site already serves it at that address: Already at its old address, or, for the posts list, The Blog's list of posts is served at its address.

An old address that the site already redirects is not overwritten: that item fails with the CMS's reason and the site's rule stays. The dry run plans the redirects as the import writes them. With no redirects chosen, every item is skipped as Left out by this run's choices.

• Run options
• Choose how post addresses move
• Redirect an old address and Upload and organize media in the Mishka CMS documentation.