Quick answers to the questions we hear most often from clients moving to the New UI.
Do I Have to Migrate My Data at All?
No. Your applications, fields, data-driven events, workflows, and access controls all carry over as-is. There's no data migration and no reconfiguration — the New UI runs on the same data and business logic you have today. More on what the New UI is →
Does the New UI Cost Extra?
No. The New UI is available at no additional cost for clients on Archer SaaS.
Can I Try It Before Rolling It out to Everyone?
Yes. The New UI can be turned on by instance, so you can enable it in Dev and Test before going live in Production. There are options to allow users to opt in on their own schedule. More on turning it on →
Will My Users Have to Be Retrained?
The New UI presents the same data and workflows in a cleaner interface, so the core of what your users do is unchanged. A few day-to-day behaviors are different like single-field editing, navigation, dropdowns are worth a short heads-up to your team. See what's changing →
What Features Are Going Away?
A few Classic features aren't carried forward, most notably the Print button, card and summary display formats, the voting field type, and bulk record creation. Most have a direct replacement. See the full list →
How Often Does the New UI Get Updated?
The New UI ships new releases every two weeks. Release notes are in the Archer Help Center →
Do I Need a Readiness Assessment to Migrate?
Not necessarily. Smaller or less complex environments can simply turn the New UI on when ready. For larger or heavily configured environments, a Readiness Assessment helps you understand custom object inventory and rollout strategy first. More on the migration path →
Are There Features That Need Setup Before I Can Use Them?
Yes. Most of the New UI works automatically, but the Workflow Tracker, Smart Copy, four-column layouts, and hiding section headers need admin configuration. Since these features did not exist before, it's not critical to set up before migration. Read more about making the most out of the New UI →
I Use Custom Objects. Do They Carry Over?
Not automatically. Custom objects keep working in Classic, but they use a new, more secure architecture in the New UI and must be recreated there. If your environment relies on custom objects, inventory them early, as it's the most common thing teams need to plan for. More on migration planning →
How Do I Report a Bug or Request a Feature?
It depends on what you need: feature ideas go to Product Pulse. Defects and performance issues go to the Case Portal. If you have questions you want answered by other clients, use the Community Discussions on the Archer Community. See support channels →
When is the end of support for classic UI?
We do not have a date for removing our Classic UI at the moment. We know that the New UI is the future of Archer, and plan to spend our resources improving and enhancing that experience, but clients will still be able to see their data using the Classic UI even past our change in support date October 2026. See our blog post on Classic UI end of enhancements →
When I make a change in application builder, I am not seeing it on the record page?
In order to increase the performance for our users, we have implemented a robust caching solution that decreases page load times significantly. While our cache will refresh on a timely basis, it sometimes means that admins who are making active changes to a layout won't see those changes immediately until the cache has refreshed. We have recently added a way to manually refresh the cache for an application available within the applications list in application builder. See our blog post on how to refresh the cache →
Comments
0 comments
Please sign in to leave a comment.