Request an Architecture Briefing

Defined implementation

Move your files with access planned and checked.

Move the agreed files, test user access and compare the destination with the original inventory. Record differences and any issues that need an owner.

Plan the File Move Review scope & terms

Price fixed after a short scope call. Price drivers and project calendar ↓

Illustrative sample · constructed example

A path exception needs an action, not a green total.

Reconciliation excerpt · constructed project folder

Source

Projects / Sample project / Drawing register.pdf

Destination

SharePoint / Projects / Drawing register.pdf

Access check

Project member opens the file; an unrelated pilot user is denied.

Selected check

Has the path exception been corrected and the destination checked?

Evidence
The source path needs an approved technical rename before transfer.
Decision
Keep the exception open
Next action
Owner approves the rename and identifies links that need updating.

Constructed row using the documented reconciliation method. It is not a recovered client file or an aggregate success rate.

Delivered SharePoint troubleshooting and reconciliation; identifying files and paths are withheld.

Inspect the related record ↗

Open the complete illustrative document to inspect its fields and print a copy.

Open the sample document ↗

File and Document Migration

The work starts here.

Files have to come off a file server, a NAS, Google Drive or Dropbox, because the hardware is going, the contract is ending, or the team cannot work from it any more.

Scope considerations

  • Permissions agreed in writing first
  • Checked file by file before sign-off
  • You decide what is left behind

What AZ changes or delivers

  1. 01

    What is in scope is counted before anything moves, and each folder gets a named destination.

  2. 02

    Permissions are mapped as they are today, and the target list of who can open what is agreed in writing before the move.

  3. 03

    File names and paths the destination will not accept are found first and fixed, rather than discovered as failures mid-move.

  4. 04

    The move runs in dated groups, and each group is checked before the next one starts.

  5. 05

    The destination is checked against the source file by file, and every gap is closed or given an owner.

Acceptance

Checks before handover

  • Every folder on the agreed list has arrived at its named destination

  • Access is tested against the agreed list of who should be able to open what

  • The agreed source and destination counts are reconciled, exceptions are recorded, and technical path or filename changes are listed for approval

Scope, price and project calendar

Engagement price

Price fixed after a short scope call.

The price is agreed in writing before any work starts and before anyone is given access. The call itself costs nothing. What moves the number:

What determines the scope

  • How much data is moving, and how many shares or sites it comes from
  • Whether permissions carry across or have to be rebuilt at the destination
  • How much has to be sorted, archived or left behind before the move
  • Whether people keep working in the files while the move runs

Delivery calendar

The calendar is set once the data, the dependencies and the cutover requirements have been checked, then fixed in writing before the move begins.

How engagements work

Scope & responsibilities

Responsibilities and exclusions

Review the exclusions, required client participation, change controls and operational handover for this engagement.

Exclusions
  • Licenses needed to run the move
  • Business content sorting or reorganization, unless separately agreed. Necessary technical path/name corrections is identified and approved within the migration scope
  • Repairing a source system that is already failing
  • Help desk and staff support
Client responsibilities
  • Decide what moves, what gets archived, and what is left behind
  • Confirm who should be able to open what at the destination
  • Give administrator access to the source and the destination
  • Tell your staff when the files move and support them afterwards
Change and rollback method
  • Folders move in dated groups, and a group is not started until the one before it checks out.
  • The conditions that stop the move are agreed before the first file moves, and they name conditions rather than intentions.
  • The source stays readable until the check sheet is signed off, so a gap found late still has somewhere to be recovered from.
Operational record and handover
  • The counted list of everything that moved
  • The permissions map, before and after
  • The list of names and paths that had to be changed to survive the move
  • The agreed conditions for stopping
  • The check sheet proving source and destination match

Access, acceptance and support arrangements ↗

Discuss this engagement

Discuss File and Document Migration

Describe the problem, systems and deadline. We will review the fit and the scope questions before preparing a written proposal.

Plan the File Move