Import Data: Difference between revisions
(Created page with "ContactsLaw allows '''importing data''' from various sources. This can be useful in new subscriptions, where bulk data can be imported from a legacy application; likewise, in established subscriptions it can be used to integrate with other software. == Import Process == The import process is as follows: # The source of the data is identified. For some file formats which do not belong to a particular application (e.g. CSV files), the user needs to nominate a specifi...") |
(No difference)
|
Latest revision as of 10:20, 16 May 2025
ContactsLaw allows importing data from various sources. This can be useful in new subscriptions, where bulk data can be imported from a legacy application; likewise, in established subscriptions it can be used to integrate with other software.
Import Process
The import process is as follows:
- The source of the data is identified. For some file formats which do not belong to a particular application (e.g. CSV files), the user needs to nominate a specific format.
- ContactsLaw converts the data from its original representation into the corresponding resources (e.g. contacts, matters, etc).
- Since some data may already exist in the subscription, ContactsLaw checks for duplicates and identifies likely replacements.
- The user resolves any outstanding issues with the data. They may choose to exclude some resources or nominate specific replacements.
- ContactsLaw creates or updates resources in the subscription, concluding the process.
Supported Formats
ContactsLaw currently supports importing data from these sources:
- Offline Data File (
.cl2
,.json
) - Data previously exported from ContactsLaw (including from another subscription). - vCard File (
.vcf
) - Widely-supported format for contacts. - Employment Hero Transactions (
.csv
) - For importing payroll transactions exported from Employment Hero.