Help Center/ Migration Center/ FAQs/ Storage Migration/ Why Are There Skipped Objects in the Initial Migration?
Updated on 2026-06-30 GMT+08:00
Why Are There Skipped Objects in the Initial Migration?
Symptom
When a migration task was executed for the first time, the migration statistics show that some objects were skipped.

Solution
This is a normal phenomenon determined by the flat structure of object storage and the used overwriting policy.
- In object storage, folders are objects. A folder, for example, 1000-files/, is essentially an 0-byte object. When OMS executes concurrent migrations, if files within a folder (for example, 1000-files/xxx.txt) are migrated first, the system automatically creates the corresponding folder at the target.
- When the task subsequently processes the folder itself (1000-files/), the system detects that an object with the same name already exists at the target. The system then compares the attributes of the source and target objects based on the selected overwriting policy. If the overwriting policy criteria are met, the source object is skipped.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot