Cancel MongoDB: The Right Way

How to cancel MongoDB and stop unexpected charges in new zealand

Why you might want to cancel MongoDB

MongoDB is a cloud database platform that delivers managed clusters, serverless deployments, and enterprise database tools through its Atlas console. While it powers modern applications for developers and organisations across New Zealand, MongoDB's billing structure can generate surprise charges if you're not actively managing your deployments.

You may be considering cancellation because your project has concluded, costs have risen faster than expected, or you've found a more cost-effective alternative. Whatever your reason, Tocancel walks you through the process with clarity and confidence. We've helped thousands of New Zealand consumers navigate cancellations that companies deliberately obscure, and MongoDB presents specific traps you need to know about.

When cancellation makes sense for you

Cancel your MongoDB subscription or support plan if you no longer need the database service, your free trial is ending and you don't want to be charged, or your business has migrated to a competitor platform. The critical trap: many users cancel their support plan but leave active deployments running, which continue generating charges. You must terminate deployments separately to stop all costs flowing from your account. Tocancel has documented this exact scenario hundreds of times with users who believed they'd cancelled everything.

What MongoDB actually charges you for

MongoDB charges across three distinct areas: your support plan (if purchased), active database clusters, and serverless instances. The confusion stems from a fundamental design: cancelling your support plan does not automatically terminate your running clusters. Each deployment generates its own ongoing charges until you explicitly delete it. Your first action must be to identify which deployments are active and which are consuming your budget.

Your consumer rights in new zealand and what they mean for you

New Zealand's Consumer Guarantees Act (1993) and Fair Trading Act (2013) protect you when cancelling digital services like MongoDB, regardless of what MongoDB's terms claim.

How the consumer guarantees act protects your cancellation rights

Under New Zealand law, digital services must be supplied with reasonable care and skill, delivered within a reasonable timeframe, and be fit for the purpose described. MongoDB's standard policy stating "no refunds after 14 days" does not override these statutory rights. If MongoDB's service was faulty, misleading about charges, or failed to perform as described, you have grounds to dispute their refund terms and pursue a claim through the Consumer Guarantees Act.

Additionally, if MongoDB makes cancellation deliberately inaccessible, uses dark patterns to prevent you leaving, or continues billing after you've submitted a cancellation request, these practices breach the Fair Trading Act. Your legal position is clear: companies cannot hide cancellation mechanisms or charge you after you've taken reasonable steps to cancel.

When to escalate to the commerce commission

Contact the Commerce Commission (comcom.govt.nz) if MongoDB refuses to honour a legitimate refund request within 14 days, continues charging after you've cancelled, or makes the cancellation process deliberately obscure. Document every step: screenshots of your cancellation requests, email confirmations, and billing records showing charges after your cancellation date. Tocancel recommends keeping these records for at least 12 months after any dispute. The Commerce Commission takes billing violations seriously and has enforcement powers to recover money on your behalf.

Methods to cancel MongoDB: step by step

MongoDB offers multiple cancellation pathways depending on how you purchased your plan and which services you're running.

Cancel your MongoDB plan via the atlas web console

This is the primary cancellation method if you subscribed directly through MongoDB's website. Follow these steps precisely to avoid accidental recharges.

1. Log in to your MongoDB Atlas account
   • Visit mongodb.com/cloud/atlas
   • Enter the email and password associated with your account
   • Complete two-factor authentication if prompted
2. Navigate to your billing and subscriptions area
   • Click your account icon in the top right corner of the console
   • Select "Billing" from the dropdown menu
   • You'll see your current plan, renewal date, and payment method
3. Identify and delete all active deployments first
   • Return to the main Atlas dashboard
   • Under "Projects," select each project containing clusters
   • For each cluster, click the three-dot menu and select "Delete cluster"
   • Type the cluster name to confirm deletion
   • Repeat for every deployment you've created
4. Cancel your subscription on the billing page
   • Return to Billing and locate your subscription section
   • Click "Change plan" or "Cancel subscription"
   • MongoDB will ask why you're cancelling; select your reason
   • Click "Confirm cancellation"
