%3CLINGO-SUB%20id%3D%22lingo-sub-361769%22%20slang%3D%22en-US%22%3EProject%20Online%3A%20Migration%20into%20or%20between%20PWA%20sites%20and%20tenants%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-361769%22%20slang%3D%22en-US%22%3E%0A%20%26lt%3Bmeta%20http-equiv%3D%22Content-Type%22%20content%3D%22text%2Fhtml%3B%20charset%3DUTF-8%22%20%2F%26gt%3B%3CSTRONG%3E%20First%20published%20on%20TECHNET%20on%20Jun%2024%2C%202015%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%3CP%3EWe%20get%20quite%20a%20few%20questions%20on%20this%20topic%20of%20migration%20to%20the%20cloud%2C%20so%20for%20example%20Project%20Server%202010%20or%20Project%20Server%202013%20to%20Project%20Online%20-%20and%20also%20moving%20data%20between%20tenants.%26nbsp%3B%20Perhaps%20a%20trial%20to%20the%20real%20one%20%E2%80%93%20or%20even%20making%20a%20copy%20of%20production%20in%20another%20PWA%20instance%20in%20the%20same%20Project%20Online%20tenant.%26nbsp%3B%20Unfortunately%20there%20are%20not%20any%20short%20cuts%20here.%26nbsp%3B%20We%20don%E2%80%99t%20have%20any%20capability%20to%20move%202010%20or%202013%20databases%20up%20to%20our%20datacenters%20(the%20schema%20is%20now%20quite%20different%20%E2%80%93%20and%20we%20are%20in%20the%20content%20database%E2%80%A6).%26nbsp%3B%20Neither%20can%20we%20pull%20data%20out%20from%20one%20PWA%20instance%20and%20move%20it%20to%20another%20-%20either%20within%20the%20tenant%20or%20to%20another%20tenant.%26nbsp%3B%20Also%20we%20have%20no%20means%20to%20move%20PWA%20to%2Ffrom%20dedicated%20farms.%3C%2FP%3E%0A%20%20%3CP%3EThe%20options%20for%20migration%20are%20listed%20on%20the%20TechNet%20page%20that%20compares%20Project%20Server%202013%20and%20Project%20Online%20-%20%3CA%20href%3D%22https%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fdn268595.aspx%22%20title%3D%22https%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fdn268595.aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%20https%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fdn268595.aspx%20%3C%2FA%3E%20-%20%3CSTRONG%3E%20A%20feature%2Ffunction%20comparison%20of%20Project%20Online%20and%20Project%20Server%202013.%20%3C%2FSTRONG%3E%20Look%20around%201%2F4%20of%20a%20way%20down%20the%20page%3A%3C%2FP%3E%0A%20%20%3CP%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F85540i5CD483B99DF86486%22%20%2F%3E%3C%2FP%3E%0A%20%20%3CP%3EThe%20article%20does%20continue%20on%20to%20cover%20resource%20migration%20options%20too.%26nbsp%3B%20If%20you%20are%20a%20partner%20with%20a%20solution%20we%20don%E2%80%99t%20suggest%20above%20then%20I%E2%80%99m%20sure%20we%20would%20be%20very%20pleased%20to%20update%20the%20list.%26nbsp%3B%20If%20you%20have%20developer%20capabilities%20you%20could%20also%20use%20some%20of%20the%20programmatic%20interfaces%20and%20write%20your%20own%20migration%20package%20%E2%80%93%20see%20the%20SDK%20information%20at%20%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fdownload%2Fdetails.aspx%3Fid%3D30435%22%20title%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fdownload%2Fdetails.aspx%3Fid%3D30435%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%20https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fdownload%2Fdetails.aspx%3Fid%3D30435%20%3C%2FA%3E%20.%3C%2FP%3E%0A%20%20%3CP%3EOne%20of%20the%20challenges%20of%20using%20the%20manual%20methods%20is%20carrying%20over%20the%20metadata%20%E2%80%93%20particular%20where%20lookup%20table%20based%20fields%20are%20concerned.%26nbsp%3B%20One%20potential%20option%20is%20even%20for%20lookup%20table%20fields%20to%20create%20another%20non%20lookup%20table%20field%20and%20copy%20in%20the%20data%2C%20so%20you%20can%20at%20least%20carry%20over%20the%20actual%20field%20setting%20%E2%80%93%20then%20use%20this%20in%20the%20new%20instance%20to%20re-set%20the%20lookup%20table%20values.%26nbsp%3B%20Although%20we%20don%E2%80%99t%20endorse%20any%20of%20the%203rd%20party%20solutions%20it%20is%20certainly%20worth%20reviewing%20if%20they%20would%20help%20to%20give%20you%20a%20cost%20effective%20migration%20and%20help%20overcome%20some%20of%20these%20challenges.%26nbsp%3B%20And%20with%20this%20next%20suggestion%20I%E2%80%99m%20not%20just%20trying%20to%20put%20a%20positive%20spin%20on%20things%20%E2%80%93%20but%20migration%20is%20a%20great%20time%20to%20reconsider%20how%20you%20have%20things%20configured%20%E2%80%93%20and%20if%20your%20current%20configuration%20is%20best%20serving%20your%20needs.%3C%2FP%3E%0A%20%0A%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-361769%22%20slang%3D%22en-US%22%3EFirst%20published%20on%20TECHNET%20on%20Jun%2024%2C%202015%20We%20get%20quite%20a%20few%20questions%20on%20this%20topic%20of%20migration%20to%20the%20cloud%2C%20so%20for%20example%20Project%20Server%202010%20or%20Project%20Server%202013%20to%20Project%20Online%20-%20and%20also%20moving%20data%20between%20tenants.%3C%2FLINGO-TEASER%3E%3CLINGO-SUB%20id%3D%22lingo-sub-891202%22%20slang%3D%22en-US%22%3ERe%3A%20Project%20Online%3A%20Migration%20into%20or%20between%20PWA%20sites%20and%20tenants%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-891202%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Brian%3C%2FP%3E%3CP%3EWith%20the%20velocity%20of%20Office%20365%20usage%2C%20migration%20of%20Project%20Online%20from%20one%20tenant%20to%20another%20is%20growing%2C%26nbsp%3B%20this%20is%20a%20good%20time%20to%20discuss%20again%20tenant%20migration%20in%20this%20blog%20(suggestion%20of%20idea).%3C%2FP%3E%3CP%3EQUESTION%3A%20I%20do%20not%20see%20the%20point%20with%20the%20lookup%20table%20option%20quoted%20here%3A%20what%20is%20the%20trick%20behind%20%3F%20does%20this%20help%20filling%20the%20lookup%20values%20to%20use%20non%20lookup%20field%20instead%20%3F%26nbsp%3B%20and%20then%20re%20set%20the%20customed%20fields%20with%20a%20value%20and%20set%20the%20values%20in%20the%20lookup%20list%20and%20reset%20the%20customed%20field%20with%20this%20lookup%20list%26nbsp%3B%20in%20the%20destination%3F%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20the%20tenant%20migration%20I%20prepare%2C%20I%20just%20thought%20to%20set%20manually%20the%20lookup%20up%20table%20as%20a%20strict%20copy%20of%20the%20source%20lookup%20table%20to%20migrate.%20As%20such%2C%20no%20issue%20should%20appear%20at%20the%20migration%20stage%2C%20when%20importing%20projects.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1449261%22%20slang%3D%22en-US%22%3ERe%3A%20Project%20Online%3A%20Migration%20into%20or%20between%20PWA%20sites%20and%20tenants%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1449261%22%20slang%3D%22en-US%22%3E%3CP%3EBrian%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDoes%20this%20mean%20there%20is%20no%20way%20to%20take%20and%20existing%20PWA%20online%20instance%20and%20migrate%20into%20a%20new%20one%3F%20Is%20the%20best%20method%20to%20just%20reload%20the%20MPP%20into%20the%20new%20PWA%20online%20environment%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJames%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1450192%22%20slang%3D%22en-US%22%3ERe%3A%20Project%20Online%3A%20Migration%20into%20or%20between%20PWA%20sites%20and%20tenants%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1450192%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F10841%22%20target%3D%22_blank%22%3E%40James%20Lucier%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThere%20is%20no%20out%20of%20the%20box%20way%20to%20do%20that%20unfortunately.%20You%20either%20manually%20re-configure%20the%20target%20PWA%20instance%20and%20move%20projects%20by%20re-saving%20the%20mpp%20files%20to%20the%20new%20target%20PWA%20instance%20or%20you%20look%20at%20a%203rd%20party%20tool%20%2F%20develop%20your%20own%20tool.%3C%2FP%3E%0A%3CP%3EPaul%3C%2FP%3E%3C%2FLINGO-BODY%3E
First published on TECHNET on Jun 24, 2015

