Find and export
your MongoDB data.

1. 1Connect through mongosh with permission to run database statistics.
2. 2Run db.stats() for each application database in scope.
3. 3Record dataSize, storageSize and indexSize separately, with their scale and units.
4. 4Review document counts and the earliest relevant timestamps. Atlas cluster metrics provide another storage cross-check.

Report in GB with the measurement basis, databases and collections identified. Add document counts where available.

Describe file storage such as GridFS or external object stores, the business date coverage and application scope.

1. 1Have the administrator plan a consistent collection appropriate to the deployment and write activity.
2. 2Use mongodump for BSON documents and collection metadata in the agreed databases.
3. 3For a replica set, review the supported oplog option where appropriate; sharded deployments require their own consistency plan.
4. 4Collect external files separately and verify the archive's collection coverage.

mongoexport provides JSON or CSV for selected collections and serves a different purpose from a database backup.

BSON can represent types that need special handling in simpler formats. Preserve schema and type context with the data.

Document collections can capture complete application events with their nested business context.

Collection and field descriptions help connect those events to the workflows they represent.

Select databases, collections and fields in scope, reviewing personal information and sensitive application content.

Telegraph Lab reviews the proposed material with you and agrees how sensitive information will be handled. Preparation can include excluding material, redacting details and replacing personal identifiers. Your company keeps ownership; the licensing agreement defines the material, permitted uses and authorized recipients.