Jump to content
Enpass Discussion Forum

Impossible to import from 1password


ChrisElden

Recommended Posts

Hello there,

I checked the other topics about this problem but it doesn't helped.

I stritcly followed you instruction but at the very end enpass say : no PIF file present in the selected directory.

Of course the 1pif file is inside this directory (i tryed to put in on the desktop and on a directory on the desktop)

i use 1password version 7.7 and enpass version 6.6.3

Thanx for any help

Link to comment
Share on other sites

I have _exactly_ the same issue here. Enpass just does not see the 1pif file as a valid file. 

Also: if you choose CSV as import, the 1pif-File is also available. You may choose it. But it won't import. 

If I put the 1pif in a directory by itself and choose the Dir for import - enpass shows, that there is no 1pif in the directory.

Language of my 1Password is German.

Edited by Zagdul
Link to comment
Share on other sites

On 8/13/2021 at 1:48 PM, Gulshan Dogra said:

Hi @ChrisElden, @Zagdul

Welcome to the Enpass Community.

Please share the following details so that we can assist you better.

  • Operating System 
  • 1Password Language
  • 1Password version
  • Enpass version

Thank you.

Operating System: macOs Big Sur 11.5.1

1password language: German

1Password Version : 7.8.7

Enpass Version 6.6.3

Link to comment
Share on other sites

On 8/13/2021 at 5:31 PM, ChrisElden said:

sorry i  bought SECRETS who is cheaper and works 100% with importing 1P and attached files.

I think Zagdul will help to solve the situation

I have secrets also, the import worked a lot better, I agree. But secrets also lacks some features. I'd like to give enpass a try

 

Link to comment
Share on other sites

Dredging up this old topic. I installed Enpass 6.6.3 (840) from the Mac App Store today. Imported from 1Password7 and all of my items in Enpass show the import time and date as both the Created and Modified dates. I looked in the .1pif data and all of the dates in there are correct (not reset to today).

I am trialing Enpass as a possible paid family user to replace 1Password when it goes to version 8. While Enpass doesn't have all of the features, it has enough for me to move. Except I won't move if I lose all of the created and modified times. 

Link to comment
Share on other sites

1 hour ago, Bill Plein said:

Dredging up this old topic. I installed Enpass 6.6.3 (840) from the Mac App Store today. Imported from 1Password7 and all of my items in Enpass show the import time and date as both the Created and Modified dates. I looked in the .1pif data and all of the dates in there are correct (not reset to today).

I am trialing Enpass as a possible paid family user to replace 1Password when it goes to version 8. While Enpass doesn't have all of the features, it has enough for me to move. Except I won't move if I lose all of the created and modified times. 

I have the same situation here, nice to see people think alike :D

