WordPress Importer


WordPress Importer は、WordPress エクスポートファイルから以下のコンテンツをインポートします。

  • 投稿、ページ、およびその他のカスタム投稿タイプ
  • Comments and comment meta
  • カスタムフィールドと投稿メタ情報
  • Categories, tags and terms from custom taxonomies and term meta
  • 投稿者

For further information and instructions please see the documention on Importing Content.



  • import_allow_create_users: あなたが既存のユーザーだけを関連付けたいのであれば偽 (false) を戻します
  • import_allow_fetch_attachments: あなたが添付ファイルのインポートやダウンロードを望まないのであれば偽 (false) を戻します
  • import_attachment_size_limit: 保存の際のファイルサイズ制限をバイト整数値で戻します (デフォルトは0で、この状態は制限なしとなります)


  • import_start: エクスポートファイルがアップロードされ、作成者のインポート設定が選択された後に発生します
  • import_end: インポーターからの最終出力後に呼び出されます



  1. WordPress ダッシュボードで「ツール → インポート」画面に移動
  2. インポーターの一覧から WordPress へのリンクをクリック
  3. 「いますぐインストール」をクリック
  4. 最後に「プラグインを有効化してインポートツールを実行」をクリック


  1. wordpress-importer フォルダを /wp-content/plugins/ ディレクトリへアップロード
  2. WordPress の「プラグイン」メニューから有効化
  3. 「ツール → インポート」画面に移動し、WordPress をクリック



エクスポートファイルのサイズが非常に大きい場合、インポートスクリプトの動作がホスティングサービスの設定した PHP のメモリ上限によって制限されてしまうことがあります。

A message like “Fatal error: Allowed memory size of 8388608 bytes exhausted” indicates that the script can’t successfully import your XML file under the current PHP memory limit. If you have access to the php.ini file, you can manually increase the limit; if you do not (your WordPress installation is hosted on a shared server, for instance), you might have to break your exported XML file into several smaller pieces and run the import script one at a time.


Support Article: Importing Content


I'm giving this two stars not one, because previous attempts left half the images behind, but I have now at least managed to get all the posts and all the images into the new WordPress site... from the previous WordPress.com site. Horrible though. Had to split a relatively small blog (55 posts) into 11 blocks, get my host to raise the timeout massively, change PHP settings, deactivate everything in sight... and I still had to push through 503 errors, STILL getting timeouts after (e.g.) 10 minutes importing a block of 5 posts, re-running several of the imports... But the worst thing is that it pulled down two copies of each image, creating a second unattached copy of the thumbnail and displaying that rather than the 'real' image, which is then viewable by clicking on the thumbnail. Some thumbnails also then displayed bigger than they are, so fuzzy too. Going to have to go through every post manually, replacing the 'ghost' image with the real one, and then deleting it. Just hoping ALL the images really are there. If it turns out the blog author didn't always link to the media file, I may find some are missing and have to back and look for them. Horrible horrible horrible... and that's going from a WordPress blog to a WordPress blog... what can be so hard?!
Dear Team Plugin is working fine, great work, I would like to suggestion if allow more data file size it will great help for people. This time plugin have (Maximum size: 4 MB) that is not enough. Please increase file size to make more useful Thank you
Importing a couple dozen posts including attachments: ✓ Importing a couple dozen pages including attachments: ✓ Importing ~100 media files including attachments: ✗ HTTP 503. I've tried disabling leech & hotlinking protection on the source domain. I've tried increasing the PHP memory_limit to 512MB, max_execution_time to 0 (unlimited), max_input_time to -1 (same as max_ececution_time), post_max_size to 128MB, upload_max_filesize to 128MB. Note that the media files I was attempting to import were less than 100MB combined. But I kept getting a HTTP 503. The way I eventually got around it was as follows: start the import of media, including attachments. When it fails, do it again, but this time without attachments. You will get a list showing you which media files were actually imported already and which haven't been imported. Now edit the xml file and remove all entries (delimited by <item>…</item>) that have already been imported. Start the media import again, with the edited xml file and include attachments. If it fails again, repeat the import but without attachments. Note files already imported, remove from xml file, rinse and repeat. Tedious? Perhaps. This plugin's fault? I honestly don't know. My cheap hoster's fault? Entirely possible. My skills not being as good as I think they are? Definitely an option. But was it the quickest way to get the job done? Yes, for me it was. Hopefully this information can help someone else. Or perhaps at least it'll help the plugin author to make this plugin more foolproof 😉
Timing out on a perfectly healthy VPS after importing only 25 posts and their media attachments. Have to workaround by migrating to a locally hosted site, then using a working migrator tool to the online site. Could there be an option to split XML into smaller chunks? I realise this is difficult to get to work everywhere, but I always advise people starting out a website and not sure how much effort they will put in to start a wordpress.com site, and its easy to upgrade. Thats a big part of what makes wordpress such a great platform for all kinds of users. When its so difficult to migrate to a self hosted wordpress, then its the opposite just a pain in the butt.


WordPress Importer はオープンソースソフトウェアです。以下の人々がこのプラグインに貢献しています。


“WordPress Importer” は55ロケールに翻訳されています。 翻訳者のみなさん、翻訳へのご協力ありがとうございます。

“WordPress Importer” をあなたの言語に翻訳しましょう。

開発に興味がありますか ?

コードを閲覧するか、SVN リポジトリをチェックするか、開発ログRSS で購読してみてください。



  • Update minimum WordPress requirement to 3.7 and ensure compatibility with PHP 7.4.
  • Fix bug that caused not importing term meta.
  • Fix bug that caused slashes to be stripped from imported meta data.
  • Fix bug that prevented import of serialized meta data.
  • Fix file size check after download of remote files with HTTP compression enabled.
  • Improve accessibility of form fields by adding missing labels.
  • Improve imports for remote file URLs without name and/or extension.
  • Add support for wp:base_blog_url field to allow importing multiple files with WP-CLI.
  • Add support for term meta parsing when using the regular expressions or XML parser.
  • Developers: All PHP classes have been moved into their own files.
  • Developers: Allow to change IMPORT_DEBUG via wp-config.php and change default value to the value of WP_DEBUG.


  • PHP7 の互換性の改善。
  • インポートされたコメントからスラッシュが消えてしまうバグを修正。
  • wp_get_http()screen_icon() を含む廃止されたお知らせが表示されないように修正。
  • マルチライン項目メタデータのエクスポートファイルをインポートする際のバグを修正。


  • インポート項目メタデータのサポートを追加。
  • スラッシュがインポートした内容から無くなるバグを修正。
  • 一部のケースで CDATA 内のキャラクターが無くなるのバグを修正。
  • PHPの通知を修正しました。



  • WXR 1.2 および複数の CDATA セクションへの対応
  • post_type が異なる場合は重複投稿とはみなされません


  • Double check that the uploaded export file exists before processing it. This prevents incorrect error messages when
    an export file is uploaded to a server with bad permissions and WordPress 3.3 or 3.3.1 is being used.


  • コメントメタ情報をインポート (WordPress 3.2 以降からのエクスポートファイルが必要です)
  • 小さなバグの修正と改善


  • 可能であればコメントと user_id を関連付けます。
  • wp:attachment_url から添付ファイルをインポート
  • 正しいディレクトリに添付ファイルをアップロード
  • サイズを変更した画像の URL を正しく再割り当てします。


  • 利用できる場合は XML パーサーを使うようにした
  • ナビゲーションメニューの適切なインポートに対応
  • その他多数。詳細は Trac チケット #15197 を参照。


  • 最初のリリース