Upgrade & Downgrade Guide

Desktop IDE Version Updates

Automatic Updates

Atlas Studio checks for updates automatically on launch (requires internet connection). When an update is available:

A notification appears in the bottom status bar: “Update available — v1.0.x”
Click Update Now to download in the background
When ready: Restart to apply update
The update is applied on restart — all settings, workflows, and credentials are preserved

Auto-updates download in the background while you work. The new version is only applied when you choose to restart.

Manual Update

If auto-update isn’t available (air-gapped environment):

Download the latest version from atlastechlab.com/studio/downloads
Install over the existing installation — settings and data are preserved

Checking your current version

macOS: Atlas Studio → About Atlas Studio
Windows: Help → About
Linux: Help → About

Or via command line:


# macOS
/Applications/Atlas\ Studio.app/Contents/MacOS/AtlasStudio --version
 
# Linux
./AtlasStudio.AppImage --version

Rollback to a Previous Desktop Version

If a new version causes issues:

Download the previous version

Previous releases are available at: https://downloads.atlastechlab.com/studio/v{VERSION}/

Or via the releases page .

Uninstall the current version

macOS


rm -rf /Applications/Atlas\ Studio.app

Install the previous version

Do not delete your data directory — settings, workflows, and credentials are stored separately.

Disable auto-update

Settings → Updates → Disable automatic updates (to stay on this version).

Subscription Plan Upgrades

Upgrading from Free to Growth or Pro

Go to studio.atlastechlab.com and sign in.

Navigate to Billing

Click Billing in the left sidebar → Upgrade Plan.

Select your new plan

Choose Growth ( $49/user/month) or Pro ($ 149/user/month). Toggle between monthly and annual (20% discount).

Complete checkout

Enter payment details via Razorpay. The upgrade is instant — no restart needed.

Verify new limits

Billing → Current Plan shows your new limits. New AI credits are added immediately.

Downgrading Plans

What to do before downgrading

Audit workflows — Web Portal → Workflows → count active workflows vs. new plan limit
Review team members — Team → count members vs. new plan limit
Check connectors — count active connectors vs. new plan limit
Export important data — export critical workflow definitions and reports

Performing the downgrade

Web Portal → Billing → Change Plan → select lower tier
Confirm you’ve reviewed the impact
The downgrade is scheduled for end of billing period — you keep current limits until then

What gets paused vs. deleted

Resource	At downgrade
Excess workflows	Paused (not deleted) — reactivate by upgrading or archiving others
Excess team members	Access revoked — users can still log in but can’t run workflows
Excess runners	Deregistered — running jobs complete, then runner goes offline
Vault secrets (over limit)	Read-only — workflows using them continue to work
Audit logs (over retention)	Archived to cold storage — still retrievable via support
Compliance features (SAP, mainframe)	Disabled — workflows using these nodes are paused

Migrating from Free to Production Use

When moving from evaluation to production:

Upgrade to Growth or Pro

Ensures you have enough workflow runs, runners, and connectors for production.

Set up team members

Web Portal → Team → Invite your engineering team with appropriate roles.

Configure SSO (Pro/Enterprise)

Settings → SSO → configure your SAML/OIDC provider for single sign-on.

Deploy production runners

Web Portal → Runners → Deploy Runner → follow the guide for Kubernetes runner deployment.

Migrate workflows from local to production

In the Desktop IDE: File → Export Workflow → save as JSON. In Web Portal: Workflows → Import → upload JSON.

Review credentials

Audit that all workflow credentials are in the Vault (not hardcoded). Web Portal → Settings → Credentials.

Test with a staging runner first

Tag a runner as staging and test your promoted workflows before assigning them to production runners.

Enterprise Migration

Migrating from self-hosted or another platform to Atlas Studio Enterprise:

Discovery call with our solutions team (schedule at atlastechlab.com/contact )
Workflow migration — we provide bulk import tooling for:
- Control-M jobs → Atlas Studio workflows
- cron scripts → Atlas Studio scheduling
- Rundeck runbooks → Atlas Studio runbooks
Connector migration — existing integrations are mapped to Atlas connectors
Training — 2× remote training sessions for your team
Go-live support — dedicated engineer during cutover week

Version Compatibility

Desktop IDE Version	Web Portal API	Notes
1.0.x	v1	Current release
0.9.x	v1 (limited)	Upgrade recommended

The Desktop IDE and Web Portal are forward-compatible within the same major version. We maintain 2 versions of backward compatibility for the API.