---
title: "How do I migrate away from Acrobits Cloud Softphone?"
topic: "White-Label / Wholesale"
updated: 2026-07-09
canonical: https://acrobits.net/resources/knowledge-base/migrate-away-from-acrobits/
summary: "Migrating away from Cloud Softphone takes 6 to 8 weeks. Your SIP accounts, provisioning data, push certificates, and app store listings belong to you: you export your data, revoke Acrobits' build access, and publish a new binary."
---

# How do I migrate away from Acrobits Cloud Softphone?

> Migrating away from Cloud Softphone takes 6 to 8 weeks. Your SIP accounts, provisioning data, push certificates, and app store listings belong to you: you export your data, revoke Acrobits' build access, and publish a new binary.

Migrating away from Cloud Softphone takes 6 to 8 weeks. Your [SIP](/voip-glossary/sip/) accounts, provisioning data, push certificates, and app store listings belong to you: you export your data, revoke Acrobits' build access, and publish a new binary.

## what you own and what you take with you

**Your SIP accounts belong to you.** Cloud Softphone does not change your SIP infrastructure. Your subscriber credentials, registrar settings, and call routing live on your switch or hosted PBX. Nothing changes on the server side when you stop using our platform.

**Provisioning data is exportable.** Your subscriber configurations (account mappings, feature flags, branding settings) can be exported from the Cloud Softphone admin portal. You receive structured data you can feed into a replacement provisioning system.

**Push certificates are yours.** The FCM and APNs credentials tied to your app store listing are typically created under your developer accounts. You retain full control of these regardless of your relationship with Acrobits.

**Call history and analytics** generated during your time on the platform can be exported before deactivation. We provide a reasonable window to pull this data after contract end.

## app store listing ownership

Your **Cloud Softphone app is published under your own Apple Developer and Google Play accounts**, so you keep control of the listing, reviews, and install base. Acrobits has build-and-publish access, not ownership.

When you migrate away:

  - You revoke Acrobits' build access from your developer accounts

  - You publish a new binary from your replacement platform

  - Your subscribers receive the update through the normal app store flow

  - Your install base, ratings, and reviews stay intact

No transfer is needed because you already own the listing.

## provisioning data portability

Cloud Softphone's provisioning system stores configuration per subscriber: SIP credentials, codec preferences, feature toggles, UI settings. This data exports as structured JSON or XML.

What you will need to rebuild on your new platform:

  - **SIP account mappings** (which subscriber gets which SIP credentials)

  - **Feature configurations** (call recording, push settings, codec priorities)

  - **Branding assets** (logos, color schemes, splash screens)

The SIP-level configuration (server addresses, ports, transport settings) follows standard SIP settings and [should work with compliant clients](/resources/knowledge-base/cloud-softphone-compatibility/).

## migration timeline

A realistic migration timeline:

  - **Week 1-2:** Export provisioning data, evaluate replacement platform

  - **Week 3-4:** Configure new platform, test with internal accounts

  - **Week 5-6:** Staged rollout to subscriber segments

  - **Week 7-8:** Full cutover, revoke Acrobits access

Plan for **6-8 weeks** minimum. Rushing the push notification migration is the most common mistake. Subscribers who lose reliable incoming calls will flood your support queue.

## why we publish this

Vendor lock-in is a real concern for operators evaluating any platform. We would rather you choose Cloud Softphone knowing you can leave than discover migration friction after signing.

Many operators stay because the platform works, rather than because leaving is difficult.

See what staying on the platform looks like: [Explore Cloud Softphone](/cloud-softphone/).

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How do I migrate away from Acrobits Cloud Softphone?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Migrating away from Cloud Softphone takes 6 to 8 weeks. Your SIP accounts, provisioning data, push certificates, and app store listings belong to you: you export your data, revoke Acrobits' build access, and publish a new binary."
      }
    }
  ]
}