@@ -9,7 +9,6 @@ Aims to fill the gap for the following type of needs:
* Tracks which row of data modified which CiviCRM entity (ex: helps to review that the import worked as expected).
* Supports large files (as long as your server allows uploading them, it has been tested with Excel files with an average of 50,000 rows).
* Can regularly run imports using a Scheduled Job, assuming a custom 'helper' that fetches data from a remote location (ex: from a third-party service) or a specific location on disk.
* The contact import and contribution import from "core" can be processed with advimport, to avoid any timeouts during the import. It also makes it possible to review errors and track the imported contact IDs.
* The contact import from core can have a column called "tags" (the name must be exact), with a list of either tag names or IDs (separated by ";"), in order to add multiple tags at once.
* The API3 Contribution/Participant import can match contacts based on their `external_identifier`.