SETUP
Log into your Synology device and do the following:
Go to the CONTROL PANEL and click WEB SERVICES.
Make sure you tick ENABLE WEB STATION and also ENABLE MYSQL.

Go to the PACKAGE CENTRE.
Install phpMyAdmin.
If you go to FILE STATION you should see a folder called WEB, and in there are the various folders that have been created to let you do your own thing.
Create a folder under the folder WEB and call it the name of the site you are looking to import. As an example, http://hightechrailandfence.com could sit in a folder called TAS. You can call it anything you like.
Go back to the Control Panel, click on Web Services again, and then click on VIRTUAL HOST. Click on create, and enter the folder name you created earlier. The hostname should be set to local. Change the port to 81 or whatever one you prefer. (You can change the hostname to your WAN ip address and port to whatever you want, if you wish to access this site from the Internet. You will have to set up port forwarding in your router for this work correctly.)
Now go to phpMyAdmin, and at the top, click on DATABASES.

Now you need to create a name for the database, so I’ll stick with tas as that is the folder I’m working in and an abbreviation for the site I have live. Just click create.
MIGRATION
Copy importbuddy.php and hightechrail.zip to the folder you created above under WEB.
Using a web browser, navigate to http://synology_ip_address/folder_you_created/importbuddy.php
Step 1: Authentication Required & Choose Your Backup File
- You’ll be prompted to Enter your ImportBuddy password to continue. For more information about setting your ImportBuddy password, visit the ImportBuddy Password page.
Password is hightech.

- Step 1 also prompts you to choose your backup file for the migration. These file options are divided into three tabs: Server, Upload and Stash.
- Server – This tab lists backup files currently on the server. Select one to use for the migration.

- Server – This tab lists backup files currently on the server. Select one to use for the migration.
Step 2: Unzipping Backup File
Step 2 unzips the backup file. There is nothing you need to do for this step. Just select Next Step once the extraction has completed.

Step 3: URL and Database Settings
Step 3 is where you will enter the database settings for the new location.

- Enter the following URL settings:
- WordPress Address – This is the address where you want the final WordPress site you are restoring / migrating to reside. Ex:
http://foo.com/wp - Use optional custom site address (Home URL)? – OPTIONAL. This is also known as the site address. This is the home address where your main site resides. This may differ from your WordPress URL. For example:
http://foo.com
- WordPress Address – This is the address where you want the final WordPress site you are restoring / migrating to reside. Ex:
- Enter the following Database Settings:
These settings control where your backed up database will be restored to. If you are restoring to the same server, the settings below will import the database to your existing WordPress database location, overwriting your existing WordPress database already on the server. If you are moving to a new host you will need to create a database to import into. The database settings MUST be unique for each WordPress installation. If you use the same settings for multiple WordPress installations then all blog content and settings will be shared, causing conflicts!- MySQL Server – This is the address to the mySQL server where your database will be stored. 99% of the time this is localhost. The location of your mySQL server will be provided to you by your host if it differs.
- Database Name – This is the name of the database you want to import your blog into. The database user must have permissions to be able to access this database. If you are migrating this blog to a new host you will need to create this database (ie using CPanel or phpmyadmin) and create a mysql database user with permissions.
- Database User – This is the database user account that has permission to access the database name in the input above. This user must be given permission to this database for the import to work.
- Database Pass – This is the password for the database user.
- Database Prefix – This is the prefix given to all tables in the database. If you are cloning the site on the same server AND the same database name then you will want to change this or else the imported database will overwrite the existing tables.
- Once you’ve entered all the new database information or created your new database, you will need to test the settings. If the test is successful, you will be able to move on to Step 4. If the test fails, however, verify all of your database settings are correct and run the test again. Click Test Database Settings to start the test.

- Once the test is successful, click Next Step.
Step 4: Database Import
Step 4 imports the database information into the database of your new site. Once the import is completed, click the Next Step button.

Note: Advanced options are also available during Step 4. These advanced options allow customizations of various ImportBuddy functionality for custom purposes or troubleshooting. Exercise caution as some advanced options may have unforseen effects if not used properly, such as overwriting existing files or erasing existing database content.
Step 5: Database Migration
Step 5 updates all of the URLs, paths, etc. on your site to match your new site.
- Before you move to the final step, be sure to go to your new site and check all of your links to ensure they have changed. You may view your entire import log for providing to support by clicking the View Import Log button.
- Once you’ve tested your new site, you can move to the final step by clicking Clean up & remove temporary files.

Simple Problems & Solutions
- Clicking on a posts results in a 404 Not Found – This is typically caused by a problem with your .htaccess file. Log into your wp-admin, navigate to Settings: Permalinks in the WordPress menu and click the “Save” button to update permalink settings to your .htaccess file. This typically resolves this problem.
- Logging in redirects back to the old site – This is usually caused by entering the source site URL as the destination URL on Step 3. Re-restoring using the correct URL should fix this problem.
- Source site has changed to the destination URL – This is caused if you restored over your source site database by entering the source site database settings on Step 3. You may re-restore using correct settings. You may correct the modified URL on the source site by using the Server Information page’s Mass Text Replace tool.
Step 6: Final Cleanup
Step 6 removes any temporary files from your new site that were used for the migration. Your site will then be ready at the URL indicated on this page.










