[Feature]: How to migrate data from Milvus 2.x to another milvus

Description

Contributor guide

Tech stack

go

Domain

database

Issue type

feature

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

4

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

over 1 week

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

blocked

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

needs investigation

Prerequisites

Milvus architectureVector database conceptsData migration strategies

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

15

Research direction

First, review the issue comments to gather any additional context about the M2M migration request and the DM tool limitation. Then, search the Milvus codebase for existing migration utilities or documentation in the 'tools' or 'docs' directories. Consider proposing a high level design or a minimal viable migration script. Avoid diving deep into implementation until the scope is clarified with maintainers.