From November 1, TinQwise will begin automatically moving content from the content builder to Studio. This will take a few weeks to complete. This does not change anything for you.
This article answers common questions about how the move works and what to expect.
Migration basics
What will be moved to Studio?
What will be moved to Studio?
Only content that has previously been pushed to Control will be migrated.
If an activity was never pushed to Control, it will not appear in Studio.
👉 Important: Unpublished drafts or test activities that never reached Control won’t move.
Do I have to do something about this?
Do I have to do something about this?
Yes and no...
Yes: If you know there is a lot of your content that has never been pushed to Control and you don't want to lose it, then you need to go to the Content Builder and migrate all activities to Studio.
No: If you don't need any content or activities that are not on Control already, then you can sit back and continue working on other things.
Will I be notified if something can’t be moved/migrated to Studio?
Will I be notified if something can’t be moved/migrated to Studio?
No notifications will be sent, however, there will be an error message for that specific activity, mentioning that the activity was unable to be migrated.
What are the chances of migration issues?
What are the chances of migration issues?
Migration failures only occur when there’s a problem with the activity itself.
If your content worked well in Control and was fully published, it's unlikely you’ll run into issues.
There’s no clear way to predict how often problems will occur, it depends on how your content was originally built.
What’s the risk of completely moving to Studio?
What’s the risk of completely moving to Studio?
While migration issues may happen, they’re fixable. After the move to Studio, you will no longer have to go on the Content Builder.
Ultimately, moving to Studio is a major upgrade:
A smoother content editing experience
More flexibility in design and structure
Better long-term support for updates
Troubleshooting and fixing issues
Why was my activity not migrated?
Why was my activity not migrated?
If an activity cannot be migrated, it’s usually because it is broken in some way. For example:
A required image is missing
A required text field is empty
The activity structure is incomplete
These errors prevent the migration tool from completing the move. First you have to find the error by going to the slides, and checking which field is missing.
Who is responsible for fixing broken content?
Who is responsible for fixing broken content?
If you created the activity, you are responsible for fixing the issue.
If TinQwise’s Professional Services team built the content for you, you don’t need to fix it yourself. Just send an email to service@tinqwise.com and we’ll take care of it.
How will I know if an activity has already been moved?
How will I know if an activity has already been moved?
There are two methods:
If you have migrate the content yourself, then you will get a completion message that the activity was successfully migrated to Studio.
Go to Control > Content > Activities.
If you search for the activity, it should show up.
It may take a few minutes for an activity to be moved.
Automations, behaviour, and translations
What happens to translations during migration?
What happens to translations during migration?
Translations will move with the activity, but missing fields in translated versions can block the migration.
Can I still edit content in the content builder?
Can I still edit content in the content builder?
No. Once migrated to Studio, editing must be done in Studio.
Will my automations linked to the content be affected?
Will my automations linked to the content be affected?
No, existing automations linked to content from the Content Builder will not be affected. Everything will continue to work as it was before.