Lifestyle
What to check before building or migrating a website with SiteGround
A new SiteGround website and a migration of existing WordPress need different preparation. Check the plan, backups and test environment before buying. Using official documentation, this guide covers new-site setup, Migrator and Staging, plus content, email and user-flow checks before switching over. A timeline should preserve the old site and a recovery path, so a completed copy is not mistaken for a completed migration or used to overwrite newer orders on the live site.
About 7 min read

Contents
- 1. Check the tools and resources you need before buying
- 2. Create a new website with the setup wizard
- 3. Prepare both source and destination before migration
- 4. Staging is for testing changes, not a permanently synchronized live site
- 5. Check data and functions when switching to production
- 6. Keep the old site until handover conditions are clear
Before using SiteGround, decide whether you are building a website from scratch or moving a WordPress site that people already use. A new site mainly needs content and management arrangements; a migration also involves existing data, update timing and switch-over risks. Both can begin with the platform's tools, but the same completion message cannot stand in for all acceptance checks.
This article follows SiteGround's public documentation for new websites, WordPress Migrator and Staging; it does not report hands-on account testing. If your site continually takes orders, accepts member registrations or collects forms, pay particular attention to data that keeps changing during migration. Assign responsibility for final synchronization and the switch before starting, so new data is not missed.
Check the tools and resources you need before buying
List the number of websites, file and database sizes, required plugins, mailboxes, backups and testing needs, then compare them with the current plans. Staging, on-demand backups and collaboration permissions may depend on the plan. Check current product documentation and your account rather than assuming that every feature on the platform overview is included in every plan.
When comparing costs, record the initial payment, renewals, extras and required labor separately. If you need official migration assistance, first confirm its scope, the information to provide and the fee. Ask whether email, external services and custom programs are included. A migration should let your existing work continue, not merely deliver a new homepage that looks similar.
Create a new website with the setup wizard
For the current initial setup, go to Websites in the Client Area and select Finish Site Setup, then confirm the domain and WordPress. To add another site, use New Website and select WordPress, then follow the screens to set the location, domain and administrator details. Buying a domain and using one you already own are different options. Decide which you need rather than buying another name simply to proceed to the next step.
After creation, enter the WordPress dashboard and complete the homepage, main content and contact information before working on navigation and appearance. For a tutoring website, for example, start with subjects, lesson arrangements and an enquiry form. Do not add student results or reviews for which you have no real information. Installation provides a starting point for content; you still need to verify the public information and image usage rights.
Prepare both source and destination before migration
For an existing site, first obtain restorable file and database backups and record the current URLs, plugins, scheduled tasks, email and important integrations. Confirm that the source can install a suitable migration plugin and that the destination host has enough resources. If the source is a restricted platform, a multisite network or a special structure, check tool compatibility and limitations first, and use official assistance if necessary.
In SiteGround's official process, open WordPress and then Migrator in the destination's Site Tools. Select the target domain and path to generate a Migration Token, then enter it in the SiteGround Migrator plugin on the source site. First confirm that the target location has no content you need to keep. Treat the token as sensitive information and use it only for the corresponding migration.
When migration finishes, inspect the copy using the official preview or test method, and keep the old site for the time being. A successful copy does not automatically prove that email, domain registration or all external services have moved too. Check how the site's outgoing mail, scheduled tasks and cache configuration work in the new environment. Matching the article count alone is not enough to finish acceptance checks.
- Back up the source site and list plugins, data, email and features that are still generating new content.
- Generate a token for the intended destination in Site Tools under WordPress → Migrator.
- Install the official Migrator plugin on the source WordPress site, confirm the destination, submit the migration and save the result.
- Preview the new site and sample its data and functions before arranging final synchronization, the DNS switch and how long to retain the old service.
Staging is for testing changes, not a permanently synchronized live site
Eligible accounts can create a test copy in Site Tools under WordPress and Staging. The official documentation explains that the tool copies website files and the database, so the test environment may also contain production data. Restrict access and review external integrations. Give it a name that clearly describes its purpose, such as testing a new layout, instead of creating several indistinguishable 'new websites'.
SiteGround's documentation states that Staging copies disable the default WordPress cron functionality to reduce duplicated automated actions. This does not mean that every third-party external call is prevented. Still check payments, newsletters, Webhooks and external schedulers, using test mode or test credentials where needed. Do not make a real charge in a copy merely because its URL contains staging.
Before moving tested changes back to the live site, understand which files or database tables deployment will update. If the live site received new orders during testing, overwriting it directly with the old database could lose them. Someone who understands the data structure should confirm the appropriate deployment scope and synchronization method. Obtain a fresh backup before operating; a one-click deployment is not free of data risks.
Check data and functions when switching to production
Agree on a cutoff point for data updates before the switch. If necessary, pause workflows that create new data, then complete final synchronization. Configure DNS according to your domain and DNS services, preserve the original values and a recovery method, and check that email records were not accidentally changed. Once the production domain reaches the new site, recheck HTTPS, the root domain, www and important deep links.
Use a signed-out browser and a phone to test the main visitor flows, including articles, images, search, forms and login. For a migrated site, also verify recently added data rather than sampling only old articles. If there is a store, use the platform's testing procedures to check checkout, notifications and dashboard data. Reaching the homepage does not establish that the whole business workflow has recovered.
Keep the old site until handover conditions are clear
After confirming that the new site is stable, arrange cancellation of the old service under the original provider's conditions. First check whether mailboxes, backups or other websites still depend on that plan, and save the necessary data. If you need to revert the new site, specify how to handle content added after the switch. Changing DNS back does not automatically make all the data consistent.
Finally, create a management sheet naming the people responsible for Site Tools, WordPress, the domain, DNS, backups and renewals. Record the migration and acceptance methods used this time. These records will help with the next update or migration without starting the investigation from scratch. Tools can shorten copying time; continued maintenance still requires clear responsibilities, preserved data and verifiable completion criteria.
Read the full description
A SiteGround migration proceeds through source backup, copying with the tool, preview testing and the production switch, retaining verification evidence at each stage.
| Task | Tool or method | Additional checks required |
|---|---|---|
| Create a new website | Website setup wizard | Content, domain and visitor flows |
| Migrate WordPress | Migrator and destination token | Data completeness, email and external integrations |
| Test changes | Staging copy | Access restrictions and test mode |
| Deploy tested changes | Applicable deployment process | Whether new production data is preserved |
| End the old service | Original provider's cancellation procedure | Mailboxes, backups and other dependencies |
Everyday website maintenance: backups, updates and fault reportingWhat website maintenance involves: a routine for backups, updates, and incident reportsWebsite maintenance includes more than plugin updates: check content, accounts, backups, outgoing email, and expiring services. Using a small WordPress content site, this guide covers routine observation, pre- and post-update checks, restoration, and incident reports, with a worksheet for owners, editors, and maintainers. Set a schedule by update frequency, identify urgent cases, and keep records the next collaborator can use.Read the full article
Checking DNS settings: from A and CNAME to email records
Found this guide helpful? Share it with someone who needs it
Lifestyle
Before Resetting WordPress: Separate Content, Theme Settings, and Full Restore
Starting over in WordPress does not always require wiping the site. This guide compares style resets, content revisions, database resets, and full restores; explains the scope of WP Reset and the limits of its snapshots; and walks through a test site, backup checks, and acceptance after a reset. It helps ordinary users in Taiwan identify the actual problem and choose a suitably narrow action with a recovery plan.
Lifestyle
WordPress Performance Plugins: Caching, Images, and Feature Conflicts
WordPress performance plugins need settings matched to the actual site; enabling every option at once is unsafe. Using a small Taiwan-based course and shop site, this guide compares WP Rocket and NitroPack, divides responsibility for caching and images, and shows how to diagnose conflicts caused by CSS and JavaScript optimization. A comparison table, staged workflow, and original diagram help administrators retain a measurement baseline and verify forms, menus, and shopping flows.
Lifestyle
Handling WordPress Comment Spam: Review Rules and Akismet
Stopping spam in WordPress comments takes sensible moderation rules and a way to correct mistakes, as well as a plugin. This guide covers discussion settings, Akismet activation and plan eligibility, reporting spam, and rescuing legitimate comments. Its daily review checklist helps small-site owners reduce the workload while leaving room for readers with real questions to join the discussion.
Lifestyle
Build a personal blog with WordPress: from categories to your first post
To start a personal blog, decide what questions you want to answer over time, then plan the homepage, post list and basic pages. Using WordPress as an example, this guide develops a writing workflow from content categories and reading layouts through the first post and later updates. It also covers checks for post cards, pagination and comments. It is for readers in Taiwan who want to turn their notes into public content: finish a small but complete site first, then add features as needed.
Sources
- SiteGround: create a new websiteChecked:
- SiteGround: automatic WordPress migrationChecked:
- SiteGround: create a Staging copyChecked:
- SiteGround: Site Tools featuresChecked:
Compiled from the references and verification dates listed above; fares, schedules, product features, and terms can change, so please confirm the latest details on the relevant official website before travelling, booking, or purchasing.