MongoDB Downgrade & Host Switch

I am shutting down operations and want to slim my infrastructure to only what is strictly necessary. Right now the live MongoDB cluster sits on an Atlas M10; the whole data set is under 1 GB and I don’t expect it to grow. I therefore believe the free-tier M0 should be enough—but I’d like a professional opinion based on the actual stats (indexes, connections, oplog, etc.).

Once you confirm that M0 is viable, I need the data moved there with zero loss and the connection string updated inside my Node.js back-end. A short hand-off session or concise notes on where and how the URI was changed will be fine; no index re-work is required.

The second part of the job is traffic redirection. Production currently runs on AWS while staging is on Hostinger. I’m closing the AWS account, so all traffic needs to flow to the Hostinger instance. You’ll handle the DNS or load-balancer changes and verify that SSL, environment variables, and any hard-coded endpoints still behave correctly after the switch.

Deliverables
• Report confirming M0 suitability with key metrics
• Successful migration from M10 to M0 on MongoDB Atlas
• Updated Node.js connection string and brief guidance for future edits
• DNS/traffic cut-over from AWS to Hostinger, tested and confirmed live

If this sounds straightforward to you, let’s proceed.