Can confirm, thank you.
To add further detail to the issues with imports, I add reproduction steps for you.
1. Project Imports
- Projects imported with fields id | name | idClient | projectCoe | idProjectType | idStatus | idHealth
Filled in
On Import, Projects appear in PROJECTS
On Import, Planning shows projects but with no names
Saving each project manually fixes the missing links (Not very fun for many projects

)
2. Activities Import
- Successful import using fields id | idProject | idActivityType | name | idUser | idStatus | done = 0 | idActivityPlanningMode = 1
All activities imported and viewable in ACTIVITIES, Planning mode no activities visible.
Manual save of activities is now required for them to display in planning (not in WBS order)
Once all saved, each project in planning must be drag/dropped to initialise the WBS ordering for all related activities (oriaplanningelement is the suspected cause - records are all initialised as NULL, once saved values are committed)
Next step is ticket import... if I must save each one manually we will have to cease with the tool for now - There are too many tickets to manually save. Is this likely to be fixed if we pay for support?