# Test importing codes from a password manager

[Read this guide on KeySigner](https://keysigner.io/integrations/guides/test-sign-in-code-import/)

Use a test account to check whether the KeySigner macOS authenticator can copy a time-based sign-in code from a 1Password 1PUX, KeePass XML or compatible KeePassXC XML export.

## Before you start

**KeySigner macOS build with password-manager import enabled**

- Use a local 1Password 8 1PUX export no larger than 16 MiB from a test vault.
- Use a local KeePass 2 XML export no larger than 16 MiB from a test database.
- Use a local KeePassXC 2.8.0 command-line XML export no larger than 16 MiB and choose KeePass XML in KeySigner.
- [Check the KeePassXC version](https://keysigner.io/integrations/setup-requirements/#check-versions-keepassxc)

## Data and access

- **Shared or checked**. KeySigner copies supported time-based code fields from the test export. The app you sign in to receives a generated code.
- **Check separately**. The source copy can still generate codes. The importer leaves passwords, passkeys and attachments in the source manager.

## 1. Prepare a test code

In 1Password 8, KeePass 2 or KeePassXC 2.8, save a time-based one-time password (TOTP) for a test account you control. Pick an account you can still access if the import fails.

**Check.** The source shows a current code for the chosen issuer and test account. The independent recovery option is available.

## 2. Export the test data

Export the test account or database to a private folder on your computer, outside any synced folder. The export can contain unencrypted passwords and codes.

**Check.** The temporary export exists in the private, unsynced location and uses the format you selected.

### Choose your export instructions

- **1Password 8 on Mac**. Open File → Export, select your test account, then choose 1PUX.
- **1Password 8 on Windows or Linux**. Open the three-dot menu at the top of the sidebar, select Export and your test account, then choose 1PUX.
- **KeePass 2**. Open File → Export and choose KeePass XML (2.x).
- **KeePassXC 2.8.0**. Use the command-line XML export with an ordinary time-based code.

## 3. Review and import one code

In KeySigner for Mac, open Accounts, choose Add (+), then Sign-in codes and backup. Unlock and choose Import from a password manager. Choose 1Password 1PUX or KeePass XML. Use KeePass XML for a KeePassXC export too. Select your file, review the test item, then choose Import this code.

**Check.** The review shows the expected test account. After import, the account appears in KeySigner’s sign-in code list.

## 4. Check the copy and clean up

Use the new KeySigner code on the test service while keeping the original code available. When the test is finished, remove the temporary export. Keep the source account until you have verified access.

**Check.** The service accepts a fresh KeySigner code and the original copy remains available. Remove the temporary export from the test computer.

## Check your result

The test service accepts a KeySigner code for the same account. KeySigner copies supported code fields and leaves the source copy available. Passwords, passkeys and attachments stay with the source password manager.

[How to verify your setup](https://keysigner.io/integrations/verify-a-setup/)

## If you get stuck

### The import option or test item is unavailable

Check that you’re using a KeySigner macOS build with Sign-in codes and backup available. Unlock the authenticator, check that the export is a local file no larger than 16 MiB, and confirm the source item has a time-based code. Use 1PUX or XML. For KeePassXC, Steam codes and older code field formats are outside this flow.

- [Choose a nonempty export no larger than 16 MiB.](https://keysigner.io/integrations/setup-messages/#export-file-size)
- [Could not use this export or review. Choose the matching format and review the file again.](https://keysigner.io/integrations/setup-messages/#export-review)
- [The reviewed data or your accounts changed. Review again.](https://keysigner.io/integrations/setup-messages/#review-changed)
- [This sign-in code is already in KeySigner. No second copy was added.](https://keysigner.io/integrations/setup-messages/#code-already-present)

## Tools in this guide

- [1Password](https://keysigner.io/integrations/1password/)
  - [Review account recovery options](https://support.1password.com/sign-in-troubleshooting/)
  - [Complete recovery for a team member](https://support.1password.com/recovery/)
  - [Setup requirements](https://keysigner.io/integrations/setup-requirements/#1password)
- [KeePass](https://keysigner.io/integrations/keepass/)
  - [Review database passwords and key files](https://keepass.info/help/base/keys.html)
  - [Setup requirements](https://keysigner.io/integrations/setup-requirements/#keepass)
- [KeePassXC](https://keysigner.io/integrations/keepassxc/)
  - [Check database unlock factors and recovery](https://keepassxc.org/docs/KeePassXC_UserGuide)
  - [Setup requirements](https://keysigner.io/integrations/setup-requirements/#keepassxc)

## Setup instructions

- [Export a test account from 1Password](https://support.1password.com/export/)
- [Copy codes from Google Authenticator](https://keysigner.io/integrations/guides/import-codes-from-google-authenticator/)
- [Review KeePass XML import and export](https://keepass.info/help/base/importexport.html)
- [Export test data from KeePassXC](https://keepassxc.org/docs/KeePassXC_UserGuide#_exporting_databases)

[More guides for this task](https://keysigner.io/integrations/tasks/import-sign-in-codes/)
