Convert NBU to VCF

A new phone, contacts application, or mail client may require contacts in VCF format, while an older Nokia phone may have them stored inside an NBU backup. The conversion extracts contact records from that backup; renaming .nbu to .vcf cannot work.

What the NBU format is

NBU is the backup-container format used by Nokia PC Suite for many Nokia and Symbian phones. A backup can contain contacts, messages, calendar entries, notes, settings, and media, so an NBU file is not itself an address book and cannot normally be imported into a contacts application.

NBU files may be tied to a particular Nokia PC Suite generation, phone model, or backup password. The exact contents depend on what was selected when the backup was created.

What the VCF format is

VCF, also called vCard, stores contact records in a text-based interchange format. Android, iOS through compatible import routes, Outlook, Thunderbird, macOS Contacts, Windows Contacts, and webmail services can import VCF files. One VCF file can contain one contact or multiple BEGIN:VCARD and END:VCARD blocks.

Depending on the source and exporter, VCF can preserve names, telephone numbers, email addresses, postal addresses, organizations, notes, birthdays, and photos. Older software usually handles vCard 2.1 or 3.0 more reliably than vCard 4.0.

Convert with NBU Explorer on Windows

1. Make a working copy of the original backup.nbu file. Keep the original unchanged until every imported contact has been checked.
2. Obtain NBU Explorer from its project source or a reputable software archive. It is an older Windows utility, so verify the download and scan it before running it; do not install an unrelated program that merely claims to convert NBU files.
3. Open NBU Explorer and use File → Open to select the copied NBU file. If the backup is password-protected, damaged, or created by an unsupported PC Suite version, the utility may fail to parse it.
4. Expand the backup tree and select Contacts. Select individual records or the complete contact set.
5. Use the available export, save, or context-menu command and select vCard or VCF. Interface labels differ between NBU Explorer releases. Save the result as contacts.vcf.
6. Open the output in a plain-text editor and check for BEGIN:VCARD, VERSION:, and END:VCARD. Count the vCard blocks if several contacts were selected.

NBU Explorer releases and download locations vary, and some versions expose contact extraction without supporting every NBU variant. If the Contacts branch is missing or empty, try a different compatible release rather than changing the file extension.

Use Nokia PC Suite when direct extraction fails

If the backup was made with Nokia PC Suite and a compatible phone is still available, install the same or a compatible PC Suite version, connect the phone with its required drivers, and restore contacts only. Export the restored contacts from the phone, Outlook, or another synchronization target using that program's Export → vCard/VCF command. This is a recovery route, not a direct NBU-to-VCF conversion, and it requires working legacy hardware and software.

Online converters and privacy

There is no broadly established online service that reliably parses Nokia PC Suite NBU backups and exports their contacts. Generic file-conversion sites generally do not support this container, and uploading an NBU file can expose contacts, messages, and other private data. Use a local extractor; an online service is appropriate only if its documentation explicitly lists NBU contact extraction, its privacy terms are acceptable, and the backup contains no confidential data.

Check the imported contacts

• VCF carries contacts only; messages, calendars, notes, settings, and media require separate recovery or export methods.
• Inspect multiple phone numbers, custom number labels, groups, birthdays, notes, photos, and postal addresses because older Nokia fields may not map exactly to modern vCard fields.
• Check accented and non-Latin names after opening the VCF in the destination application. Old exporters may write character data with encoding that newer applications interpret incorrectly.
• Confirm that the destination supports the exported vCard version. If import fails, export as vCard 2.1 or 3.0 when the software provides that choice.
• Remove or merge duplicates before importing if the destination address book already contains some of the same records.