Our professional services team has performed hundreds of successful SaaS migrations. Our predictable, repeatable process ensures migrations are delivered successfully and on time.

When we migrate a client, we take a copy of your database and bring it directly into our environment. This means that your record data, history logs, and attachments will all show up day one on SaaS. We also bring your configuration database, so your SaaS instances function exactly as they did before.

Migrating to SaaS won't restart your Archer implementation. Dashboards, reports, and form layouts all stay the same. What changes is the URL your users log into.

One major change that is recommended would be to turn on the New UI, which will change the look and feel of Archer. Turning on the New UI will not change any workflows, layouts, or the underlying data, but it will change how your users see those elements visually. You can migrate to this on your own time, and we have another hub to talk about the New UI and how to best transition users.

→ Click here to go to the New UI Hub

Most of the work during migration is repointing URLs, integrations, and paths to their new locations, since Archer would no longer be hosted internally.

The End-to-End Migration Progress

Below is a table showing the general timeline of SaaS Migrations

Instance Assessment

Before doing any work, we will have you fill out an assessment specific to your environment. This goal of this assessment is to review several aspects of your current on-prem instance to determine what needs to happen to migrate to SaaS. This includes filling out an Excel-based questionnaire, and providing the Installation and Instance Reports from your Archer Control Panel (ACP).

• We have done 400+ implementations
• Question we have learned to ask up front rather than at the end
• This will give us the best understanding of the overall effort, complexity, time, etc.

→ Click here to download the SaaS Migration Questionnaire
→ Click here to get instructions on how to generate the Installation and Instance Reports from ACP

Based on the outcome of assessment, we may need to resolve some tasks before migrating. Common pre-migration tasks include:

• Resolving exceeded user counts
• Addressing large storage overages
• Optimizing field history configuration
• Optimizing data feed scheduling

We also identify tasks to complete after migration, such as:

• Updating data feeds
• Repointing integrations to the correct URLs
• Configuring Single Sign-On
• Updating any URLs in dashboards or records that point to the on-prem instance

Scheduling Your Migration

Archer migrates one client each day, and we have them all scheduled in advance. We will work with you to slot you in around your timeline. Migrations run on weekdays, and you should plan for one business day of downtime. Once we go live, all users should log into the new SaaS Instance. Your existing on-prem instance can be shut down later at a time of your choosing.

Migration day

We fully support you on migration day and walk through everything on a call beforehand.

Before your migration day, you will want to inform your users about the migration. It may be wise to use the security parameter settings in your On-Prem Archer instance to block users from logging in on the scheduled date and after. As stated before, users should expect one day of down time.

On migration day, below is are some things you should expect.

Who to bring

• Archer Admins
• Business users (optional, for testing)
• Identity & Access Management experts (for SSO and SCIM setup)
• SQL Admins (for database queries and scripts)
• Server Admins (to provide the files needed for migration)

What we'll need:

• Instance database: the SQL database file from your administration team
• File repository: a zip file of all attachments from your file repository
• Company files: all company and appearance files stored in Archer

What will happen?

Our team will will handle the actual migration, including validating your database, applying upgrades, migrating company files, attachments, and everything else to the cloud.

Your team will need to be available to help do the following:

• Configure user access mechanisms, like SSO and SCIM.
• Complete the post migration tasks determined within the Instance Assessment
• Validate that the SaaS instance looks good
• Reenable user access
• Disable access to your on-prem Archer

We have done this hundreds of times, and have a team that will be with you the whole time.

Case studies

See how organizations like yours made the move.

• Intuitive Surgical

Back to the SaaS Migration Hub