Migrated Sites

If Contentrain Migrate moved your WordPress site and delivered it as a Git repository, Studio is where you keep managing it: content, comments, forms, and media in one place. This page walks through the steps the Studio interface shows you.

Open Your Site in Studio

Your delivery includes a link to Studio. It opens a page that shows what came with your migration and a button to continue.

1. Open the link and sign in to Studio (or create an account)
2. Choose the workspace the site should live in, if the page asks. You need to be an owner or admin of that workspace
3. Click Connect {repo} to turn the delivered repository into a project, or Open the site in Studio when it is already connected

If something is missing, the page tells you what and gives you the next step:

Message	What to do
Studio's GitHub App is not installed	Click Install Studio's GitHub App, then connect again
Studio cannot access the repository	Click Open the app's settings on GitHub, allow the repository, then click Check again
The repository is on another GitHub account	Transfer it to the account where the app is installed (the page links to GitHub's guide), then check again
The plan has ended or is not set	Open billing settings and choose a plan

If the link has expired or was used with another account, open Studio from your migration's delivery page for a fresh link, or contact support.

Setup Wizard

Once the project exists, its overview shows Migrated from WordPress with a summary line. For owners and admins the setup wizard opens by itself while steps are open. You can close it with Close and continue later (it stays closed in that browser), reopen it from Continue setup or Setup details, and skip any step. Skipping a step only stops Studio asking.

The first screen, Your site is in Studio, shows the repository, the plan that came with your migration, and what content was moved. Four steps follow.

1. Forms and comments

Turn on your forms and comments runs your new site's forms and comments with Studio: messages reach your inbox and comments wait for your approval in Studio. This adds one small settings file, studio.json, to your repository, and your host rebuilds the site on that change.

• On a project that reviews changes, turning this on is your approval for this one file. Your content changes still wait for review as usual
• If your default branch is protected, the change is a pull request on GitHub. Merge it there
• If your repository already has a studio.json pointing somewhere else, Studio leaves it as it is. Check it with your team or contact support
• Forms beyond what your plan takes stay off

2. Comments

Bring over your comments imports the comments from your WordPress site, with each name, website, and text. Email addresses and IP addresses were not moved. The comments appear under the same posts on your new site, and you moderate them in each model's Comments tab. See Comments.

If the export has expired, upload the export file yourself in a model's comment settings.

3. Images

Move your images to Studio Media copies the images that are in your repository into Media, points your pages at them, and merges that change. Clicking Move is your approval; nothing else in your content changes. You can close the window while the move runs.

• Moving images needs a plan with media storage and image delivery, and image delivery must be on for the project. The wizard tells you which is missing
• On a project that reviews changes, approve the move in the wizard
• If your default branch is protected, the move is a pull request on GitHub. Merge it there
• Files larger than your plan takes stay where they are and keep loading from WordPress, so keep WordPress running for those. Host them elsewhere and update their links, or move to a plan that takes larger files
• You can keep images in the repository instead

4. Live site

Check it on your live site confirms that changes made in Studio reach your live site.

1. Enter your live site's address
2. Click Make the test change. Studio adds a tiny check file, public/.well-known/contentrain-check.txt, to your repository
3. Once your host has rebuilt, click I see it, finish. If it does not show, check that your host builds from the repository's default branch and that the address is right. If you can open the check file yourself, you can mark the step done manually

You can delete the check file at any time. If you are not on a host yet, choose Not on a host yet.

If you want scheduled posts to go live without a manual build, add a deploy hook too. See Deploy Hooks.