Viber transfer to iOS: Migravi FAQ

Migravi is an independent iPhone app that imports supported Viber ZIP and CSV text exports into a separate archive. Read old conversations, search messages and organize your archive offline. It is developed and published by REPARIS d.o.o.

No. Migravi imports exported text history into Migravi, not into the official Viber application. It does not sign into your Viber account, modify Viber or restore a Viber cloud backup. Keep using Viber separately for live conversations.

The supplied Migravi 2.0 build targets iPhone running iOS 17 or later. iPad support is not part of this version. Check the final App Store listing for the requirements of the version you install.

No Migravi account is required to browse your archive. After import, reading and searching work offline. Getting the app or downloading an export from a cloud provider may require internet access; these are separate from offline archive browsing.

No. You must obtain a compatible text export first. Available export options depend on your Viber version. Use Settings → How to import chats? in Migravi for the available import instructions. A Google Drive or iCloud Viber backup is not a ZIP/CSV text export that Migravi can restore.

No official Viber affiliation is implied. Migravi is an independent product of REPARIS d.o.o. References to Viber, iPhone and iOS explain compatible source files and devices; they do not imply endorsement.

1. Save a supported export somewhere accessible in Files on your iPhone.
2. Open Migravi → Settings → Import chats.
3. Select one ZIP on its own, or select one or several CSV files.
4. If a ZIP presents a conversation picker, select the chats you want.
5. Review the proposed own numbers carefully and confirm only numbers that belong to you.
6. Keep Migravi open until import completes. Check Import History and the resulting Chat and Groups lists.

Multiple CSV selection is supported. Select a ZIP alone; do not combine several ZIP files or mix a ZIP with CSV files in one selection. Import other ZIP exports separately.

The direct ZIP flow includes a conversation selection screen. Select or deselect conversations before confirming import. Cancelling before import does not add the unselected conversations to your archive.

No. Migravi accepts supported exported text chat files, not Viber’s Google Drive or iCloud backup format. Renaming a backup to .zip or .csv does not make it compatible.

Confirm that it is a compatible Viber export rather than an unrelated CSV or backup. If stored in cloud storage, download it fully in Files and try again. Check available iPhone storage and read the error and Import History entry. If several CSV files were selected, test one original file to identify the failing source. Preserve the original export; do not edit dates or columns blindly.

The Viber text exports supported by Migravi do not include the original photos and videos or usable file references needed to retrieve and match them to messages. Migravi can display media placeholders, but it cannot recover the original files from these exports.

For security reasons, Migravi does not support methods that require rooting your Android device or bypassing its protections. We will not add support for these methods.

They represent media references recorded in the text export. They are not downloadable attachments inside Migravi. Their wording may depend on the app language or source export. A placeholder does not mean that the original photo, GIF or video was imported.

Yes. Migravi recognizes previously imported records and merges compatible newer or older exports. Re-importing is intended to avoid adding the same exported messages again. If nothing new is present, the archive may remain unchanged; consult Import History rather than expecting a new conversation every time.

Repeated text can represent real messages. The import logic accounts for repeated records rather than treating every matching text as one message. Legitimate repeated records, including repeated photo placeholders at the same timestamp, are intended to be preserved. Do not delete repeated entries solely because their wording is identical.

Messages are ordered chronologically, with sequence used to keep records in order when timestamps match. Compatible older and newer exports are merged into that chronology. Conversation lists use their latest message information, rather than placing every import at today’s date. Migravi depends on dates supplied by the export; it cannot reconstruct dates absent from the source.

Your confirmed number identifies outgoing messages and helps distinguish private chats from groups. Labels such as Me, Ja or Ich can suggest a candidate, but a suggestion is not treated as your identity until you confirm it. Select only numbers you genuinely used for the exported conversations.

Without your correct confirmed number, your own messages can be counted as incoming messages from another participant. This can make some private conversations look like groups. It does not necessarily affect every chat: export names and participant information also influence classification. Confirming the correct identity and importing again can repair existing conversations.

1. Open Settings → the phone-number section.
2. Choose the reset/forget-number option (the label may be Reset my numbers or Forget Number, depending on language/version).
3. Confirm the reset. This forgets both accepted and rejected number choices; it does not delete chats.
4. Import the same export again.
5. Confirm your correct number when asked, then let the import complete.
6. Check Chat and Groups again. Migravi reassesses existing messages and conversation classification.

