Stuck on Apple Billing – Need Safe Migration Plan (Production App, No Downtime)

Bugs
1

Title: Stuck on Apple Billing – Need Safe Migration Plan (Production App, No Downtime)

Hey everyone,

I’m currently stuck in a situation with Replit billing and need some real-world guidance from anyone who’s gone through this.

Here’s the issue:

- My account is on the Core plan through Apple billing

- I cannot upgrade to Pro or a higher tier because of this

- Support told me I need to create a NEW account to switch to direct billing

The problem is — I’m not working on a test project.

I have a LIVE production platform with multiple integrations:

- Stripe

- Supabase (database)

- Google Analytics

- Resend (email)

- UptimeRobot

- Custom domain via GoDaddy (DNS, MX, CNAME configured)

This is a national-scale platform and already in use.

Before I migrate, I need clarity on a few critical points:

1. When I export/import via ZIP or GitHub:

  • Does EVERYTHING carry over cleanly?

  • What breaks (secrets, env variables, deployments)?

2. Deployment:

  • Do I need to unpublish first?

  • Will the new app have a new URL before reconnecting domain?

3. Domain (GoDaddy):

  • Do I just repoint DNS to the new deployment?

  • Any downtime risk?

4. Integrations:

  • Will I need to manually reconnect:

    • Stripe

    • Supabase

    • Analytics

    • Email services

5. Safest migration strategy:

  • How do I switch WITHOUT downtime or breaking production?

I’m happy to rebuild properly if needed — I just want to do this once, correctly, before scaling further.

If anyone has done this or has a clean step-by-step approach, I’d really appreciate it.

Thanks in advance :folded_hands:

Colin

1 Like
2

1. When I export/import via ZIP or GitHub:

  • Does EVERYTHING carry over cleanly?

    • No, this is definitely not what happens. I wouldn’t bother with zip, rarely works. Git is the way to go, it does a decent job.

  • What breaks (secrets, env variables, deployments)?

    • Secrets. Deployment. Some files may not transfer (like attached_assets)

2. Deployment:

  • Do I need to unpublish first?

    • You don’t have to, but you might as well.

  • Will the new app have a new URL before reconnecting domain?

    • Yes, a new dev env URL

3. Domain (GoDaddy):

  • Do I just repoint DNS to the new deployment?

    • Correct, just as you have done before. Add the custom domain after successful deploy, add the new txt record (A record will remain the same). Wait for verify. Easy.

  • Any downtime risk?

    • Yes, there will likely be some downtime. If you have this in production, you should notify users of some possible downtime.

4. Integrations:

  • Will I need to manually reconnect:

    • Stripe

      • Stripe connector? Yes. Direct API? Yes.

    • Supabase

      • Same as above

    • Analytics

      • Google GA4? No migration needed.

    • Email services

      • Depends. Probably same as Stripe/Supabase. Need more info.

5. Safest migration strategy:

  • How do I switch WITHOUT downtime or breaking production?

    • You don’t. You probably can’t verify the same domain on two separate projects at the same time (never tried, but illogical). But you can make it fairly seamless. Downtime can be mitigated to DNS verification period - probably 5-10 minutes.