Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Migrating Aperture Library to Capture One catalog

Comments

33 comments

  • hifimacianer
    Hi Peter,

    would your tool also work with the new photos app, since the Library structure should be quite similar to Aperture?
    I like the new photos app in terms of speed and I'm also able to organize my pictures in a way I like.

    But it really lacks the editing features I need, so your solution would be also very welcome for my workflow.
    Would it be a big effort for you to adopt your scripts to work with the new photos app?

    Björn
    0
  • NN635770922769309595UL
    I have just "completed" the shift ("completed" because as another post mentions, I took the opportunity to do some housekeeping, and only moved the current Aperture library; the older ones are safely stored away for whenever).

    The library is a managed one, and makes / made extensive use of Folders and Albums. I first tried C1 back in April with what was then version 7 Pro, and gave up because of the problems mentioned in this thread. However, I recently found out about Aperture Exporter () which worked a treat, preserving the folder/album structure. And version 8 was well nigh irresistible.

    AE does have a known crash bug but I treated each Folder + its associated albums separately and all was well. I chose to go the Catalog / User collection / Group / Album route in C1, importing each Aperture Album from where I had AE park it.

    Bit of a lengthy job, but am highly delighted with the outcome.
    0
  • leanhnam220
    Thanks for giving me interesting information
    0

Post is closed for comments.