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

# How do I migrate away from Acrobits Cloud Softphone?

> Your SIP accounts, provisioning data, push certificates, and app store listings belong to you. Export your data, revoke build access, and publish a new binary. Plan for 6-8 weeks minimum.

Migrating away from Cloud Softphone takes 6–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. Here is exactly what that process looks like.

## What You Own, And What You Take With You

**SIP accounts belong to you.** Cloud Softphone never touches 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 were 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 Transfer

This is the part operators worry about most. Here is how it works:

Your **Cloud Softphone app is published under your own Apple Developer and Google Play accounts**. You own the listing, the reviews, the 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

There is no "transfer" needed because you already own it.

## 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) is standard and [works with any compliant client](/resources/knowledge-base/cloud-softphone-compatibility/).

## Timeline Expectations

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.

The operators who stay (and most do) stay because the platform works, not because leaving is hard.

Ready to evaluate what staying 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": "Your SIP accounts, provisioning data, push certificates, and app store listings belong to you. Export your data, revoke build access, and publish a new binary. Plan for 6-8 weeks minimum."
      }
    }
  ]
}