> For the complete documentation index, see [llms.txt](https://developer.collibra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.collibra.com/api/guides/import-api/synchronization/batch-synchronization.md).

# Batch synchronization

For synchronizing less than 50 000 resources, you can use `/import/synchronize/<synchronization_id>/<file_format>-job` to complete the entire synchronization process in one call.

{% hint style="info" %}
This call performs both the import and finalization steps in a single job. Resources that no longer exist in the external system are removed from Collibra.
{% endhint %}

To synchronize large amounts of data:

{% stepper %}
{% step %}
Divide the input into multiple files which do not exceed the 50 000 resources recommended limit.
{% endstep %}

{% step %}
Start the synchronization process for each batch by calling `/import/synchronize/<synchronization_id>/batch/<file_format>-job`.
{% endstep %}

{% step %}
[Finalize](/api/guides/import-api/synchronization/synchronization-finalization-request-format.md) the synchronization by calling `/import/synchronize/<synchronization_id>/finalize/job`.

{% hint style="success" %}
The optional `finalizationStrategy` parameter determines the behavior regarding resources that no longer exist in the external system. You can set the parameter to `REMOVE_RESOURCES` to delete externally missing resources, to `CHANGE_STATUS` to update their status in Collibra or to `IGNORE` to leave them as they are. The default behavior of the Import API is to delete externally missing resources.

When you select `CHANGE_STATUS`, you must also specify the status to use with the `missingAssetStatusId`.
{% endhint %}
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Provide the same [synchronization ID](/api/guides/import-api/synchronization/synchronization-id.md) throughout the batch synchronization process.
{% endhint %}
