Editing Migrating Aiga records (section)

==Principles==
{{See also|Cutover dates}}
As at January 2025, the trend in Kotahi service configuration is to define a small number of custom activities (eg. requisition, assessment/goal plan) and leave a generic <code>narrative case note</code> to catch almost everything else.

This <code>narrative case note</code> is broadly equivalent to a 'Contact' in Aiga; the biggest functional difference being there are three data points for a contact in Kotahi (type, method, location) and only one in Aiga.

In terms of migration principles, we are electing to Keep It Simple and use only the <code>narrative case note</code> as a target for migrated Aiga data. This will inherently require a loose mapping from Aiga contact types, to the three elements used in Kotahi.

In terms of scope, we are migrating only Aiga contacts for ''migrated clients''. We have only been pulling across clients which are current at the time of cutting over the service/contract to Kotahi.<ref>Please refer to [[Cutover dates]].</ref> There is therefore a known corpus of clients and contact data which will never be migrated to Kotahi, but which will however remain available within either a moribund Aiga app or a SQL backup in the event the app is decommissioned.

We will also migrate attachments, or documents, for in-scope clients and this will be clarified further below.