After having created activities in the Content Builder you can either push them to TinQwise Control or migrate them to Studio for advanced editing and versioning. This article walks you through both paths and helps you decide which option fits your workflow best.
Pushing vs migrating: what's the difference?
Push to Control
Keeps the activity editable in Content Builder. Learners can access it if configured, but any updates must be pushed again.
Migrate to Studio
Moves the activity to Studio for editing and version control. Once migrated, the activity is no longer editable in Content Builder.
Important 🔥
We recommend you to migrate as much content as possible from the Content Builder to Studio! Editing, interface, and your general experience will be much better using Studio! 🌞
Inline images & videos are not supported in studio right now.
🔁 Push to TinQwise Control
Use this option when you want learners to see the content but still plan to edit it in Content Builder.
Go to Content Builder
Select a single activity or a folder
Click Push to TinQwise learning platform
Choose the correct platform from the list
If you push a folder, you’ll see a list of all included activities. After pushing, your content appears in Control > Content > Activities.
🔥 Important
Every time you edit the activity in Content Builder, you’ll need to push it again to update the version in Control.
🧪 Migrate to Studio
Use this option when you want to edit and manage your activities in Studio with version history and structured editing.
Steps:
Go to Content Builder
Select the activity or folder you want to migrate
Click Push to TinQwise LXP
Choose Push to Studio when prompted
Select Push to Control if you only want to publish for learners
Select Migrate to Studio to move the activity for editing and versioning
If you choose Migrate to Studio:
The activity or folder is prepared for Studio
Studio creates a new version (not a duplicate)
All structure and assets are preserved
If you choose Migrate to Studio:
The activity or folder is prepared for Studio
Studio creates a new version (not a duplicate)
All structure and assets are preserved
What gets transferred
All associated media and documents are automatically included.
You’ll find them under Control > Content > Assets.
Limitations and known issues
Limitations 🌧
Smart exam activities cannot be migrated to Studio
Very important 🌤
Studio does not support inline images in text fields
🔍 Why:
Inserting images directly into text disrupts layout and impacts learner experience. Always use designated image fields instead.