Importing records

Most Kahua applications allow for the import of entity records. Imports can be used to create new records or update existing ones. Creating or updating records through an import is most appropriate in document management, properties, and contact applications. Importing records into Kahua can differ slightly by application.

Imports are done into an application for a project. The import is completed at an application level (not cross-application) and is done for one project at a time.

Note If you are looking to migrate data for multiple projects or applications, please reach out to your account manager for assistance.

Items to consider prior to importing records:

  • Users will need Moderator or Admin access to an application to be able to import records into that application.

  • Typically, it is not recommended to import new cost records, such as a contract, budget, or pay request. This is due to those records having an ‘items’ grid, which is a separate entity within the record itself. These records should be created manually. If you want to migrate cost records from another system, please contact your account manager for assistance.

  • Import is most appropriate for apps such as those found in the document management suite, as well as the Contacts app and, if using, the Properties app.

  • If workflow is enabled on a project, you should only utilize an import to create new records, not update them. Do not export and re-import to modify existing records that are locked and currently part of a workflow. You can use the import process to update records that are not currently in workflow or if workflow is not enabled for that project.

  • To generate the file you will need to populate for an import, you must perform an export from the project and application where you want to perform the import .

  • Consider creating at least one record in the application prior to performing the export. This sample record provides an example of how the data should be entered.

How to . . .