[Archivesspace_Users_Group] Migration Advice/Best Practices

Callahan, Maureen maureen.callahan at yale.edu
Tue Mar 24 10:14:31 EDT 2015

Hi Phil,

I’m sure others will have suggestions, but I would recommend you check our ArchivesSpace blog at Yale and the Rockefeller Archives Center’s blog. We’ve started cataloging the various migration errors that we need to diagnose and fix, and will be writing a blog post about them soon.

Beyond this, there’s the obvious piece that you’ll have to start with the Archon migration, since it requires an empty ASpace database. AT doesn’t have this requirement.

Finally, we’ve found that any shared name or subject strings across repositories result in a broken link to the resource. We’re in the throes of figuring out how to re-link those with SQL updates, and we’ll be happy to share what we’ve come up with.

Best of luck with your migration.


On Mar 24, 2015, at 5:52 AM, Suda, Phillip J <psuda1 at tulane.edu<mailto:psuda1 at tulane.edu>> wrote:

Good morning,

                   We are in the process of migrating instances of Archon and AT to ArchivesSpace. We would like to merge all instances (AT + Archon) into one instance of ASpace, with different repositories for each respective instance of Archon or AT. How have people handled this? What are the best practices for this type of migration? Thank you for any and all advice.

Thank you,


Phillip Suda
Systems Librarian
Howard-Tilton Memorial Library
Tulane University
psuda1 at tulane.edu<mailto:psuda1 at tulane.edu>

Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20150324/c825dc86/attachment.html>

More information about the Archivesspace_Users_Group mailing list