Skip to main content

Migration Guide

This guide explains how to migrate between 23blocks deployment modes, including requirements, process, and what to expect.

Your Data, Your Choice

23blocks is committed to data portability. You can migrate between deployment modes or leave 23blocks entirely with your data intact.

Supported Migration Paths​

FromToSupportedNotes
Shared CloudDedicated Cloud✅ YesMost common upgrade path
Shared CloudPartner Managed✅ YesRequires partner engagement
Shared CloudSelf Managed✅ YesRequires DevOps capability
Dedicated CloudPartner Managed✅ YesChange who manages your infra
Dedicated CloudSelf Managed✅ YesTake over management
Partner ManagedDedicated Cloud✅ YesMove to 23blocks management
Partner ManagedSelf Managed✅ YesTake over from partner
Self ManagedDedicated Cloud✅ YesHand over to 23blocks
Self ManagedPartner Managed✅ YesEngage partner for operations
Any ModeShared Cloud⚠️ LimitedOnly for small data volumes

Requirements Before Migration​

1. Written Notice​

30 days written notice is required before any migration.

Submit your migration request via:

  • Email to migrations@23blocks.com
  • Support ticket in your dashboard
  • Through your account manager (Dedicated Cloud customers)

2. Account in Good Standing​

Your account must be in good standing:

  • ✅ Active subscription (not suspended)
  • ✅ No outstanding support issues blocking migration
  • ✅ Terms of Service compliance

3. All Invoices Paid​

All outstanding invoices must be paid before migration can proceed.

  • Review your billing history in the dashboard
  • Pay any overdue invoices
  • Contact billing@23blocks.com with payment questions

Migration Process​

Phase 1: Request & Planning (Days 1-7)​

  1. Submit Migration Request

    • Specify current and target deployment mode
    • Preferred migration date
    • Any special requirements

  2. Eligibility Check

    • Account standing verified
    • Invoice status confirmed
    • Technical feasibility assessed

  3. Planning Call

    • Review migration scope
    • Confirm timeline
    • Discuss any custom requirements

Phase 2: Preparation (Days 8-21)​

  1. Environment Provisioning (if applicable)

    • New infrastructure set up
    • Configuration aligned with current setup
    • Testing environment available

  2. Data Export Preparation

    • Database export scheduled
    • File storage inventory completed
    • API configuration documented

  3. Integration Review

    • API endpoint changes documented
    • SDK configuration updates identified
    • DNS changes planned

Phase 3: Execution (Days 22-30)​

  1. Data Migration

    • Database migrated during maintenance window
    • File storage transferred
    • Verification checksums validated

  2. Cutover

    • DNS updated to new environment
    • Old API keys deprecated
    • New credentials activated

  3. Verification

    • All blocks functional
    • Data integrity confirmed
    • Performance baseline established

Phase 4: Completion (Days 31-60)​

  1. Monitoring Period

    • 30-day parallel access to old environment
    • Support for any issues
    • Performance optimization if needed

  2. Old Environment Decommissioned

    • After 30-day retention period
    • Or immediately upon your request
    • Data securely deleted

What You Receive​

When migrating, you receive a complete export of your data:

Database Export​

  • PostgreSQL dump format
  • All tables and relationships
  • Historical data included
  • Compatible with standard PostgreSQL tools

File Storage Export​

  • All uploaded files
  • Original filenames preserved
  • Directory structure maintained
  • S3-compatible format

Configuration Export​

  • Block configurations
  • API settings
  • Environment variables
  • Webhook configurations

Documentation Package​

  • Migration runbook
  • New environment credentials
  • Updated API endpoints
  • SDK configuration changes

Timeline by Migration Type​

MigrationTypical Timeline
Shared → Dedicated14-21 days
Shared → Self Managed7-14 days
Dedicated → Self Managed7-14 days
Self Managed → Dedicated14-21 days
Partner changesVaries by partner

Downtime Expectations​

Migration TypeExpected Downtime
Shared → Dedicated< 2 hours
Shared → Self Managed< 4 hours
Dedicated → Self Managed< 2 hours
Self Managed → Dedicated< 4 hours
Minimize Downtime

Schedule migrations during your lowest-traffic periods. We can coordinate timezone-appropriate maintenance windows.

Commercial Considerations​

Contract Changes​

When you migrate:

  • Current contract is amended (not terminated)
  • New deployment terms take effect
  • Pricing changes on migration completion date
  • No early termination fees for upgrades

Pricing Adjustments​

ScenarioBilling Change
Upgrade (Shared → Dedicated)New pricing starts on migration date
Downgrade (Dedicated → Shared)Pro-rated credit applied
Lateral (Partner → Self)License fee unchanged

Cancellation vs Migration​

If you're leaving 23blocks entirely:

  • Same 30-day notice requirement
  • Full data export provided
  • Data retained 30 days post-termination
  • Permanent deletion upon request

API Changes During Migration​

What Changes​

  • API base URL (for some migrations)
  • API keys (new credentials issued)
  • Rate limits (may differ between modes)

What Stays the Same​

  • API endpoints and schemas
  • SDK method signatures
  • Response formats
  • Authentication flow

Updating Your Application​

// Before: Shared Cloud
const client = new BlocksClient({
  baseUrl: 'https://api.23blocks.com/v1',
  apiKey: 'sk_live_old_key'
});

// After: Dedicated Cloud
const client = new BlocksClient({
  baseUrl: 'https://your-company.api.23blocks.com/v1',
  apiKey: 'sk_live_new_key'
});

Frequently Asked Questions​

Can I migrate with zero downtime?​

For critical applications, we can arrange blue-green deployment with DNS-based cutover, reducing downtime to seconds. Contact us to discuss.

What if I need to migrate urgently?​

Emergency migrations are available for critical situations. Standard requirements still apply, but timelines can be compressed with additional coordination.

Can I migrate just some blocks?​

Yes, partial migrations are supported. For example, migrate your Auth block to Dedicated while keeping other blocks on Shared.

What happens to my data if migration fails?​

Your original environment remains intact until successful migration is confirmed. We don't decommission anything until you verify the new setup works.

Is there a migration fee?​

No separate migration fee. You pay only for the new deployment mode.

Can I test before committing?​

Yes, we can provision a test environment on the target deployment mode before full migration.

Start Your Migration​

Ready to migrate? Here's how to begin:

Step 1: Plan Your Migration​

Review this guide and identify your target deployment mode.

Step 2: Check Requirements​

  • Account in good standing? ✅
  • Invoices paid? ✅
  • 30+ days until desired migration date? ✅

Step 3: Submit Request​

Email: migrations@23blocks.com

Include:

  • Current deployment mode
  • Target deployment mode
  • Preferred migration date
  • Any special requirements

Contact​

Migration Support

Billing Questions

Technical Questions