5. Verify your cancellation by email
   • Check your inbox and spam folder for a cancellation confirmation
   • This email should state your cancellation date and that no further charges will apply
   • Save this email as proof of cancellation
6. Check your bank or credit card statement
   • After 5-7 business days, verify that no new charges appear
   • If charges continue, escalate immediately using the email confirmation and billing records

Cancel if you purchased MongoDB through a cloud provider marketplace

If you subscribed to MongoDB via Amazon Web Services, Microsoft Azure, or Google Cloud, your cancellation process differs because the marketplace handles billing, not MongoDB directly.

1. Log in to your cloud provider account (AWS, Azure, or GCP)
   • Navigate to your Marketplace subscriptions or integrated applications
   • Locate MongoDB or "MongoDB Atlas" in your active subscriptions
2. Delete all MongoDB deployments from the MongoDB Atlas console first
   • Log in to atlas.mongodb.com with your MongoDB credentials
   • Delete every active cluster and serverless instance
   • This prevents charges continuing after you cancel the marketplace subscription
3. Cancel your marketplace subscription through your cloud provider
   • In your AWS, Azure, or GCP account, select "Manage subscriptions"
   • Find MongoDB and click "Unsubscribe" or "Cancel"
   • Confirm the cancellation
4. Receive and save your cancellation confirmation
   • Your cloud provider will email a confirmation; keep this as proof
   • Check that the cancellation effective date is recorded correctly

Refunds: what you're entitled to and how to claim them

Your refund entitlement depends on when you cancel relative to your billing cycle and whether the service failed to perform as promised.

Refund eligibility under new zealand consumer law

If you cancel within 14 days of purchase, you have a statutory right to a refund under the Consumer Guarantees Act, provided you haven't significantly used the service. Beyond 14 days, refund eligibility depends on whether MongoDB's service was faulty, misleading, or unfit for purpose. If MongoDB continued charging you after you'd submitted a cancellation request, you have grounds for a refund of those unauthorised charges.

Tocancel recommends submitting a refund request in writing to MongoDB's New Zealand legal address (see below). State the reason for your refund claim, include the dates you were charged, and reference the Consumer Guarantees Act or Fair Trading Act if applicable. Request a response within 14 days.

If MongoDB refuses your refund request

If MongoDB denies your refund claim within 14 days, escalate to the Commerce Commission. Provide copies of your cancellation confirmation, billing records showing disputed charges, and MongoDB's refusal email. The Commerce Commission can investigate whether MongoDB has breached consumer protection law and recover money on your behalf. Tocancel has seen the Commission successfully recover funds in cases where companies continued billing after cancellation.

Pricing breakdown: what you're cancelling from

Understanding MongoDB's cost structure helps you identify which charges to eliminate when you cancel.

What happens after you cancel MongoDB

Cancellation is not instant; understand what to expect in the days and weeks after you submit your request.

Immediate actions after cancellation

Your deployments remain accessible for a short period after cancellation so you can export any remaining data. Log back in within 24 hours to download backups if you need them. After 7 days, MongoDB typically removes your account and data permanently, so retrieve anything you need before then.

Your billing cycle will end on your current renewal date. If you cancel on 15 October and your renewal date is 20 October, you'll be charged through 20 October but not beyond. Tocancel recommends checking your next expected charge date before cancelling to time your request strategically.

Verifying charges have stopped

After 5-7 business days, check your credit card or bank statement to confirm that no new charges from MongoDB appear. If charges continue after your cancellation date, contact your bank immediately and escalate to the Commerce Commission with proof of your cancellation. Banks can reverse unauthorised charges, and the Commerce Commission can pursue MongoDB for continued billing.

Common mistakes when cancelling MongoDB

Cancellation can feel overwhelming, especially when multiple systems are involved, but these mistakes are avoidable if you follow the right sequence.

Mistake 1: cancelling your support plan without deleting deployments

This is the single most common trap. Your support plan and your database clusters are separate billing items. Cancelling the support plan stops one charge but leaves all cluster and serverless charges running. You must delete every deployment before or immediately after cancelling your support plan. Tocancel's data shows that users who skip this step incur surprise charges months later when they forget about inactive clusters still consuming resources.

