Data migration between two alfresco instances

[pierre_lorson]

Hello,

I would like to migrate some data from one instance to another one, without losing the data on the second instance.

What would be the best pratices to do it ? Is there an updated migration tool ?

Thanks in advance

[venzia]

Hi, its depends of your ACS versions and if there are custom models with metadata that need to be migrated too.

Can you share more details about?

KR,

[pierre_lorson]

Hi, thanks for answering

We're using ACS 23.4.1, and we have customs models indeed

[venzia]

Ok, and what's the use case? I mean, can you explain which content need to be "replicated" in the target instance and why? there are several options so to know the context better will allow us to suggest the better choice..

KR,

[AlfrescoZZZ]

This project can let you export content and metadata https://github.com/ziaconsulting/alfresco-bulk-export/
in acp format and import the acp in another alfresco https://formtektips.blogspot.com/2016/11/import-and-export-of-alfresco-acp-files.html
Please note that it is important that the two alfresco instances have users with the same username (case sensitive if possible to avoid some annoying low-level errors) and, even more importantly, the same Alfresco Models.

[Overwerkt]

Hi pierre_Lorson,

If you want to migrate Alfresco Enterprise Edition data from one instance to another without losing data on the second instance, you'll need to carefully plan and execute the migration process. Here are some best practices and considerations:

Best practices for Alfresco data migration without data loss

1. Back up both instances: Before initiating any migration, create complete backups of both the source and target Alfresco instances, including the database, content store (dir.root), and SOLR indexes. This provides a safety net in case of unforeseen issues during the migration process.

2. Ensure compatibility:  Verify that the Alfresco versions and configurations are compatible between the two instances. This includes custom content types and models, if applicable.

3. Plan the migration strategy:  Choose a migration approach that minimizes downtime and disruption, considering factors like the volume of data and sensitivity of information. Common strategies include:

Bulk Migration:  Migrating a large portion of data in one go, while allowing users to access the existing system, and syncing new information afterward.

Phased Migration:  Migrating data in stages, perhaps department by department, or starting with recent and essential data.

On-Demand Migration:  Migrating specific content only when it's requested by users.

6. Utilize migration tools:  Consider using specialized tools like Proventeq's Migration Accelerator, which can migrate, enrich, restructure, and classify content while maintaining metadata, custom properties, and views. You may need to create or utilize a custom migrator for highly specific or complex scenarios, particularly when dealing with content models or properties not present in the target environment.

5. Thoroughly test and validate:  After the migration, rigorously test and validate the migrated data, including content, metadata, workflows, and access rules, to ensure data accuracy and integrity. Pay close attention to details like file creation dates to ensure they tally with pre-migrated versions.

6. Implement a change management plan:  Provide adequate training and support to users to help them adapt to the new Alfresco instance.

Are there updated migration tools?

While Alfresco itself provides some basic migration and backup/restore capabilities, for Enterprise Edition migrations, particularly when maintaining data on the target instance is paramount, consider the use of tools like the Migration Accelerator mentioned earlier.  Additionally, for specific scenarios such as migrating from a legacy system to Alfresco, or converting Enterprise Edition to Community Edition, you may need to develop or leverage custom migration scripts or tools. Organizations experienced in Alfresco data migration can also provide valuable expertise and support. (You can ask your Alfresco Account Manager or Customer Service Manager to put your in touch with one of their clients who might be willing to share their knowledge and experience about their own Alfresco data migration.)

Important Note: Migrating Alfresco data, especially without data loss, requires careful planning, technical expertise, and attention to detail. Always thoroughly test your migration plan in a staging environment before attempting it on production systems.

[AI responses may include mistakes. Learn more]

[heiko_robert]

A bit late but I just saw the thread by accident. We have implemented our own Alfresco modules, “ecm4u Alfresco Sync,” which works similarly to rsync. It consists of a server and a client module, and you define the source and target node, as well as a blacklist of aspects and properties.

The client recursively replicates the nodes, including the properties, and adds the old nodeRef as a reference so that direct links to a nodeRef can later be redirected to the new node (alfresco will always create new nodeRefs in the target).

If you are interested, please send me a direct message.