Who is this article for?

Administrators who would like to prepare to move from the Classic UI to the Miramar UI

Please contact us to create a Miramar Migration plan

The transition to Miramar modernizes the look and feel of the user interface, dashboard, search functionality, and reporting.  Various modules will have minor applications configuration changes to accommodate for improved field and layout improvements.

The workflow-enabled modules will be adapted to the Standard Workflow Layout, whereas the layout of non-workflow-enabled modules might continue to maintain a resemblance to the Classic version. 

Each customer should consider the timing of their migration to Miramar and subsequently engage with their Technical Account Manager (TAM) to initiate discussions. 

The migration will be executed by Ideagen resources from the Professional Services team. It will be essential to schedule the migration in accordance with the availability of Ideagen resources.

The commencement and duration of the migration will depend on several factors that can be discussed with a TAM. 

Related articles and videos

The following are some helpful Miramar migration articles and information for customers to review prior to a migration:

• Getting started with the Miramar UI
• Understanding a Classic to Miramar UI migration
• Navigating the Standard Workflow Layout (SWL)
• Frequently asked questions about Miramar UI
• Skills training catalogue and courses 

Resource Requirements

Customers are encouraged to consider how they will address the following elements:

• Resource Allocation – Each customer converting to Miramar should plan on allocating the following resources, part-time or full-time, to the project:
  • Project Manager
  • Application Subject Matter Expert (SME), for each application
  • Testers
  • Trainer (unless performed by one of the roles above)
  • IT representatives (see below)
• A Temporary Pause in Other Changes - To streamline the migration to Miramar, reduce risk, and keep costs to a minimum, no other changes to the modules will be allowed during the migration. Working with a Technical Account Manager, each customer will need to review all currently open tickets and pending changes. These pending changes will need to be completed before the migration or delayed until after the migration.
• Address Potential Gaps in Functionality - While Miramar offers many new features never available in Classic, there are some Classic features not yet available in Miramar. Each customer should discuss any potential gaps with their Technical Account Manager.
  Note: Most customers do not use the features that are not available in Miramar yet.
• Internal Change Management – Upgrading the user interface of a widely used business application will require proper change management. The demonstration will provide insight as to how the Miramar UI will be different for users. As the migration project progresses, internal changes will be identified and discussed to ensure a smooth end-user transition.
• Training – During the migration project the project team can identify what level of training will be required. For example, will in-person training be provided to all users? Will training material need to be created, or updated?
• Testing – What will be the acceptance criteria that must be met prior to activating Miramar in production? Acceptance criteria will be defined during the migration project, but customers can begin considering what success looks like.
• Coordination with IT – Ideagen DevonWay will provide the updated URL during the project, but customers can alert their IT organizations that these changes are forthcoming. this will require modifications to:
  • System shortcuts on intranet websites.
  • Shortcuts on user desktops and browsers.
  • Other locations where shortcuts may exist.