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.
PricePrice fixed after a short scope call.
DeliveryThe calendar is set once the data, the dependencies and the cutover requirements have been checked, then fixed in writing before the move begins.
What you receive · illustrative sample
Confirm the files, permissions and exceptions.
Illustrative file-migration acceptance sheet. Unsupported paths are handled separately from optional content reorganization.
| Source item | Destination check | Acceptance |
|---|---|---|
| Sample department share | Agreed file counts, sizes and exceptions reconciled | Owner reviews reconciliation |
| Restricted project folder | Named users can open it; other pilot users cannot | Permission test recorded |
| Unsupported source path | Approved technical rename and link impact listed | Exception accepted or corrected |
Meet the person responsible for delivery.
Alwatheq Zboun leads the agreed work. A sample shows the format; the statement of work defines your deliverable and acceptance checks.
Engagement context
When this engagement applies.
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
The defined work
Engagement scope.
- 01
What is in scope is counted before anything moves, and each folder gets a named destination.
- 02
Permissions are mapped as they are today, and the target list of who can open what is agreed in writing before the move.
- 03
File names and paths the destination will not accept are found first and fixed, rather than discovered as failures mid-move.
- 04
The move runs in dated groups, and each group is checked before the next one starts.
- 05
The destination is checked against the source file by file, and every gap is closed or given an owner.
Acceptance
Completion has an agreed standard.
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
Commercial basis
Price, scope and timing are considered together.
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 workScope & responsibilities
The full engagement boundary.
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
Before you commit
A clear first step.
You stay in control.
Start with the problem and the result you need. The initial fit conversation is free and does not require access to your systems.
Check client feedback on Upwork ↗Prefer to contract through Upwork? Contact Alwatheq there. Existing Upwork engagements continue through Upwork.
Who will actually do the work?
Alwatheq Zboun leads the scope, technical work and handover. If a specialist collaborator is needed, their role is agreed with you before work starts. Your proposal names the responsibilities and delivery windows.
What happens before you get access?
We agree the scope, fee and completion checks in writing. Access uses named accounts and only the permissions the work requires. Approved access is reviewed and removed at handover.
How do we know the change worked?
Your scope defines the pilot, test cases and acceptance checks. Results and exceptions are recorded. Recovery options and their limits are agreed before production changes; a failed check is addressed before the next approved stage.
Will we need an ongoing retainer?
A defined project can end at handover. Your team receives the agreed configuration records, runbook and walkthrough. Any limited support period is written into the proposal; ongoing support or additional work is a separate agreement.
Discuss this engagement
Put the scope in context.
Describe the problem, systems and deadline. Alwatheq will review the fit and the scope questions before preparing a written proposal.
Plan the File Move