Q: Question about Aperture Library after it has been migrated to Photos
After an Aperture library has been migrated to Photos, its extension becomes “.migratedaplibrary”
Anyone know what effect, if any, this extension change has on using Aperture?
As far as I can see the library can continue to be used as before, although edits are not reflected in the Photos library of course.
I have a hunch it might prevent that library being migrated to Photos again, but I can imagine I might want to migrate again if I wanted to trash the original Photos library and start over, or if I had added significant number of photos to Aperture since the original migration.
Thanks
MacBook Pro with Retina display, OS X El Capitan (10.11.4), null
Posted on May 28, 2016 12:31 PM
I have a hunch it might prevent that library being migrated to Photos again, but I can imagine I might want to migrate again if I wanted to trash the original Photos library and start over, or if I had added significant number of photos to Aperture since the original migration.
That is right. The extension indicates that the library has been migrated. There is no other difference.
Photos will not migrate the library again with that extension. I simply change the extension back to .aplibrary after migrating an Aperture library. Then Photos can migrate it again , if need be, and I can use it in Aperture again.
BTW, the migrated Aperture Library and the new Photos library are sharing the storage, but not the image files, the photos are stored very efficiently by hard links. See: Photos saves disk space by sharing images with your iPhoto or Aperture libraries - Apple Support
and Six Colors: The (hard) link between Photos and iPhoto
The migration is nearly lossless but not perfect: How Photos handles content and metadata from iPhoto and Aperture - Apple Support
Posted on May 28, 2016 12:49 PM