Migrating to the New UI is mostly a planning exercise rather than a technical project. Your data and configurations carry over, and most clients can move at the pace that works for them.

Turning on the UI is a matter of toggling a switch on the Archer Instance Manager (AIM), but there are some things to consider before flipping the switch. Here's the path we recommend.

1. Assess Your Readiness

The first step is to check out the major differences between the classic UI and the New UI. While most objects in your applications will immediately work, we have retired some features that were not widely used by our clients. We also made changes to some of the existing layout objects that users should be aware of. Additionally, any custom objects will need to be refactored to work with the New UI.

→ Click to see what is changing between the classic and New UI
→ Click to read more about the change with custom objects

If you need extra help, your client success manager is prepared to guide you on a migration plan. For larger or more complex environments, you can engage Archer Professional Services to complete a New UI Readiness Assessment. The assessment covers your custom object inventory, configuration complexity, and rollout strategy, and produces a plan tailored to your environment.

Talk to your account representative about engaging professional services to help with your migration.

2. Refactor Custom Objects, If Applicable

Some clients have written custom code to enhance their Archer experience. Because the UI has changed so drastically, custom objects written in the classic UI will not function as intended and will need to be written. We have a guide linked below to help these clients move these customizations forward.

Configurations Are Not Custom Objects

Custom objects refers to code written by clients and put into a "Custom Object" in application builder. This step does not refer to configurations to your fields, layouts, reports, dashboards, workflow, etc. Clients without custom objects can skip this step.

→ Click to read more about the change with custom objects

3. Plan Your Rollout

With any huge change, you should alert your users about the change and what to expect. Plan a day between large assessment cycles to make the change, and provide methods for users to reach out and get support.

→ Click to read more about support for the New UI

4. Turn on the New UI

Any Archer Admin can turn on the UI in the Archer Instance Manager (AIM). We provide four different modes, giving you control over your rollout:

Classic: Users will only see the Classic UI.
Classic Default: Users will see the Classic UI initially, but can switch to the New UI.
New Default: Users will see the New UI initially, but can switch back to the Classic UI.
New: Users will only see the New UI.

Users switch between experiences by clicking on their user icon at the top right of their screen, then click "Classic User Experience" or "New User Experience".

→ Read our article "Accessing the New User Experience" on the Archer Community

5. Make the Most of the New UI

The New UI immediately improves the UI automatically the moment you flip the switch, but there are a handful of features that need to be set up by your admins to take full advantage of them. Some of the features are listed below, and clicking on the links will take you to the help center to help admins know how to set them up.

→ Click here to see a highlight of all features

Need Help?

We have a FAQ on our community for clients migrating to the New UI. Additionally, if you run into issues, then contact support.

→ New UI FAQ
→ Click to read information on support for the New UI
→ Visit our support portal

Back to the New UI Hub