Difference between revisions of "Branch Migration into new system"
| (6 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
If you want to take one branch out of an existing system, and create a new system, our data migration team can help. | If you want to take one branch out of an existing system, and create a new system, our data migration team can help. | ||
| − | For full details and costings, please contact the | + | For full details and costings, please contact the data team at: dm@dizions.co.uk |
| + | |||
| + | ===Uploaded documents=== | ||
| + | Documents are included as part of the migration. Because each document has individual access rights (a list of users and/or groups), our migration team will need to know what to do with documents which belong to the clients who are being migrated, but which are not currently visible to any of the users who are being migrated. For example, suppose the source system had a user group called Benefits Team, and some of the clients who will be migrated to the destination system have had some benefits advice, and none of the users in the destination system are in the benefits team. We can either: | ||
| + | |||
| + | 1) Not migrate these documents (default), or | ||
| + | |||
| + | 2) Grant visibility of these documents to a nominated user group, or, | ||
| + | |||
| + | 3) The documents are excluded from the main migration process, and you provide us with the documents and associated id numbers | ||
Latest revision as of 11:40, 2 August 2024
If you want to take one branch out of an existing system, and create a new system, our data migration team can help. For full details and costings, please contact the data team at: dm@dizions.co.uk
Uploaded documents
Documents are included as part of the migration. Because each document has individual access rights (a list of users and/or groups), our migration team will need to know what to do with documents which belong to the clients who are being migrated, but which are not currently visible to any of the users who are being migrated. For example, suppose the source system had a user group called Benefits Team, and some of the clients who will be migrated to the destination system have had some benefits advice, and none of the users in the destination system are in the benefits team. We can either:
1) Not migrate these documents (default), or
2) Grant visibility of these documents to a nominated user group, or,
3) The documents are excluded from the main migration process, and you provide us with the documents and associated id numbers
