A steel structure repaired component archive link migration checklist helps EPC teams move repair records without breaking final retrieval. During a project, repair evidence may live in temporary review folders, quality drives, engineering comment folders, site issue trackers, or cloud links created by individual users. At closeout, those links often need to be migrated into a controlled owner archive.
The risk is not only that a link stops working. A migrated link may open the wrong revision, skip restricted evidence, lose the relationship between component mark and repair number, or leave historical transmittals pointing to a location that is no longer controlled. This checklist gives document controllers and quality teams a practical way to migrate links while preserving traceability.
1. Map the original link locations
Before moving archive links, record where the current links point and why they exist. Do not start by copying folders into a new location without a source map. The source map shows which links must be preserved, replaced, disabled, or kept only as historical references.
- List links from transmittals, email records, comment logs, archive indexes, NCR closeout packages, and handover trackers.
- Record whether each link points to a file, folder, photo package, review workspace, or document management record.
- Record the repaired component mark, repair reference, NCR number, inspection record, or acceptance record tied to the link.
- Identify links owned by personal accounts or temporary project groups.
- Separate final archive links from links that only supported review comments or temporary evidence exchange.
For the starting file map, use the repaired component archive index checklist.
2. Define the target archive location
Migration should have a defined target, not just a new folder name. The target archive should be stable after project closeout and should match the owner's document control or maintenance record structure.
| Target decision | Migration check |
|---|---|
| Owner document system | Confirm accepted records can be searched by component mark, repair reference, and final acceptance status. |
| Project closeout archive | Confirm access remains available after contractor project accounts are closed. |
| Maintenance handover folder | Confirm repair limitations, transferred items, and inspection notes remain visible to the right users. |
| Restricted technical archive | Confirm engineering dispositions and root cause records are migrated under controlled permissions. |
For access rules in the target location, use the archive access control checklist.
3. Preserve final record relationships
Link migration should not break the relationship between a repaired component and its evidence. If files are moved into new folders but their references are not preserved, future users may find a photo set without knowing which NCR it closes, or a signed acceptance record without the related inspection evidence.
- Keep component mark, repair number, NCR number, inspection number, and final acceptance record connected in the target archive.
- Preserve links between transferred items and their later closeout records.
- Keep repair limitations and accepted conditions connected to the final release record.
- Make sure superseded drafts are not migrated as final files unless clearly labelled as historical records.
- Confirm the archive index points to the migrated final location, not the old temporary folder.
For evidence relationships, use the repaired component audit trail checklist.
4. Replace old links without losing history
Old links should not simply disappear. Historical transmittals and comment records may still reference the old route. The migration record should show what old link was replaced, where the record moved, and whether the old link was disabled, redirected, or kept as read-only historical access.
- Record original link, target link, migration date, migration owner, and approval owner.
- Record whether old links are disabled, redirected, or kept temporarily active.
- Confirm old public links do not bypass the permission rules of the target archive.
- Update archive indexes, handover trackers, and final transmittal references with the migrated link.
- Keep a migration log with the final repaired component archive package.
For issue and transmittal history, use the transmittal record checklist.
5. Retest permissions after migration
Permissions often change during migration. A folder that was open to a review group may become restricted in the owner system, or a restricted file may accidentally move into a general handover folder. Permission testing should be done after migration, not assumed from the source folder.
| User role | Access after migration |
|---|---|
| Owner handover user | Can retrieve accepted repair records, limitations, and final status documents. |
| Quality user | Can open inspection evidence, NCR closeout files, and final repair records. |
| Engineering reviewer | Can access restricted dispositions through the approved technical route. |
| External expired user | Cannot open old review links or restricted records after access is removed. |
For periodic user review, use the archive permission review checklist.
6. Test retrieval from the target archive
A migration is only successful when users can retrieve the final record from the target archive without asking the original project team to resend files. Test retrieval by using the normal search route or index route expected after handover.
- Search by component mark and confirm all final repair records appear.
- Search by repair number or NCR number and confirm the same final package can be opened.
- Open final inspection evidence, photo records, acceptance records, and transferred item closeout records.
- Open restricted technical records through the approved reviewer role.
- Confirm old links do not remain the only way to find the record.
For retrieval testing, use the archive retrieval checklist.
7. Control link expiry during migration
Some old links should expire after migration. Others may need a short overlap period while the owner confirms the new archive route. Define those rules before disabling source folders or project accounts.
- Set an expiry date for temporary review links after target archive access is verified.
- Keep a short overlap period only where required for owner verification.
- Record links that must remain active for contractual or legal archive reasons.
- Disable public links after the controlled target archive is available.
- Retest retrieval after old links expire.
For expiry controls, use the archive link expiry checklist.
Final archive link migration checklist
Before closing migration, confirm:
- All original links are mapped with source, purpose, owner, and linked repaired component record.
- The target archive location is stable after project closeout and owner handover.
- Component marks, repair references, NCR numbers, inspection records, and acceptance records remain connected.
- Old links are replaced, disabled, redirected, or retained with written justification.
- Permissions are retested after migration for owner, quality, engineering, and expired external users.
- Retrieval is tested from the target archive without depending on old temporary links.
- The migration log is stored with the final repaired component archive.
Red flags in archive link migration
- Files are copied into a new archive without a source link map.
- Old transmittals point to folders that no longer exist and no replacement route is recorded.
- Owner users can open final records only through temporary project accounts.
- Restricted technical records move into general handover folders.
- Archive index links are updated, but comment logs and acceptance records still point to old links.
- No retrieval test is performed after project folders are closed.
Buyer note: Link migration is a handover quality control, not only an IT task. EPC buyers should require a source map, target archive rule, replacement log, permission retest, link-expiry plan, and retrieval test before accepting migrated repaired component records.