In the past, you may have created activities in the Content Builder. As we transition from Content Builder to Studio, your content needs to come along too. This article walks you through how to move your content from Content Builder to Studio.
🧪 Moving activities from the Content Builder to Studio
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 Migrate to Studio to move the activity for editing and versioning
What will happen:
The activity or folder is ready to edited in 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?
Media and documents: All associated media and documents are automatically included in the migration.
You’ll find them under Control > Content > Assets.
Automations and reporting data:
Most activity-level automations should carry over, but it’s recommended to double-check any custom automations after migration. Some platform-specific automations might need re-linking.
Learner access and progress:
Learners will retain access to the activity, and their progress should remain intact. No extra actions are required on your side.
We always suggest performing a small test migration first to confirm everything works as expected.
Limitations and known issues
Limitations 🌧
Smart exam activities cannot be migrated to Studio. You will be able to keep creating them on the Content Builder.
Very important 🌤
Studio does not support inline images in text fields (but they will still exist).
When you transfer activities that do have inline images, these images will not be able to be edited, only removed.
You can then re-add images using an image placeholder