Hi Jon, I can only give a very generic answer as I have not done a migration myself. Others will comment, I'm sure.
Migration options: Manually. For a small site (< 300 pages) a manual migration works OK. This means copy-pasting content from the old system to Magnolia CMS. Your site has 7500 pages so this is probably too big an effort. Scripting. For a larger site you may want to write a script that reads the incoming content (preferably in XML for ease of implementation) and stores it in the Java Content Repository (JCR). The script can be written in the Groovy language for example. This is a semi-automated process that allows you to add Magnolia CMS specific metadata, such as indicating whether a page should be visible in navigation and whether a page should it be teased from a section page. A Groovy script can import content into the JCR directly. XML import. The XML import/export feature expects the incoming XML to be in the standard JCR System View XML format. If the incoming XML is not in the correct format it needs to be translated first, for example with a script. With a script you can also identify content types in the XML, such as "articles", "products", "images", and transform them into the format Magnolia CMS can import natively. Data module. The Data module can handle structured data such as XML and store it independent of page structure. This is a viable option for migrating non-page content such as addresses, employees, client references and such. You can also use the Document Management System (DMS) for mass upload of non-page content. It allows you to import a complete file system in .zip format. Zip the assets and select "upload zip" from the context menu in AdminCentral. Magnolia uploads the package and extracts it to a file hierarchy. With any of these options, it makes sense to split up the migration - don't try to do everything in one go. --Antti On Jun 23, 2011, at 10:03 AM, Jon RINGWOOD PSE 55500 wrote: > Morning all, > > Apologies if this has been discussed previously but is there any way to > import content from another CMS into Magnolia? I don't think the import > feature is designed for this sort of process. Is the only way to manually > create new pages from scratch? Quite an issue for us as we're considering > migrating our current intranet, over 7,500 pages, from our current CMS into > Magnolia. > > Has anyone had any experience with this, it must be a fairly common problem. > > Any advice most welcome. > > Jon R > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- > This email and any other accompanying document (s) contain information from > Kent Police, which is confidential or privileged. The information is > intended to be for the exclusive use of the individual(s) or bodies to whom > it is addressed. The content including any subsequent replies could be > disclosable if relating to a criminal investigation or civil proceedings. If > you are not the intended recipient, be aware that any disclosure, copying, > distribution or use of the contents of this information is prohibited. If you > have received this email in error, please notify us immediately by contacting > the sender or telephoning 01622 690690. ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
