I looked into Mylio, firstly I can’t move on as the registration process seems to be broken. I’ve registered with two different email addresses but their verification email never arrives, so you can’t run their Mac client.

But, there’s a blog post explaining their “import from Aperture” process, which is less than it seems. As we all now, you can export the originals or versions into a folder from Aperture. Mylio can then import that folder.

If you export the originals you leave behind all edits and metadata, if you export versions you embed edits without being able to reverse them.

Overall this doesn’t seem like a real migration path from Aperture. I’m experimenting with Capture One which successfully imported 35,000 photos for me.

Bill.

Given what I’ve learnt about their ‘import’ I won’t be bothering to pursue this - it’s not achieving much, other than moving the files out of Aperture and into Mylio.

The information you read was from an old FAQ 

The correct updated link for the new Mylio Aperture Import is here

https://support.mylio.com/hc/en-us/articles/204523374-Importing-From-Ape…

This is a full import feature with all edits (Crop, Rotate, Adjustments), Albums, Faces, Locations, etc…

Hi – I wrote The Official Guide to Mylio, I wrote this independently from the company after I fell in love with the early beta releases.  Full disclosure, I have since joined the company.   As an Aperture user since beta, I can tell you first-hand that the Aperture import is nothing short of a godsend to Aperture fans looking for an alternative platform.  It is the first tool I have seen that actually brings in your edits, crops, etc.  It has been in beta (available to anyone who currently uses Mylio for about a month and is about to be released).

Based on some of the comments here, it is clear that an old FAQ file was not removed.  The original way to export to Mylio was clunky and required you export and import.  With the Aperture release, it is as simple as clicking on Import Aperture Files. 

There are three useful locations on the Mylio site to learn more about how the import works:

1 - http://budurl.com/Mylioaperture1 - Covers basic Importing from Aperture to Mylio.

2 - http://budurl.com/Mylioaperture3 - Provides a comprehensive list of Aperture features and how they convert to Mylio.

Apple made it impossible to move 100% of the features, but Mylio now offers the most complete Aperture migration path available anywhere.  Even if you intend to use Lightroom, Mylio’s interop with Lightroom (and Photoshop) make it a more complete solution than importing into Lightroom alone.

We’d love to get feedback from any of you who try the product, and we offer a 30 day free trial at - http://budurl.com/MylioFreetrial .

We have world-class support too (all of our support team are former Apple Geniuses), so please don’t hesitate to reach out to support@mylio.com with any questions.