We get quite a few questions on this topic of migration to the cloud, so for example Project Server 2010 or Project Server 2013 to Project Online - and also moving data between tenants.  Perhaps a trial to the real one – or even making a copy of production in another PWA instance in the same Project Online tenant.  Unfortunately there are not any short cuts here.  We don’t have any capability to move 2010 or 2013 databases up to our datacenters (the schema is now quite different – and we are in the content database…).  Neither can we pull data out from one PWA instance and move it to another - either within the tenant or to another tenant.  Also we have no means to move PWA to/from dedicated farms.

The options for migration are listed on the TechNet page that compares Project Server 2013 and Project Online - https://technet.microsoft.com/en-us/library/dn268595.aspx - A feature/function comparison of Project Online and Project Server 2013. Look around 1/4 of a way down the page:

The article does continue on to cover resource migration options too.  If you are a partner with a solution we don’t suggest above then I’m sure we would be very pleased to update the list.  If you have developer capabilities you could also use some of the programmatic interfaces and write your own migration package – see the SDK information at https://www.microsoft.com/en-us/download/details.aspx?id=30435 .

One of the challenges of using the manual methods is carrying over the metadata – particular where lookup table based fields are concerned.  One potential option is even for lookup table fields to create another non lookup table field and copy in the data, so you can at least carry over the actual field setting – then use this in the new instance to re-set the lookup table values.  Although we don’t endorse any of the 3rd party solutions it is certainly worth reviewing if they would help to give you a cost effective migration and help overcome some of these challenges.  And with this next suggestion I’m not just trying to put a positive spin on things – but migration is a great time to reconsider how you have things configured – and if your current configuration is best serving your needs.

3 Comments
Established Member

Hi Brian

With the velocity of Office 365 usage, migration of Project Online from one tenant to another is growing,  this is a good time to discuss again tenant migration in this blog (suggestion of idea).

QUESTION: I do not see the point with the lookup table option quoted here: what is the trick behind ? does this help filling the lookup values to use non lookup field instead ?  and then re set the customed fields with a value and set the values in the lookup list and reset the customed field with this lookup list  in the destination? 

In the tenant migration I prepare, I just thought to set manually the lookup up table as a strict copy of the source lookup table to migrate. As such, no issue should appear at the migration stage, when importing projects.

Senior Member

Brian,

 

Does this mean there is no way to take and existing PWA online instance and migrate into a new one? Is the best method to just reload the MPP into the new PWA online environment?

 

Thanks,

 

James

Hi @James Lucier 

There is no out of the box way to do that unfortunately. You either manually re-configure the target PWA instance and move projects by re-saving the mpp files to the new target PWA instance or you look at a 3rd party tool / develop your own tool.

Paul