Tips for Migrating Jira Server to Cloud as an Indie Dev: Handling Custom Workflows and App Data?

[Bunny]

I'm an indie mobile game mod developer (running a small site with 10K+ users for racing tweaks—CarX Street Mods), and we're finally ditching our ancient Jira Server instance (v8.20.5) for Cloud Premium. With Server EOL long past, it's time—especially since our custom workflows for bug tracking mod releases and user feedback tickets are getting clunky on self-hosted.

We're a lean team (me + 2 freelancers), so a phased migration makes sense: Start with users/groups, then data via JCMA. From Atlassian's guide, I know to test apps first (e.g., our ScriptRunner for automated permission audits), but what's the real-world gotcha for devs like us?

• Workflow Mapping: Our server has mod-specific schemes (e.g., "Drift Bug → QA Test → Release"). How do you recreate these in Cloud without losing automation? CCMA for Confluence pages too?
• App Compatibility: Migrating to Forge apps—anyone swapped Server plugins for Cloud equivalents without downtime? Tips for 1000+ historical issues?
• Data Cleanup: Pre-migration checklists mention archiving old data—how much is "too much" for Cloud performance? We're at ~5K tickets.

Planning a test run next week with the free migration trial. Grateful for any phased strategy tips, especially for solo admins—phased vs. big-bang? Tools like MAGIC for small sites?

Thanks in advance—excited for Rovo AI in Cloud! #JiraMigration #ServerToCloud #IndieDev