Migration¶
A migration moves the existing pictures of a company from one storage source to the other: from Tenant Media to External File Storage, or back. It covers every kind of record Media Bridge manages (items, item variants and employees) in one run.
What's in this section¶
- Migrate pictures: run the migration wizard, in the foreground or as a background job.
- Monitor migration runs: follow a run and read its counters.
- Fix failed records: read the migration log, retry failed records, or resume a run.
- Cancel a stuck run: release a run that no longer runs, so a new migration can start.
- Clean up migration history: delete old runs automatically with a retention policy.
How a migration works¶
flowchart TD
A[Start the wizard] --> B[Choose From and To]
B --> C[Choose options]
C --> D{Run in background?}
D -- No --> E[Run now]
D -- Yes --> F[Job queue entry runs it]
E --> G[Each record with a picture in From]
F --> G
G --> H[One log line per record]
H --> I{Any failed records?}
I -- No --> J([Completed: storage source switches to To])
I -- Yes --> K([Completed with Errors: storage source unchanged])
K --> L[Retry failed records or resume the run]
L --> I
classDef goal fill:#ccffcc,stroke:#155724,color:#155724
classDef warn fill:#fff3cd,stroke:#856404,color:#856404
class J goal
class K warn
Key rules¶
- Only records with a picture in the source are processed. Records without a picture are not counted.
- The storage source switches only after a run without failures. A run that completes with errors keeps the current storage source, so no picture becomes unreachable.
- Only one migration can run at a time, per company.
- Nothing is uploaded twice. Retrying or resuming a run skips records that were already transferred.
- Progress is saved every 500 records. An interrupted run loses at most the current batch, and can be resumed.
- Consumer companies can't migrate. A company that reads its pictures from a media source company has no pictures of its own to move.