This guide provides a step-by-step path for migrating existing applications to Azion. It outlines the necessary requirements and details the steps for a successful transfer of applications from other services to a distributed architecture.

Migrating from other platforms

If you’re migrating from a specific platform, Azion provides dedicated migration guides:

• Cloudflare: Cloudflare to Azion migration guide — covers Workers, KV, R2, D1, DNS, WAF, and more

Why migrate to Azion

Migrating to Azion Web Platform provides distinct advantages for modern applications:

Performance

• Cold-start-free execution on a distributed architecture
• Instant deploys with zero-downtime updates
• Global points of presence that execute logic close to your users

Cost efficiency

• Zero egress fees for data transfer over Azion’s infrastructure
• Predictable pricing without hidden bandwidth charges

Platform unification

• Build, secure, store, and observe in one integrated environment
• Consistent APIs and configuration patterns across all capabilities
• Single platform for applications, functions, storage, databases, and security

Prerequisites

Before starting the migration, ensure you have the following:

• Azion account: Create a free account at Azion Console. You’ll need access to the Console to create applications and configure domains.

  Create an Azion account

• Azion CLI (optional but recommended): Install the CLI for local development and deployment. The CLI provides a streamlined workflow for building, testing, and deploying applications.

  Azion CLI overview

Before you begin

Before you migrate applications to Azion, there are two major variables that must exist:

1. Connector: the source server of the application. This entry point takes the form of either a host, an IPv4, or an IPv6 address of a storage service or an existing application.

2. Workload: the target domain of the application. This output takes the form of an Azion domain, which can be pointed to a custom domain.

Most applications need a connector from which Azion retrieves the content and code that make them up. That application passes through Azion’s global points of presence for it to be delivered to users through a domain address associated with a workload.

Step 1: Create an application

You can start by creating an application using a basic template. A recommended option is the Hello World template, which uses Functions to run a simple function on a distributed architecture.

See the full list of available templates.

Step 2: Test locally

Before fully deploying the application, the recommendation is to stage your application through the hosts file to ensure everything is working correctly. This step helps to identify and address any misconfigurations or issues caused by the migration.

Step 3: Point the domain to a workload

The final step to fully migrate your application to Azion is to point your custom domain to the Azion’s workload. By doing so, you allow users to access your application through its domain, reducing latency and processing costs on the origin.

After migration

Once your application is running on Azion, configure these essential features:

Configure observability

Monitor your application’s performance and behavior in real time:

• Real-Time Metrics — View requests, bandwidth, latency, and cache hit ratios through dashboards and GraphQL API
• Real-Time Events — Access detailed logs for requests, functions, WAF events, and more for troubleshooting

Enable security features

Protect your application with Azion’s security capabilities:

• Web Application Firewall — Guard against SQL injection, XSS, and other application-layer attacks
• DDoS Protection — Automatic protection against volumetric and protocol attacks

Continue learning

Explore the documentation to get the most from Azion Web Platform:

• Applications documentation
• Functions documentation
• Rules Engine documentation