Field notes

QwenWorkWhat transfers and what does not

Migration is not a file conversion. The files are the easy part; the hard part is that a team's habits are encoded in the tools they are leaving.

The inventory that comes first

AssetTransfers?Notes
docx / xlsx / pptx filesYesOpens and edits; complex layouts may need one pass
Custom templatesMostlyMaster slides and styles carry over; fields with macros do not
VBA macrosNoLogic has to be re-expressed, usually as an automation or a script
Shared drive structureAs a decisionA good moment to collapse eleven folders into four
Naming conventionsYes, if you enforce themThe easiest habit to keep and the most valuable

What people miss in week one

Not the features. It is finding things. A team that has used the same shared drive for six years has an implicit map: the Q3 folder is next to the client folder, and the template everyone copies is buried three levels down. A new workspace has no map, and search only helps if you remember the filename.

A migration sequence that works

  1. Move one real project, not a pilot

    Pilots produce enthusiasm; real projects produce the objections you need to hear.

  2. Rebuild the two templates people actually use

    Not the twelve in the library. The two that appear in every email.

  3. Write down the folder map on paper

    Where things go, in four lines. If it needs a diagram, it is too complicated.

  4. Keep the old system read-only for a quarter

    Not for files — for the habits. People will go back to look for something, and that is fine as long as it is read-only.

The macro conversation

Every organisation has one spreadsheet that a departed employee automated with 400 lines of VBA. It cannot migrate. The honest options are: rebuild it as an automation with the vendor's task system, rebuild it as a small script, or keep one Windows machine with Excel installed specifically to run it. The third is more common than anyone admits, and it is acceptable if written down.

Do not promise feature parity. A migration that lands with 80% of the old capability and a clear list of the missing 20% succeeds. One that promises 100% and delivers 80% is remembered as a failure, even though the result is identical.
Setting up the new workspace before the move: permissions.