Thanks for the updates everyone - now I have to find 365Gb free on my hard drive, which I don’t have :-(

But seriously, this looks like a better path than others - I’ve been trying Capture One and not fully convinced of that path yet.

We at Mylio want to be of service to the Aperture community.  I am the founder and wanted to take a moment to provide a quick overview of where we fit in.

Mylio represents a new category of tool.  It provides many of the same features as Aperture and Lightroom but also reaches into new territory including the ability to work on computers (Mac and Windows) and devices – phones and tablets.  Today we support IOS but Android is in beta and will become available soon.  In addition to allow you to work with and organize pictures on a single machine, it also replicates your pictures across all your machines so you can work wherever you are.  The same replication engine allows you to automate the process of protecting your pictures.  Uniquely all of this works both with and without the cloud.  For example, I am writing while travelling with almost non-existent internet connections and yet replication still works completely and is very fast.

We built our own raw stack; doing a good job with your pictures is important to you and to us.  Building a comlete suite of tools takes time.  Today we have all the global adjustments.  A few features also coming soon round this out including brushes (yes), and presets which can be applied against sets of images and also applied at import time.  So, if you see this missing, know that it is coming.

Most importantly, for the Aperture community, we imagined how it must feel to have thousands of pictures and face losing all your adjustments and metadata in the process of moving to a new environment.  That is why we went the extra mile to work around the limitations of the Apple SDK and develop our own mechanisms to bring all your work across.  We hope this serves you well.

We are here to help.  If you have questions, please ask.  And, if you do decide to start working with us, you can count on our support when you need it.

Looking forward to helping you.

David

I am trying to determine if there can be an effective and efficient workflow combining Mylio and Capture One.  Mylio customer support has been excellent. Having reviewed Mylio’s description of ‘edits’ that are carried over from Aperture, I am waiting for further clarification from them.  Mylio requires the ‘duplication’ of the originals from the Aperture referenced library.  This will create a new 620 GB folder, leaving the original Aperture folder intact and no longer accessed.  It was originally suggested that Capture One reference the Mylio folder, and that Mylio creates a ‘Watch’ on the Capture One Catalog in order to update the files in the Mylio Library.  This seemed to be a great solution.  Use Mylio as the best transition from Aperture to replicate your library and edits; use Capture One as the primary RAW editor; let Mylio ‘watch’ and reflect these edits in it’s Library; and let Mylio manage backing up to a different location (Drobo NAS).  And, when not connected to the backup, Mylio would cache these changes and then reconnect to d/l at the best time.  I thought I went to heaven!  Then I was told that everything could be set up as indicated, but Mylio will not be able to read Capture One’s edits since they are ‘hidden’ in Capture One’s ‘Library’. Sort of similar to Aperture’s Library, but Mylio has not yet overcome this hurdle.  Therefore the Capture One ‘Watch’ folder will not work out.  Will Mylio work this out with Capture One?  Is there a valid reason for them to do this? Or, is it only Lightroom that Mylio will ‘integrate’ with in this manner?

Capture One’s Aperture import appears to be excellent. But how good is their import of Aperture edits compared to Mylio?  How good is their batch processing of metadata and IPTC compared to Mylio? If good enough, then Mylio may not be enough of added value.

I too am concerned that a future Apple OS will no longer ‘support’ Aperture. Therefore, I do not want to continue to invest in Aperture and move on now so as to be fully integrated  when/if it should happen.  I purchased the Mylio Premium package when on special–good deal; but have not yet pulled the trigger on Capture One. My Drobo 5N is now set up, however I have not yet begun the transition from Aperture and will wait until confident of the ultimate plan.

I look forward to Mylio’s experts additions to this thread and hopefully Capture One will chime in as well.  Also, I am interested in whatever observations and conclusions that both Bill and Nick may continue to offer.

Two sets of comments going on here, that really turn into three: library size, Capture One, and Interop / Editing in general.

There are three levels of Mylio; all three should easily support a 300GB library.  Perhaps the size related to images.  The Basic SKU is defined around jpg and simple edits; the other two SKU’s provide full raw.  One of the main breakthroughs in Mylio is the ability to scale.  My own library has over 500,000 images and is 8TB in size.  The $21 / month SKU has a marketing limit of 500,000 images, but on request and at no extra charge we will relax that limit; there are now a significant number of users with 600K, 800K and even over 1M images in the system.

I do not have the details right now but we can interop pretty well with Cature One.  We also interop extremely well with Photoshop; PSD’s are replicated and displayed.  In the case of Capture / One there are two ways of storing files and one works much better than the other.

We do have a goal of supporting most of the editing that somebody like an Aperture user would do.  Then the interop is there for the presumably small number of pictures that require really sophisticated editing, with everything fitting into a smooth overall workflow.  One advantage of being able to edit many or most of your pictures in Mylio itself is that you can then work on them on a tablet as well as a computer.  I am actually on a trip right now where I have worked on thousands of pictures on my iPad, with no internet connection on a train where working with my computer would just not have been possible.

I can send more details on Capture One interop later this week if that helps.

David, more details of the Capture One interop would be great. If Capture One uses the Mylio folder with the Raw files (imported from Aperture) will Capture One recognize all of the edits imported by Mylio?  Will Capture One recognize new edits made in Mylio?  If Capture One edits are made on any of these Raw files, will Mylio recognize these edits?  If so, will this be accomplished by using the Mylio ‘Watch’ function on the Capture One ‘Library’? If not now, what is the probability that Mylio will develop this interop?  Can you suggest a workflow using Mylio as the primary DAM, a 4TB mobile drive as the primary location for original files, and the Drobo NAS network storage as the back up/edited raw versions for all files? Thanks again.

David, anything new concerning the intro with Capture One? 

Thanks.

Thank you for following up and hopefully the future will fully integrate Mylio with CP1. My interest is to: 1- Use Mylio’s Aperture import tool. 2. Use Mylio to effect multiple back ups of the original files. 3- Use Mylio as the primary DAM. 3- Use CP1 as the primary editing tool. 4- Use Mylio to ‘Watch’ changes to the CP1 and ‘import’ these changes to the Mylio library. Therefore, any changes to the RAW file made by CP1 will be acknowledged by Mylio and backed up as well.  I understand at this time that Mylio does not recognize the ‘XMP’ side car files that CP1 creates because they are hidden in the CP1 library. Sort of the way that Aperture hides their changes in the Aperture Library.

In Aperture, their Backup algorithm only backs up the original unedited files.  Therefore it is important to save the last Aperture Library before importing to Mylio or any other application.

I was hoping that Mylio would solve this problem by locating the Mylio ‘Library’/original to my mobile 4TB drive; back up to my NAS device; and then all changes to files/and new imports to Mylio would be simultaneously backed up to my NAS device.  

I think that this is possible with Mylio now (am I correct about this and my RAW files?); but not with the integration of CP1.

I look forward to this possible change with CP1.

Thank you David

Just curious if anyone out there is having success using Mylio and CaptureOne together?  Kind of like an alternative to Creative Cloud for Capture One users.