Before getting started with iManage Security Policy Manager (SPM) in the Cloud, SPM must be provisioned and any required migrations must be completed. In addition, we recommend that you consider your organization's data imports into SPM.

This section gives an overview of these requirements, recommendations, and associated responsibilities.

Detailed information about all of these is presented in subsequent sections of the guide.

Migration types

The responsibility for migration depends on the migration type:

• Migrating from SPM on-premises to SPM in the Cloud

• Migrating from a third-party ethical walls product to SPM

If you're using SPM for the first time and aren't migrating from another product, no such migration is required.

Migrating from SPM on-premises to SPM in the Cloud

If you were already using SPM on-premises and are switching to SPM in the Cloud, this type of migration is performed for you by iManage or iManage partners.

Migrating from a third-party ethical walls product to SPM

If you were previously using a third-party system, such as Intapp Walls or Compliguard Protect to apply ethical walls, you can migrate existing walls from that system into SPM. The responsibility for this type of migration is with your organization. For more information, refer to iManage Security Policy Manager Generic Migration.

SPM provisioning

The provisioning of iManage Security Policy Manager in the Cloud is performed for you by iManage. When SPM is provisioned, you'll receive an "iManage Security Policy Manager provisioned" email from us.

This includes initial credentials to sign in to SPM—with which you can perform import authorization and assign roles—and other information.

Data import considerations

• Clients, matters, users, groups, and associated metadata

• User activity

• Data import planning

Clients, matters, users, groups, and associated metadata

To ensure that clients, matters, users, and groups in SPM are updated in line with any changes to the same in your source systems, scheduled imports of these data types must be established between the source systems and SPM.

You can add client, matter, and user information in SPM without affecting these items in your source system.

Before setting up these scheduled imports, consideration must be given to the sources that'll be used.

• For client and matter import, the source will be the location where clients and matters are mastered in your organization—for example, iManage Work or Elite Enterprise.

• For user and group import, the source will be iManage Work.

The type of imports required also depend on the type of data you need to import. For example, your organization may require matter metadata defining the departments used for Collections (departmental) security, client/matter metadata defining responsible attorneys, and so on.

• If your organization requires basic client, matter, user, and group information to be imported from iManage Work in the Cloud, we'll configure these scheduled imports for you. These imports run every 15 minutes.

• If your organization requires additional metadata from any source, or basic information from data sources other than iManage Work in the Cloud, these scheduled imports must be deployed and configured by your organization.

User activity

Attorney time recording (billing) and document activity information can also be imported into SPM. This type of information can be used—for example, to enable the creation of rules that automatically add users to matters when those users meet the defined criteria for hours posted or activity performed on documents relating to such matters. Document activity data is always sourced from iManage Work.

• If your organization requires time recording (billing) data to be imported into SPM, you must deploy and configure scheduled import from an on-premises time entry system such as Aderant Expert.

• If your organization has requested import of document activity data from iManage Work in the Cloud, we'll configure these scheduled imports for you.

• If your organization requires this type of data to be imported from an on-premises iManage Work system, this scheduled import must be deployed and configured by your organization.

Data import planning

It's important that the correct data sources and import types are selected. Attempting to switch data sources after an import is established isn't recommended and may require the intervention of iManage Support, and necessitate system downtime.

This guide contains information to help you plan and implement appropriate import solutions for your organization.