How to Transfer SMS and Call Logs Between Android Phones Without Using Google Backup

When you switch to a new Android phone, the built‑in Google backup often skips SMS and call‑log data, or you may simply prefer to keep those records out of the cloud. This tutorial shows you how to move both SMS messages and call logs safely, using only free apps and ADB when needed, without rooting either device.

Before you start

• Charge both devices or keep them plugged in.
• Enable Developer options on both phones if you plan to use ADB (Settings > About phone > Tap “Build number” seven times).
• Install the free app SMS Backup & Restore on both phones. The app works on Android 5.0+ and does not require root.

Overview of the workflow

1. Create a combined SMS + call‑log backup on the old phone.
2. Copy the backup file to the new phone (via USB, Wi‑Fi Direct, or cloud).
3. Import the backup on the new phone.
4. Verify that messages and call entries appear correctly.

Each step is broken down below with the exact menu paths you’ll see on most stock Android skins. Minor wording differences may appear on Samsung, Xiaomi, or OnePlus devices, but the overall flow stays the same.

Step 1 – Create a backup on the source phone

Step 2 – Transfer the backup file to the new phone

You have three reliable ways to move the file. Choose the one that matches the devices you have on hand.

Option A – Direct USB transfer (recommended for speed)

1. Connect the old phone to a PC via USB.
2. On the phone, select File transfer (or “MTP”).
3. Navigate to the backup folder (e.g., SMSBackupRestore) and copy the XML file to a temporary folder on the PC.
4. Disconnect the old phone and connect the new phone.
5. Select File transfer again and paste the XML file into the same SMSBackupRestore folder on the new device. If the folder does not exist, create it.

Option B – Wi‑Fi Direct (no PC needed)

1. Open Settings > Connections > Wi‑Fi Direct on both phones.
2. Tap the device name on the source phone to request a connection; accept on the target phone.
3. On the source phone, open the file manager, locate the XML backup, and use the share icon → Wi‑Fi Direct to send it.
4. The target phone will prompt you to accept the file; save it in /sdcard/SMSBackupRestore/.

Option C – Cloud or email (useful if you lack cables)

1. From the source phone, open the backup folder in a file manager.
2. Share the XML file via Gmail, Drive, or any cloud storage you trust.
3. On the new phone, download the file and move it to /sdcard/SMSBackupRestore/ using the file manager.

Step 3 – Import the backup on the destination phone

Step 4 – Verify the migration

1. Open the native Messages app. Scroll to the oldest conversation; you should see messages that date back to before the transfer.
2. Open the Phone app → Recents. Verify that older call entries are present.
3. If any entries are missing, return to the backup file and repeat the restore step. Occasionally, duplicate entries appear; you can clean them with the app’s “Delete duplicate messages” option under Settings > Advanced.

Troubleshooting

Backup file not recognized

• Ensure the file extension is .xml. Some file managers rename it to .txt during transfer.
• Check that the XML file is not corrupted. Open it in a text editor; the first line should read <?xml version="1.0" encoding="UTF-8"?>.
• If the file is zero‑bytes, repeat the backup step; the original phone may have run out of storage during creation.

Restore fails with “Permission denied”

• On Android 10+ the app may need the Manage external storage permission. Go to Settings > Apps > SMS Backup & Restore > Permissions and enable it.
• Restart the app after granting the permission.

Duplicate or out‑of‑order messages

• Duplicate entries happen when you restore the same backup twice. Use the app’s built‑in duplicate‑removal tool (Settings > Advanced > Delete duplicate messages).
• Message order is controlled by timestamps stored in the XML. If you notice gaps, it usually means the source phone’s clock was incorrect at the time of backup. Adjust the source phone’s date/time and create a fresh backup.

Alternative method: ADB‑only backup (for power users)

If you prefer not to install a third‑party app, you can use ADB to pull the SMS and call‑log databases directly. This method works on any Android version but requires a computer and a USB cable.

1. Enable USB debugging on both phones (Settings > Developer options > USB debugging).
2. Connect the source phone to the PC and run:

   adb backup -f smscall.ab -noapk -nosystem -shared com.android.providers.telephony

   This creates a full backup file named smscall.ab.
3. Transfer smscall.ab to the new phone (any of the methods described in Step 2).
4. On the new phone, connect to the PC and run:

   adb restore smscall.ab

   Accept the restore prompt on the device.

After the restore, open Messages and Phone apps to confirm the data is present. This approach bypasses the XML conversion step, but the backup file is not human‑readable and cannot be edited.

Safety and privacy considerations

• Never store the backup file on a shared or public computer after the transfer is complete. Delete it securely (use a file‑shredder app) if you no longer need it.
• If you plan to sell or recycle the old phone, perform a factory reset after confirming the new phone has all messages and logs.
• When using cloud storage, enable two‑factor authentication on the account to protect the backup file.

Wrap‑up

By following the steps above you can move your entire SMS history and call‑log records from any Android phone to another without relying on Google’s backup service. The process uses a free, open‑source app that works on virtually every Android version, and it gives you full control over where the data lives during the transfer. Keep the backup file safe, verify the restore, and you’ll have a seamless migration experience.