1. In source site, save the database using phpmyadmin.

1.1. In phpmyadmin, ->  データベース ->  relevant database (wpdb) -> エクスポート -> 詳細　-> select relevant tables -> 　実行　:     source.sql

In selecting the tables, you need prefix of tables, which can be found in the wp-config.php of the  wordpress now exporting.

You need to remember this prefix when importing the database to the target site.

1.2. Xport the files: ftp dump whole “wp-content” to the PC. FFFTP is convenient.

2. In target site:

2.1. If the target is multidomain site, check the database prefix used for those.

2.1.1.  If none of them uses the prefix of the one used in the source site, simply import the source.sql using phpmyadmin of the target site.

2.1.2. If there is a site which uses the same prefix of the source.sql, you have to remove the tables related to that, which means that site must be killed, and then import the source.sql, which means source site wil be migrated to this site.

2.1.3. If none of the target sites is using the same prefix as that of the source site, you can safely import the source.sql.

2.2. Prepare a directory for the target site.

2.2.1. If the directory or wordpress site which is assigned the above prefix does not exist, create a directory and dump, not install, new wordpress files and directories to that directory and then remove “wp-content” from that directory.

2.2.2. If the prefix is assigned to the already existed and removed database wordpress directory, remove the “wp-conten” directory from that directory.

2.3. Edit “wpconfig.php” in that directory so that the above mentioned prefixed database should be used.

2.4. Place searchreplacedb2.php (renamed knsecret.php) in that directory and visit that file (e.g. http://newsite(/newdirectory)/knsecret.php)

2.5. Follow the instruction:

replace source_url (e.g. 192.168.0.16/wptest)

with target_url (e.g. norikoguide.pepper.jp/norikoshop).

Note: leading “http://” should not be included,  nor trailing “/ “.

3. You visit the new site.  It would be all right as the old site. Finally don’t forget to remove “searchreplacedb2.php” (knsecret.php). To avoid the danger of cracking.