Import data
When the JSON files are prepared, you can import them to the Tuum environment.
Rules for data migration
The main rules for data import are the following:
The person can be imported only once. The import will be rejected if the imported person already exists in the Tuum environment.
The account can be imported only if the account person already exists in Tuum.
The transaction can be imported only if the transaction-related account exists in Tuum.
Therefore, the data migration must be completed in the following order:
Migrate persons,
Migrate accounts,
Migrate transactions,
Migrate loan contracts.
Migrate data
To migrate data, use the import data API call.
api/v2/import
The following parameters are required when calling the import data API endpoint.
sourceName
string
query
The name of the application from which you are importing data. For example my_old_customer_data_application
sourceRef
string
query
The unique sequence number of the imported data batch. For example 00123
x-leaf-tenant-code
string
header
The name of the target leaf tenant in Tuum where the data will be imported.
For example my_target_leaf_tenant
The request content should presented in the multipart/form-data form.
Sample request
Processing of migrated data
Tuum system returns a 202 response when it has successfully received the data import file.
During subsequent asynchronous processing, Tuum performs multiple checks and validations.
To ensure the data import process reaches one of the following final statuses: DONE, PARTIALLY_DONE, ERROR, or DISCARDED, do the following:
Monitor the data import process by making API calls to the data import status endpoint.
If necessary, perform failover actions to complete the data import process and bring it to its final status.
Last updated
Was this helpful?