You can choose to put your migrated clients through your full onboarding process or perform just the key compliance checks.

You might choose full onboarding if, for example, you've experienced a regulation breach or the compliance rules have changed since your clients were first onboarded.

This is the most straightforward migration path because you'll be treating all customers, existing and new, the same. You only need one workflow.

Alternatively, with limited compliance, you can set up ongoing monitoring and only run the most important checks. This option assumes any compliance in your legacy system is enough.

There are two options to process clients with limited compliance:

If you're using the second option, tasks with autocompletion may need to be resolved manually for the migrated clients. To do this, you can listen to the Manual action required webhook to find out when Passfort's automated processes have ended, then use the API to manually complete the tasks.

Before you start your migration, consider which data providers you want to use.

In particular, you should decide which ones you'll use for ongoing monitoring. Data providers with ongoing monitoring continually scan for changes to check results and push any new updates to Passfort. Most commonly, ongoing monitoring is used for the PEPs and sanctions screening check (individuals) and the Sanctions and adverse media screening check (companies).

Other checks, like the Company data check and the Merchant fraud check, offer ongoing monitoring as well. To find out if you can use ongoing monitoring for a data provider in Passfort, see its configuration topic.

If you're changing data providers or you're adding a monitoring service, you'll need to rescreen your migrated clients in order to initiate ongoing monitoring.

If you already have a monitoring service with a data provider and you wish to continue that relationship through Passfort, contact us and we'll help you get set up.

It's not possible for one data provider to take its state from another provider, so to initiate ongoing monitoring on a profile, you'll need to run the check once per provider.

Call the following API endpoint to create a profile and add an application: https://developer.passfort.com/api2#tag/Profiles/paths/~1profiles/post

For step-by-step instructions for using the API endpoint, see Create profiles.

The script should also create profiles for any company associates you're onboarding, such as directors, shareholders, and so on. Profiles for company associates need additional API calls to create a link between them and the parent company profile. To learn how to do this, see Create a profile for an associate and link it to a company.

We recommend only migrating the profile data required to perform your compliance processes.

At a minimum, include the following information for individual profiles:

At a minimum, include the following information for company profiles:

You may need to provide additional data depending on:

To see which data providers are configured on your account, log into the Passfort portal and go to Policy Builder > Data providers. To see which risk factors are used in your risk models, go to Policy Builder > Risk management. If you have not yet chosen your data providers or if you're using the Risk module and you have not yet chosen your risk models, contact us and we'll help.

You can upload any additional audit records or other documentation to the profile. These are added as files.

Use this endpoint to add files to a profile:

https://developer.passfort.com/api2#tag/Document-Images/paths/~1profiles~1{profile_id}~1files/post

Any file uploads must be in one of Passfort’s supported file types, which are PDF, JPEG, PNG, or GIF, and encoded in Base64. For step-by-step instructions for using the API endpoint, see What are files, documents, and document_images in the API?.

Tags are used to attach a label to a profile. We suggest adding a migrated tag to help you track which profiles were moved over from your legacy system.

Use this endpoint to add tags to a profile: https://developer.passfort.com/api2#tag/Document-Images/paths/~1profiles~1{profile_id}~1files/post

For a full list of webhook events and instructions for setting them up, see Configuring webhooks.

A description of each webhook body can be found in the webhooks section of the API resources.

When you're building your webhook receiver, it's important to consider the response time. See Returning a 200 response for more details.

For step-by-step instructions on how to update your system data when Passfort's profile data changes, see Sync profile data with your system data in the API.

The test in your demo environment should confirm:

There's no charge for the checks run in the demo environment, so you can perform your test on a reasonable number of profiles. Most clients find 100 profiles is about the right size.

Ideally, the profiles should cover different kinds of clients and data types.

If your demo environment test passes, we recommend performing a smaller scale test, such as five - ten clients, in your production environment.

This allows you to confirm that any live data providers are in place and configured correctly.

If you're performing limited compliance, it also allows you to confirm that the temporary changes to the workflow are in place.

To prevent duplicate profiles, remove these test cases from your full migration when you run it later. You don't need to give us advance warning before running the small-scale test.