Oracle Guided Learning Guide Transition and Migration FAQ
Customer-facing summary of common questions and planning considerations for a guide transition or migration.
Overview
This document answers common questions about transitioning Oracle Guided Learning (OGL) guide content from one environment or setup to another. It is intended to help project teams understand what to expect, what should be prepared in advance, and which items may require follow-up after the switchover.
Table 1-1 At a Glance
| Topic | Summary |
|---|---|
| Timing | The switchover is typically quick and is usually completed after business hours to reduce user impact. |
| Freeze Period | A short freeze period is generally required. During this time, guide development and changes should pause. |
| Prework | Most preparation activities can be completed ahead of time so the cutover itself remains low impact. |
| Roles and Settings | Guide-level role-based rules transition, but custom roles may need to be re-applied in settings. |
| Archived Content | Archived content is not migrated. |
| Inactive Content | Inactive content can migrate and will remain inactive after the move. |
| Simulations | Simulation availability depends on account setup and guide type. Published guides can provide shareable simulation links where supported. |
Frequesntly asked Questions
What pre-work is involved?
Planning : Set a migration timelines. Host application roles and themes will need to be recreated in the new OGL application. You are required to export the host application Custom role and any Custom themes created in the exiting OGL Account. Once exported the application roles should be manually recreated in the new OGL account and the theme import into the new OGL account. If your organization is utilizing an end user browser extension, an updated version, containing the new OGL URL, is required and will need to be deployed to the host application users. You are required to raise a support request for an updated extension.
What issues can be caused by unpublished revisions?
Unpublished revisions can create confusion, including duplicate-looking versions or unexpected behavior. Before transition planning begins, guides should ideally be in a clear state, such as draft or published. If older revisions need to remain available, teams may need to clone and publish the appropriate version before the move.
Is there a transition plan or timeline?
In most cases, the switchover itself is short. A freeze date and a switchover date are usually planned close together. The exact timeline depends on overall readiness, including whether there are unpublished revisions or other cleanup activities to complete first.
Can prework be completed before the switchover?
Yes. The majority of preparation work can usually be completed in advance. This helps keep the final switchover efficient and minimizes disruption to end users.
Should changes be avoided between the freeze date and the switchover?
Yes. During the freeze period, guide development and related changes should pause. A short no-change window helps reduce risk and ensures the final transition is based on a stable content set.
What happens to role-based rules and custom roles during the transition?
Guide-level role-based rules transition as part of the content. However, custom roles may need to be re-applied in the target settings after the move. Until that is completed, users may temporarily see a broader or narrower set of content than intended.
Will users notice changes before the theme is reapplied?
Most setup activities can be completed ahead of time. Switchover and theme reapplication are typically handled quickly to minimize visible impact.
Is archived content migrated?
No. Archived content is not migrated as part of the transition.
Is inactive content migrated?
Yes. Inactive content can be migrated and will remain inactive after the transition.
How are simulations managed during migration?
For supported accounts, simulations may be enabled at the application level and can also be controlled at the guide level. Simulation links are typically shareable only after the guide is published and available in the Help Panel or widget. Simulation support applies to newer process guides created using capture and playback.
Are analytics transitioned?
The migration process will not include the transfer of analytics data. Any historical analytics or reporting will need to be viewed in the existing OGL Account or exported from the relevant dashboard as an XLSX or CSV file. Historical OGL analytic will be available to view and export for up to 60 days post migration.
Does the AppID remain the same?
Yes AppIDs will remain the same.
Recommended preparation checklist
- Review guide status and reduce unnecessary unpublished revisions.
- Confirm the planned freeze date and switchover date.
- Pause guide changes during the agreed freeze window.
- Document any custom roles that will need to be re-applied after transition.
- Confirm whether archived content needs to remain available elsewhere, since it is not migrated.
- Validate which guides are inactive and whether they should remain inactive after migration.
- Review simulation requirements, including whether guides are published and shareable.
- Plan a short post-cutover validation to confirm theme, roles, and visibility settings are correct.
Post-transition validation
After the switchover, it is good practice to complete a short validation cycle. This typically includes confirming guide visibility, checking custom roles, validating theme presentation, and testing any published guides that use simulation, video, or widget-based access.
Note:
This document is a customer-ready summary intended for planning discussions. Detailed execution steps, environment-specific timelines, and tenant-specific configuration activities should be confirmed with the implementation or support team managing the transition.