Migration from Self-Hosted to Cloud seems broken

Hello,

I'm trying to migrate from my Self-Hosted Appwrite instance to Cloud, and can't figure out what's going wrong.

• If I initiate the migration from Cloud, it fails instantly without any useful logs.
• If I initiate the migration from Self-Hosted, it shows an "invalid API key" error when listing resources before migrating.

I've just updated my Self-Hosted instance to 1.9.1. Given that I don't have much logs, I'm not sure what information I could add. This is all I see when it fails instantly from Cloud:

{
  "$id": "69d8c9e14612ada932fa",
  "$createdAt": "2026-04-10T09:58:57.287+00:00",
  "$updatedAt": "2026-04-10T09:58:57.936+00:00",
  "status": "failed",
  "stage": "finished",
  "source": "Appwrite",
  "destination": "Appwrite",
  "resources": [
    "user",
    "team",
    "membership",
    "database",
    "table",
    "column",
    "index",
    "row",
    "bucket",
    "file",
    "function",
    "environment-variable",
    "deployment",
    "site",
    "site-variable",
    "site-deployment",
    "provider",
    "topic",
    "subscriber",
    "message"
  ],
  "resourceId": "",
  "statusCounters": [],
  "resourceData": [],
  "errors": [],
  "options": []
}

And the destination project ID: 69d8c9b60011bf0e3ba6

Has this issue be seen already?

Thanks

Hey, happy to help!
Both issues point to one likely cause.... is your self-hosted instance publicly accessible on the internet with a valid domain and SSL?

Yes it is, and resources can be retrieved without issues when initiated from the Cloud. Then I select every one of them, hit start, and it instantly fails.

Good to know.... so the resource listing works fine, which rules out connectivity. The instant failure on start is likely a version compatibility issue between your self-hosted 1.9.1 and the Cloud migration worker, or a payload validation error that isn't surfaced in the logs. Can you check your self-hosted instance logs (appwrite container) right at the moment you hit start? That should catch whatever's being thrown before the status flips to failed.

I'll try, though I may have a lead: disabled Cloudflare proxy for the domain, now I can't access the instance (Websites prove their identity via certificates, which are valid for a set time period. The certificate for <redacted> expired on 12/23/2025.). Certificate seems fine when proxy in ON. Is there a procedure to force regenerate the certificate?

Re-enabled proxy, re-tried a migration and looked at the logs: nothing, as in it never receives requests.

Found https://appwrite.io/docs/advanced/self-hosting/configuration/tls-certificates#manual-generation, I try that

SSL seems fine now, though the migration still fails

Oh sorry, just realized my self-hosted instance is on 1.9.0. Don't know from where I've written 1.9.1.

The SSL fix was worth trying but since migration still fails and the logs show no incoming requests, it sounds like Cloud's migration worker isn't able to reach your instance at all or is hitting something silently before the request lands. This is getting into territory that's tricky to debug without direct access. Feel free to DM me, I've handled similar Appwrite migration issues before and can help you get it sorted.

Can someone who doesn't lure you into DMs to request payment could help?