Migration Overview

Mock API Builder helps you develop and test your application quickly. When your real backend is ready, you'll need to migrate from mock APIs to production APIs. This guide covers strategies for a smooth transition.

Incremental

Migrate endpoints gradually, testing each one before moving to the next

Environment-Based

Use different APIs per environment (dev/staging/prod)

Parallel Testing

Run both mock and real APIs side-by-side for validation

Strategy 1: Environment-Based Configuration

Setup Multiple Environments

The simplest approach is to use environment variables to switch between mock and production APIs:

.env.development (Local Dev)

plaintext

.env.staging

plaintext

.env.production

plaintext

API Configuration File:

javascript

Deployment Configuration

Platform Environment Variables:

Go to your hosting platform's project settings → Environment Variables
Set NEXT_PUBLIC_API_URL for each environment:
- Development: Mock API URL
- Preview: Staging API URL
- Production: Production API URL
Redeploy to apply changes

Strategy 2: Incremental Endpoint Migration

Endpoint-by-Endpoint Switching

Migrate one endpoint at a time while keeping others on the mock API:

javascript

Using in Services:

javascript

Migration Checklist per Endpoint

Verify production endpoint exists and returns expected data structure
Compare response schemas between mock and production
Update endpoint configuration to point to production
Test in staging environment first
Monitor for errors in production logs
Keep mock as fallback temporarily in case of issues
Remove mock dependency once stable

Strategy 3: Feature Flags

Dynamic API Switching with Feature Flags

Use feature flags to toggle between mock and production APIs at runtime:

javascript

Enable flags progressively:

bash

Validating the Migration

Compare Mock vs Production Responses

javascript

Automated Migration Tests

javascript

Rollback Strategy

Quick Rollback to Mock APIs

Always have a rollback plan in case production APIs have issues:

Option 1: Environment Variable Toggle

bash

Option 2: Fallback Logic

javascript

Warning: Automatic fallback can mask production issues. Use logging and monitoring to detect when fallbacks occur.

Post-Migration Monitoring

Track API Usage and Errors

javascript

Migration Best Practices

Migrate incrementally don't switch everything at once, test each endpoint
Test in staging first validate production APIs in non-prod environment before going live
Compare response schemas ensure production matches mock structure to avoid breaking changes
Keep mock APIs available maintain for development and testing even after migration
Monitor actively watch for errors and performance issues after switching
Have a rollback plan be ready to quickly switch back to mocks if needed
Update documentation keep API docs current with migration status
Communicate with team ensure everyone knows when endpoints are migrated

Migration Overview

Incremental

Migrate endpoints gradually, testing each one before moving to the next

Environment-Based

Use different APIs per environment (dev/staging/prod)

Parallel Testing

Run both mock and real APIs side-by-side for validation

Strategy 1: Environment-Based Configuration

Setup Multiple Environments

The simplest approach is to use environment variables to switch between mock and production APIs:

.env.development (Local Dev)

plaintext

.env.staging

plaintext

.env.production

plaintext

API Configuration File:

javascript

Deployment Configuration

Platform Environment Variables:

Go to your hosting platform's project settings → Environment Variables
Set NEXT_PUBLIC_API_URL for each environment:
- Development: Mock API URL
- Preview: Staging API URL
- Production: Production API URL
Redeploy to apply changes

Strategy 2: Incremental Endpoint Migration

Endpoint-by-Endpoint Switching

Migrate one endpoint at a time while keeping others on the mock API:

javascript

Using in Services:

javascript

Migration Checklist per Endpoint

Verify production endpoint exists and returns expected data structure
Compare response schemas between mock and production
Update endpoint configuration to point to production
Test in staging environment first
Monitor for errors in production logs
Keep mock as fallback temporarily in case of issues
Remove mock dependency once stable

Migration Best Practices

Migrate incrementally don't switch everything at once, test each endpoint
Test in staging first validate production APIs in non-prod environment before going live
Compare response schemas ensure production matches mock structure to avoid breaking changes
Keep mock APIs available maintain for development and testing even after migration
Monitor actively watch for errors and performance issues after switching
Have a rollback plan be ready to quickly switch back to mocks if needed
Update documentation keep API docs current with migration status
Communicate with team ensure everyone knows when endpoints are migrated

Migration Strategies

Migration Overview

Strategy 1: Environment-Based Configuration

.env.development (Local Dev)

.env.staging

.env.production

API Configuration File:

Platform Environment Variables:

Strategy 2: Incremental Endpoint Migration

Using in Services:

Strategy 3: Feature Flags

Enable flags progressively:

Validating the Migration

Rollback Strategy

Option 1: Environment Variable Toggle

Option 2: Fallback Logic

Post-Migration Monitoring

Migration Best Practices

Migration Strategies

Migration Overview

Strategy 1: Environment-Based Configuration

.env.development (Local Dev)

.env.staging

.env.production

API Configuration File:

Platform Environment Variables:

Strategy 2: Incremental Endpoint Migration

Using in Services:

Strategy 3: Feature Flags

Enable flags progressively:

Validating the Migration

Rollback Strategy

Option 1: Environment Variable Toggle

Option 2: Fallback Logic

Post-Migration Monitoring

Migration Best Practices