You do not need to delete the archive first. If the export has insufficient participant data, classification may still require further investigation.

No. Resetting number choices removes remembered confirmed and rejected numbers. Existing chats stay as they are until a subsequent import with a confirmed identity refreshes the archive. Once you confirm a different set of own numbers, that refresh can also change ownership and classification of existing chats; the reset is not a switch affecting only new files.

1. Import the first device’s export and confirm its own number.
2. Keep that number confirmed; do not reset it simply to add the second device.
3. Import the second device’s export and confirm its own number if offered. Migravi can retain additional confirmed own numbers.
4. If no new number is offered, add your second number under Settings → Enter number manually, then import the second export.
5. Check the number section for the main and additional confirmed numbers and verify both archives.

Both numbers must belong to you. Existing chats remain stored, but the importer may refresh their ownership/classification using the full confirmed-number set. Files representing the same conversation can merge rather than form two independent account archives.

Resetting removes the first number from confirmed identities. Add both of your own numbers again using Settings → Enter number manually, then re-import the relevant exports and allow the refresh to finish. Keeping only the second number can cause messages sent from the first number to be treated as incoming in existing chats. Do not erase conversations to resolve this.

Build 68 uses one archive and one set of confirmed own numbers, not independent account profiles. Compatible conversations may merge. If you require a hard boundary between accounts or two entirely separate identities, do not assume adding a second number provides that boundary.

Yes. In Settings, use Enter number manually and include the country calling code, for example +385 followed by your number. Save only a number that belongs to you. If validation fails, check the international format. Re-import after adding the number so the archive can refresh its message ownership and classification.

Migravi remembers both confirmed and rejected candidates. A previously answered number is not normally proposed on every import. If you rejected your own number by mistake, reset the remembered choices and import again, or add the correct number manually. After a reset, re-establish all your own numbers if you use more than one.

Messages from that number may be marked as yours and conversation classification can be wrong. Reset the number choices, then confirm or manually add only your own numbers and re-import. Confirming a contact merely because their name resembles Me or Ja is not enough; check the actual number.

Long conversations load in pages to keep browsing responsive. The initial window is not the full archive. Scroll toward older messages to load earlier pages, or use the date-jump action to reach an older date. A 200-message window does not mean the rest of the import was discarded.

Open the chat and use its search action. Enter at least two characters. Matches are highlighted, and previous/next controls move between results with a current/total indicator. The chat remains a conversation view rather than a list containing only matching messages. Close search to return to normal browsing.

Yes. Build 68 includes archive-wide search in Explore (Istraži). Enter at least two characters; results show the conversation and an excerpt. Open a result to jump into its chat. This differs from search within one open conversation.

Build 68 limits archive-wide search to the 300 newest matching results and in-chat search to about 1,000 matching messages. Narrow the phrase if a limit indicator appears. Search targets text messages, so generated photo/GIF placeholders are not searched like ordinary text. Deleted or trashed content is not part of normal search.

Use the jump-to-date action in the conversation menu and choose a date in the available archive range. Migravi loads a window around that position instead of first loading every message between today and that date. A date with no messages does not create missing history.

It surfaces conversations with messages on today’s calendar date in earlier years. Opening an item takes you to the relevant chat position. It is a browsing aid, not a complete statistical report: very busy dates can be limited by the amount loaded for the feature.

Star a message from its actions, or use available selection actions for several messages. Explore shows starred messages and lets you open their conversation. Removing a star changes the favorite state; it does not delete the message.

The conversation provides copy/share actions and selection tools for multiple messages. A copy places text on the clipboard; sharing sends selected content to the app or recipient you choose. These are user-directed exports, separate from Migravi uploading your archive. Check the selected messages and destination before sharing private information.

You can rename contacts/groups locally and choose an avatar from Photos using the conversation actions. These changes affect Migravi, not the contact’s Viber account. Custom names and avatars are kept when compatible histories are re-imported. Settings offers light, dark and system appearance. Photo access is needed when selecting an avatar.

Yes. Import runs while the app is open. Do not force-close Migravi or rely on background execution to finish it. With the import screen behavior enabled, the display dims after 30 seconds without touch. Keep-screen-on behavior is available under Settings → During import.

Reopen Migravi. When an interrupted import is detected, choose Continue import to resume from saved progress, or Discard remainder if you no longer want to finish. Some messages may already have been committed before interruption. Preserve the source export until you verify the outcome.