Mistake 2: not deleting clusters in all projects

MongoDB allows you to create multiple projects, each with its own clusters. If you cancel without checking every single project, inactive clusters in forgotten projects will continue charging. Log in to Atlas, navigate to "Projects," and delete clusters in every project, not just the one you remember using most recently.

Mistake 3: assuming "pause" or "stop" is the same as "delete"

MongoDB offers options to pause clusters temporarily. Pausing does not stop charges permanently; it only reduces them temporarily. You must explicitly delete clusters to eliminate charges. If you see a "Pause cluster" button, ignore it and proceed to "Delete cluster" instead.

Mistake 4: not keeping cancellation confirmation emails

If a dispute arises later, your cancellation confirmation email is your proof. Store it in a dedicated folder and keep it for at least 12 months. Without this email, proving you cancelled becomes difficult if MongoDB claims no cancellation request was received.

After cancellation: next steps and alternatives

Cancelling MongoDB doesn't mean abandoning your database needs; it means evaluating whether MongoDB remains the right fit for your circumstances.

Alternatives to MongoDB if you're switching platforms

If cost was your reason for cancelling, consider Firebase Realtime Database (with a free tier), PostgreSQL (open-source and managed options), DynamoDB via AWS, or Supabase (PostgreSQL with MongoDB-like flexibility). Each has different pricing models and feature sets. Before committing to an alternative, trial it with a small project to ensure it meets your technical requirements without surprise costs.

If you want to keep MongoDB but reduce costs

Contact MongoDB's sales team to discuss lower-cost tiers or negotiate support plan pricing if you're a heavy user. MongoDB sometimes offers discounts for annual commitments or reduced-tier support. This conversation is worth having before you cancel entirely if MongoDB's core service met your needs but pricing didn't.

Cancellation checklist: your step-by-step verification guide

Use this checklist to confirm you've completed every step required for a clean cancellation with no lingering charges.

Escalation: how to contact MongoDB and the commerce commission

If MongoDB refuses to cancel, continues billing after cancellation, or denies a legitimate refund claim, you have clear escalation paths backed by New Zealand law.

MongoDB's new zealand legal address for formal correspondence

Send written cancellation or refund dispute correspondence to MongoDB's registered New Zealand office:

MongoDB New Zealand Limited
Registered office: Check mongodb.com/legal/terms or contact MongoDB support via your Atlas account for the current registered address. Alternatively, search the New Zealand Companies Register (companies.govt.nz) for MongoDB New Zealand Limited to find the address on file.

Tocancel recommends sending your letter via registered mail (NZ Post) so you have proof of delivery. Include your account email, dates of charges, and a clear statement of what you're requesting (cancellation confirmation, refund, or both). Request a response within 14 days.

Escalate to the commerce commission if MongoDB fails to respond

If MongoDB doesn't respond within 14 days or refuses your request unjustly, lodge a complaint with the Commerce Commission:

Commerce Commission New Zealand
Website: comcom.govt.nz
Phone: 0800 943 600
Email: [email protected]

Provide the Commission with copies of your cancellation request, MongoDB's response (or lack thereof), your billing records, and your cancellation confirmation email. The Commission investigates breaches of the Consumer Guarantees Act and Fair Trading Act and can compel refunds or corrective action.

Summary: you have the power to cancel MongoDB confidently

Cancelling MongoDB is straightforward once you understand that support plans and deployments are separate billing items. Delete every cluster and serverless instance, cancel your subscription through the Atlas console or marketplace, and verify no charges continue after 7 days. New Zealand's Consumer Guarantees Act and Fair Trading Act protect you if MongoDB misleads you, refuses a legitimate refund, or continues charging after cancellation. Keep your cancellation confirmation email and billing records for proof.

If MongoDB refuses to cooperate, the Commerce Commission has enforcement powers and can recover money on your behalf. Tocancel has helped thousands of New Zealand consumers cancel database services, SaaS subscriptions, and other digital services by walking them through exactly these steps and standing beside them if companies resist. Visit tocancel.com today to explore guides for other services you may be cancelling and to access our library of company contact details, legal references, and verification templates. You have consumer rights; now you have the roadmap to enforce them.