But for whatever reason, I cannot import from 1password7 - what directory did you choose? Enpass wants to have a directory, when I choose the dir, where the 1pif file (actually it's a directory with a flag) is located, I always get "nothing to import".

I also tried to change the 1pif-Directory, so that I could use it in the file chooser. No effect neither.

Link to comment
Share on other sites

Allow me to suggest a work-around that will let you get up and running immediately.

I also just recently switched from 1Password to Enpass and had this exact problem, but I found an easy work-around that doesn't require anything more than a 1PF and Enpass and access to the Finder.

  1. Save the content to import from 1Password as a 1PF file and make note of the location in the Finder.
  2. Create a new empty folder somewhere on your Mac. Call it whatever you want. This is where the files to import into Enpass will go.
  3. Keep the folder you just created open in a separate window or tab and in a different window navigate to the 1PF file in the Finder.
  4. Right click on the 1PF file and select "Show Package Contents".  This will open the 1PF file (which is really just a special kind of folder).
  5. Do a "Select All" of the files and folders you see in this package content window (⌘A).
  6. Drag and drop the content you just selected into the folder you just created in Step 2
  7. Fire up Enpass and start the import process. Select 1Password and the 1PF file format as the import options.
  8. When you are asked to select the folder in which the 1PF file exists, instead select the folder that you created in Step 2 above.
  9. Enpass will now find the content to import from 1Password and import all of it. 

I did these steps myself and I was able to import everything.

I'm not sure why Enpass doesn't see or work with the actual packaged 1PF file, but I suspect it might be because very early versions of 1Password a long time ago used to export content into a folder instead of a packaged 1PF file?

In any case, until Enpass fixes this, the steps listed above will let you get to work with Enpass.

  • Like 1
Link to comment
Share on other sites

@Gulshan Dogra, 1Password does not export items in 1PF format loose in a folder like you show it (not any more). The Mac will have a single file. Enpass does not recognize this .1pf file by default (although it absolutely should).

You can follow my directions above to manually pull out the data Enpass can import, but ideally Enpass should recognize a .1pf file and import it.

Link to comment
Share on other sites

On 8/17/2021 at 2:28 PM, Discordant said:

Allow me to suggest a work-around that will let you get up and running immediately.

I also just recently switched from 1Password to Enpass and had this exact problem, but I found an easy work-around that doesn't require anything more than a 1PF and Enpass and access to the Finder.

  1. Save the content to import from 1Password as a 1PF file and make note of the location in the Finder.
  2. Create a new empty folder somewhere on your Mac. Call it whatever you want. This is where the files to import into Enpass will go.
  3. Keep the folder you just created open in a separate window or tab and in a different window navigate to the 1PF file in the Finder.
  4. Right click on the 1PF file and select "Show Package Contents".  This will open the 1PF file (which is really just a special kind of folder).
  5. Do a "Select All" of the files and folders you see in this package content window (⌘A).
  6. Drag and drop the content you just selected into the folder you just created in Step 2
  7. Fire up Enpass and start the import process. Select 1Password and the 1PF file format as the import options.
  8. When you are asked to select the folder in which the 1PF file exists, instead select the folder that you created in Step 2 above.
  9. Enpass will now find the content to import from 1Password and import all of it. 

I did these steps myself and I was able to import everything.

I'm not sure why Enpass doesn't see or work with the actual packaged 1PF file, but I suspect it might be because very early versions of 1Password a long time ago used to export content into a folder instead of a packaged 1PF file?

In any case, until Enpass fixes this, the steps listed above will let you get to work with Enpass.

unfortunately, this did not help either. Enpass states "nothing to import" :$

Link to comment
Share on other sites

52 minutes ago, Zagdul said:

unfortunately, this did not help either. Enpass states "nothing to import" :$

I've done this on 3 different machines, so I can confirm it works if you follow the exact directions I posted (assuming you are using a recent version of 1Password and Enpass). Did you check your export from 1Password to make sure it actually contains anything? If you're sure there is data that was successfully exported, make sure you're pulling out everything inside the .1pf file, this will typically include a data file and 2 folders (though this will vary depending on what you actually exported).

The  folder you point Enpass at needs to have a data.1pif file and perhaps also folders for certain types of other things you exported. See the attached screenshot as an example. This is all inside a folder I happened to call "Export" and I pointed Enpass at the "Export" folder and told it to import 1pf from 1Password.

871831437_ScreenShot2021-08-19at12_08_10PM.png.6a26f7011acdfc0bde2c7b4f3073450d.png

Edited by Discordant
  • Thanks 1
Link to comment
Share on other sites

14 hours ago, Discordant said:

I've done this on 3 different machines, so I can confirm it works if you follow the exact directions I posted (assuming you are using a recent version of 1Password and Enpass). Did you check your export from 1Password to make sure it actually contains anything? If you're sure there is data that was successfully exported, make sure you're pulling out everything inside the .1pf file, this will typically include a data file and 2 folders (though this will vary depending on what you actually exported).

yes, that is all correct, and it looks like this exactly here. Thanks for the screenshot, that is exactly what I see in the 1pif "directory". I actually also tried copying the content via shell so that I won't miss any hidden files - there weren't any.

But it does not work here anyway. Maybe it is related to the language - my Mac runs in German. I was trying to change the language in 1Password, just to try, but there is no such setting. I'd have to change the whole OS to try that.

I was just taking a look at the data.1pif file inside the export.1pif (confusing suffixes) - it is not language specific. Each entry has a defined structure and key-names are english. So it should work. Could it be there is a problem with Umlauts then?

This is really annoying. I was importing data using CSV, but that lacks some info and of course all attachments.

 

Edited by Zagdul
Link to comment
Share on other sites

That's wild. Perhaps it does have something to do with the language, but I also wonder if there is something different about your 1PF file somehow. What version of 1Password are you using to export? Also, you might want to try just exporting a few items (instead of everything) and see if that works. If it does, perhaps there is something in the export that Enpass doesn't like, like a weirdly encoded item?

There's also another possibility. Try importing the 1PF file into something else that Enpass supports like KeePass XC or something like that. Then try exporting from the other program and see if Enpass likes that.

 

Link to comment
Share on other sites

KeePass XC does also not import that file, I can only choose a vault, it would not take the 1pif file as an option.

But you were right, when only exporting a couple of passwords, it worked...

Thanks for the Idea, it is most definitely related to the content itself... I will play with that a bit and keep you posted here!

Link to comment
Share on other sites

This was weird... I could import all Data from 1Password, just one category after the other. Still, needed to copy the content of the 1pif dir to some other dir in order to make enpass actually find anything.

But it seems it is not related with the content itself. The Number of Passwords should also not be the issue (~ 900 entries including licenses etc). 

Well, it seems, I was able to migrate anyway. Thanks for the help!

Edited by Zagdul
Link to comment
Share on other sites

  • 1 month later...

Importing from 1Password  1pif folder - out of 2,532 items (+72 in archive), enpass only imported 1,609 entries. The import skipped 923 1P accounts. It's possible there's an entry in 1P that causes enpass to fail reading the remainder of the file. Is there an import log to see where it hung/stopped so I can identify the 1P entry that is causing the enpass bug?

I verified the data.1pif file created by 1P does  has 2,593 "uuid" entries, so the issue is with Enpass' import process.

Running 1Password v7.8.7 with local (non-cloud) password vault on Mac OS Catalina 10.15.7. Enpass v6.7.2

Link to comment
Share on other sites

I just tried the app store 6.7.3 version, but it still stops after importing 1609 entries.

FYI I usually purchase apps directly from the developer's website as (1) the app store version sometimes have limitations imposed by Apple, and (2) so the developers get the full sale amount without having to loose Apple's commission.

  • Thanks 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...