4.1- Project Planning

Follow

Proventeq Migration Accelerator is a sophisticated migration product, so it is important to plan
the migration to ensure that the migration runs smoothly.

Questions to ask when planning for migration include:

  • What systems to migrate, their physical location and how much of the data is to be
    migrated.
  • What requirements/expectations are there regarding project milestones, migration
    completion.
  • How to split the migration to make it manageable.
  • Differences between the Source and Target in terms of metadata, users, security, and
    folder structure.
  • Should the existing folder structure remain or be changed.
  • Do existing access permissions need to be carried over to the target.
  • How will end-users be affected, communication plans for end user.
  • Source system readiness – Ensuring any documents are ‘check-in’ prior to discovery,
    that source system is in a good state of health.
  • Target system readiness.
  • What to do with the Source once migration has been completed.

When starting a migration project, the end-users are a vital part of a successful project.
Communication is important and end-users need to know.

  • Why the content is being migrated
  • What the benefits will be to them
  • When the migration is going to happen
  • What the expectations are upon them

Any upfront communication also allows users to do any clean up prior to the migration and as a
result less data will need to be migrated. End-users will also need to know what the new
environment will be, how it will be structured and how to access their data after the migration.
Some training may be required for them to take full advantage of the new environment.

NOTE: It’s important to understand that by default the location data being migrated to is 
new and so users should not be working in that area, potentially manipulating folders or
documents in locations that are actively being migrated to. If it’s essential for this to be
allowed, contact technical support to understand ramifications and potential
workarounds.
Was this article helpful?
0 out of 0 found this helpful

Comments