No. It stops the remaining portion rather than undoing all saved messages. Import History should record a Partial result and the available saved counts, with a note that the remaining portion was discarded. If you want the remaining messages later, import the original export again and verify the merge.

Large exports require parsing, duplicate checks and saving many messages. Progress and automatic dimming are expected; dimming does not mean the import stopped. Keep the app open, ensure sufficient storage and let it finish. If iOS terminates the app, reopen it and check for a resume prompt rather than deleting the archive.

Open Settings → Import History. Entries include date/time, processed files, new or updated chats, added messages, skipped duplicates and status where available. Successful, Partial and Failed describe the result. A progress percentage is not an exact message count, and the log is not a copy of message contents.

Check Chat, Groups and Import History first: the import may have completed, or no resumable pending state may remain. If the export is incomplete in the archive, re-import the original file and let duplicate handling merge it. If the failure repeats, retain the error details and app version for support; do not choose Delete all data as a first troubleshooting step.

Normal deletion moves the item to Trash. It disappears from normal browsing but remains stored until restored or permanently deleted. Open Settings → Trash to review deleted chats, groups and individual messages. Read the confirmation before choosing permanent deletion.

Open Settings → Trash. Swipe right to restore and swipe left to request permanent deletion; selection controls may also be available. Restored messages return to their original conversation position. If the whole conversation is still in Trash, restore it as well to browse it normally.

No. Re-importing the same history is intended to keep a trashed message in Trash, not make it visible again. Restore it explicitly from Trash if you want it back in normal browsing.

Not during ordinary re-import into the same retained conversation. Migravi remembers individual-message deletion so it does not reappear from that source. Permanent deletion cannot be undone from Trash. Deleting/recreating the entire conversation or clearing the whole archive changes that context; do not use those actions expecting individual deletion choices to carry over.

The whole conversation can be recreated from the export. This differs from permanently deleting an individual message while retaining the chat. A recreated conversation is not a restoration of all local customizations or deletion choices. Keep the original export if you may want the conversation again.

It resets the app by permanently removing the archive, messages, Trash and settings, including number choices. The action cannot be undone within Migravi. It is different from Forget Number. Rebuilding an archive requires your original supported exports. Copies in existing device backups or external storage are not automatically removed by this app action.

Migravi does not upload imported chat contents to Migravi servers or a Migravi cloud service. The archive is stored locally on your iPhone. User-selected sharing, cloud transfer of exports and device backups are separate operations.

Yes. Device backups such as iCloud Backup may include app data according to your device and backup settings. Local app storage does not mean data can never be in the cloud. Manage backup inclusion separately in your device settings. Read Apple’s explanation of iCloud Backup.

Yes. Importing a file does not automatically delete the source copy from iCloud Drive, another provider, email or the old device. Manage those copies separately if you no longer need them. Consider whether deleting the only export would leave you unable to rebuild the archive.

Migravi 2.0 does not include an in-app archive backup/restore feature. Device-level backups are a separate system and are not a guaranteed substitute for keeping the original export. Do not assume installing Migravi on a new iPhone will automatically sync your archive.

Enable App Lock in Settings to require the device’s supported authentication, such as Face ID or passcode, when opening the app and returning from the background. The app switcher preview hides messages. If no supported authentication is configured, set it up in iOS first. App Lock is not a promise of a separately encrypted export, and it does not control external copies or backups.

Deleting the app can remove its local archive. Build 68 does not offer Migravi account sync or an in-app archive restore tool. Retain your supported exports before uninstalling or changing devices. Whether device-level restoration recovers app data depends on the backup and restore process; Migravi cannot promise recovery of data it no longer has.

Provide your Migravi version/build, iPhone model, iOS version, file type, approximate size, the exact error and the steps that caused it. Include the relevant Import History counts if useful. For number/classification issues, describe whether a number was confirmed, rejected or reset. Avoid sending entire private chats or unredacted phone numbers unless genuinely needed and you agree to share them. This version does not promise an automatic support-log attachment tool.

The current website describes Migravi as coming soon to the App Store. Availability, price and purchase terms must be taken from the published listing when it launches. Purchase limits and StoreKit monetization are planned rather than implemented in the reviewed build; do not treat an earlier proposed price or free limit as a current offer.