Has anyone had success moving existing projects from the core tables into teamspaces?

[David84]

Hi, everyone.

We're starting to utilize our Teamspaces with Project Portfolio Suite with Financials.

Is there a way to migrate projects currently in the core tables into the extended teamspace project tables?

There isn't anything I can find in the documentation and the one mention I found in the community from 2 yrs ago ended with the recommendation to open a HI ticket.

Cheers,

David

[Uncle Rob · Accepted solution]

Never had to do it before, but here's how I'd attempt it.
First, understand all the tables that teamspaces adds:

https://docs.servicenow.com/bundle/newyork-it-business-management/page/product/project-management/re...

Then I'd run a script to move the project first, then whatever subservient records into the given teamspace tables (by changing the record's sys_class_name).

[David84]

Thanks for the response Robert.

I'll try that out in my dev instance. 

Hope I can report success later.

Cheers.

[Jayarnab Saha]

Hi David,

teamspace tables (tsp*_project) are extended from core project table (pm_project). So, all your teamspace records are belongs to parent table pm_project as well.

Now, if you want to migrate the records from pm_project (parent table) to tsp*_project (child table), then you need to update the sys_class_name field. 

For pm_project the sys_class_name is 'pm_project', you need to update it to 'tsp*_project' (i.e., if you have installed teamspace1 plugin, then you have to make it 'tsp1_project'). Hope this answer helps you.

Regards,

Jayarnab

[David84]

Thanks Rob and Jayarnab for the responses.

I've been able to successfully move projects and project templates in my dev instance and in our working instance.

The field sys_class_name is the key field to change, but there is another field that appears in some records that also need to be changed to the appropriate table.

Template definition records hold a "table" field that references the actual table the template record will be used in. If it references a PPM table that is extended in Teamspace, it too needs to be updated.

Here is a list of fields I needed to change to migrate Projects and Project Templates

current projects:
pm_project -> sys_class_name ==> tsp1_project
pm_project_task -> sys_class_name ==> tsp1_project_task

template definitions:
project_template -> sys_class_name ==> tsp1_project_template
project_template -> table ==> tsp1_project

template task record:
project_template_task -> sys_class_name ==> tsp1_project_template_task
project_template_task -> table ==> tsp1_project_task

template relation record: (table field = planned_task_rel_planned_task)
project_template_task -> sys_class_name ==> tsp1_project_template_task

Cheers,

David