Create or import a site

Use Create Site for a new WordPress installation and Import Site when you already have WordPress content or a supported backup package to bring under Webcore management.

Create Site

A new site is provisioned with a dedicated system identity, document root, MariaDB database, PHP configuration and web-server configuration.

Where automatic placement is available, Webcore can select a suitable active hosting node from current capacity information when an administrator has not chosen a destination explicitly.

Public DNS does not need to be moved merely to provision the site. SSL issuance does require the public hostname to be suitable for ACME validation on the destination. Until cutover, Preview provides a Webcore hostname for inspecting the managed site over HTTPS.

Import Site

The managed import path inspects and normalises the source before applying it to the destination. Supported workflows include Webcore backup packages and supported Plesk/WP Toolkit WordPress backup formats.

Depending on the source format, the importer identifies the WordPress document root, database material and application metadata, restores the destination under the site's managed identity, and repairs destination-specific WordPress configuration where required.

Do not manually flatten or rearrange an unfamiliar backup archive before trying the managed importer; package inspection is designed to identify supported layouts.

Large imports

Large WordPress installations can require substantially more time for extraction, database import, URL rewriting, ownership repair and validation than a small site. Allow the managed import operation to finish rather than repeating the request because it is taking longer than an ordinary page action.

After import

1. Verify the site through Preview if production DNS has not moved.
2. Open WP Admin and check the active theme, plugins, users and application-specific configuration.
3. Confirm the selected PHP runtime is compatible with the imported application.
4. Check generated links and media for source-domain references.
5. Validate SSL after public DNS is ready.
6. Create a Staging copy before substantial post-migration changes.
7. Enable or verify the intended backup schedule.
8. Run diagnostics or a malware scan when the source environment was untrusted or its condition is uncertain.

For a recovery package that should be tested without changing production, prefer Restore backups to Staging.