Ready to move your content from Fastr Frontend to Fastr Workspace? Our team has built a streamlined migration process designed to minimize risk and ensure everything looks great before any live content is affected.
Migration Process
Migration happens in three phases, each building confidence before moving to the next.
Step 1: Migrate non-live designs
We start by migrating a handful of designs that are not currently published or marked as live in Frontend. These could be older experiences, duplicates of your homepage content, or any content that isn't live yet.
This allows both teams to review the migration process together. We'll verify that migrated content looks visually correct and that all interactions and expected behavior are intact. If any issues come up, our team can make fixes and re-run the migration script without impacting your live content.
Step 2: Migrate live content with low impact
Next, we migrate experiences that are marked as live in Frontend and published on your website. Once migrated, the live code on your site will render the Workspace content instead of the older Frontend version.
We start with a lower-impact page — either a test page with live content or a page with very low traffic. This lets us confirm that migrated live content is working as expected before expanding further.
How a live experience switches over
For any specific live experience, here's what the cutover looks like:
- Migrate the design to Workspace and visually confirm everything looks correct.
- Publish the Workspace version. Without any change to the embed code on your site, your page will now render the content from the new platform.
- Frontend redirects to Workspace. If you open that experience in the old platform to make edits, you'll automatically be redirected to the new platform. You'll also see a Live in Workspace flag so it's clear which experiences have already been moved over:
Verification and rollback. As soon as an experience goes live, we do a manual verification on your live site to make sure everything looks good. If we spot any issue, the support team has a Rollback option that instantly undoes the change — the Frontend version goes live again — so there's a safety net at every step.
Step 3: Full account migration
After the first two steps are completed without issues, we proceed with a full account migration. We can migrate the entire account at once or in smaller batches — whatever your team prefers. We won't migrate any additional content without discussing the approach with your team first.
Getting Started
To kick off your migration, email support@getfastr.com. As a first step, we'll ask your team to identify a few pieces of content for Step 1 — these should be duplicate experiences or a duplicate page in your Frontend account that we can migrate and review together.
Frequently Asked Questions
Will I need to update the embed code on my website?
No. The embed codes stay the same from Frontend to Workspace. Once a live experience is migrated and published, your existing code automatically renders the Workspace version — there's no new code to copy or deploy.
What happens to the experience in Fastr Frontend after it's migrated?
The experience is flagged as Live in Workspace in Frontend, and any attempt to edit it there will redirect you to the new platform. From that point on, Workspace is the source of truth for that content.
What if something doesn't look right after we go live?
Every live migration is manually verified right after cutover. If an issue is found, the support team can use the Rollback option to revert immediately, restoring the Frontend version as live while we investigate.
Will migrating affect a planned site launch or replatform (e.g., Shopify)?
It shouldn't. Because the embed codes don't change, content can be migrated before or after a launch without disrupting it. We'll coordinate timing with your team either way.
Do we have to migrate the whole account at once?
No. After the initial review steps, you can migrate the full account in one pass or in smaller batches by page or folder — whichever your team prefers. We never migrate additional content without aligning with you first.
What domains should we allowlist for Workspace?
If your environment restricts outbound domains, allowlist static.getfastr.com and images.getfastr.com so Workspace content loads correctly.
How long does migration take?
Timelines vary by account size and complexity, so it's hard to commit to an exact date before we've migrated an initial set of content. We've migrated a number of accounts at this point, and we'll give your team a clearer estimate once the first experiences are moved and reviewed.
Comments
0 comments
Please sign in to leave a comment.