Many GraphTokenLock contracts have vested a long time ago, and their owners are free to remove their funds from them. However, many choose not to do so because these contracts are currently used for Indexer stake, Delegation, or Curation, and there is no easy way to exit funds out of the contract without disrupting indexer operation.
While I appreciate the proposed migration helper that offers a path to migrate GRT held through these contracts, the method is cumbersome. Indexers, for instance, will have to wait for the migration contract to become available to deploy to Arbitrum, because the indexer address will be the counterpart vesting lock contract. Indexers may want to deploy immediately to support the L2 migration early, but are prevented of doing so. Additionally, even if the original contract is fully vested, the contract owners will have to use an L2 Token Lock contract with all the problems it entails. (See this post for the difficulties it causes: GIP-0045: Enable beneficiary change for indexers' tokenlock smart contracts)
Therefore, I would like to suggest a second migration path for TokenLock holders that are fully vested. and are not encumbered with any restrictions (past endTime). The migration would then be identical to the standard case.