Import and Export Manager considerations and configurations

When configuring the Import Manager or Export Manager for use in a SaaS environment, there are special considerations and configurations.

Best practice is to use the Ingestion API rather than Import Manager. The Ingestion API fully supports multi-tenancy.

Import Manager and Export Manager SaaS considerations

The SaaS provider must configure and administer the Export Manager and export data on behalf of each tenant.
The SaaS provider must create the enterprise entities that are used by Import Manager for each tenant individually:
- Data source (adhering to naming conventions)
- Users with Agent ID or Extension, depending on seating type
The SaaS provider must create the following items for each tenant as separate Import-Export Manager entities, adhering to naming conventions:
- Adapter
- Selection plan
- Job

Import Manager and Export Manager SaaS Configurations

For Import Manager, configure data source, users, and adapter metadata mapping for Resolve to Existing Employees mode.

The Service Provider is responsible for ensuring that Employees resolve to the correct tenants. If different tenants have the same Employee IDs, it is possible that the Import Manager will match the recording against the wrong tenant. This should be avoided by checking for this condition and ensuring the Employee named metadata is uniquely associated to a name in that tenant.
For adapters that extract metadata from the database, modify attribute fields in the database before historical calls are extracted.
Extract tenant data to a staging location where you can verify the results.