Microsoft 365 Migration

Move a SharePoint Online Test Site Collection to Production

Chanuka GeekiyanageChanuka Geekiyanage Nov 20, 2026 868 views

Question details

Move branding, files, resources, and content from a SharePoint Online test site collection to a production site collection.

Move a SharePoint Online Test Site Collection to Production
Product
SharePoint Online
Device & OS
not provided
Scenario
An IT team tests changes in a restricted QA site collection before publishing them to a separate production site collection.
Observed behavior
The team needs a controlled way to transfer the tested content and configuration to production.
Before you start

Inventory the QA site's libraries, lists, pages, permissions, branding, and customizations, and confirm that you have the required access to both site collections. Identify settings and integrations that may need separate recreation or testing in production.

Solution 1Recommended

Migrate the site collection with a specialist SharePoint tool

Use a migration product when you need to move multiple types of SharePoint content and review what the tool can preserve.

1
Select a migration tool

Choose a SharePoint Online migration product and check its documentation for support for your source and destination, including pages, metadata, version history, and permissions.

2
Configure the migration

In the tool, connect to the QA and production site collections, then select the lists, libraries, pages, and other supported content to migrate.

3
Run a test migration

Use a separate test destination where possible. Run the tool's assessment or test migration, then review its reports for errors and unsupported items.

4
Recreate and validate settings

In the destination site's Settings and Site contents, review navigation, branding, permissions, and site features. Recreate workflows, custom solutions, and settings that the tool did not transfer.

5
Complete the production move

Schedule a change window, run the final migration or supported incremental pass, and check the production site's content and access with representative users.

Migrate the site collection with a specialist SharePoint tool
Check the migration scope: SharePoint Online does not provide a simple in-place backup-and-restore process for copying an entire site collection to another URL. Preservation of versions, permissions, and customizations depends on the tool and configuration.
Free Microsoft Office alternative

Work with Office files during your SharePoint migration

WPS Office is a free, lightweight alternative with a familiar interface for reviewing and editing Office documents as you move them between sites. It supports seamless migration of local document workflows, but it does not migrate SharePoint sites or replace SharePoint administration tools.

Review documents copied from QA before they are published to productionCompatible with Microsoft Word, Excel, and PowerPoint formatsFamiliar editing interface for users moving from Microsoft OfficeFree, lightweight tools for everyday document work
microsoft office alternative - wps office

Frequently Asked Questions

Can I restore the QA site collection directly to a production URL?

SharePoint Online does not offer a simple in-place backup-and-restore process to copy an entire site collection to another URL. Use a migration tool or scripts for supported content, and plan to recreate unsupported settings and customizations.

Will copying a document library also copy the site's branding and navigation?

No. SharePoint's Copy to command is for selected files and folders, not the complete site. Review branding and navigation separately in the production site's settings.

How can I check whether permissions migrated correctly?

Open the production site's Settings and review its site permissions, then check any libraries or items with unique permissions. Test access with representative users before the site goes live.

Can PowerShell help with a SharePoint Online migration?

Yes. SharePoint PowerShell or PnP PowerShell can help with assessment and scripted migration tasks, subject to the commands and permissions available. Check current tool documentation and test scripts against a separate destination before using production.