proimporter - The proimporter Makes Calendars Visible

Importing third-party project plans into Oracle® Primavera P6 often results in contamination by unnecessary data. One example are calendars, which are often configured differently. The proimporter helps you to avoid this!

For complex projects, it is inevitable that the project files of your own company, suppliers and subcontractors are merged. However, these large-scale data imports into Oracle® Primavera P6 can be a threat to the target database. If the Oracle® Primavera P6 standard import is used and the XER file to be imported contains different data compared to the target database, inconsistent data will be imported. The data content in the target database increases, resulting in duplications, synonyms and data that is not needed or deviates from the P6 company specifications.
bild cal
A good example for this are calendars, which have the same name, but differ in configuration and content from database to database. A standard data import is therefore often problematic, because with Primavera P6 EPPM you cannot view the calendar content in advance. Especially the import of global calendars is a big problem for the database, because they could affect all projects where the calendars are stored and in use. If such a calendar is already assigned to activities or resources, it is already in use without being visible to the scheduler. This can have far-reaching consequences for the schedule. Ultimately, all data must be cleaned and adjusted manually. This costs a lot of time and money.
bild2However, the proimporter from proadvise can solve this problem. The practical tool shows every user which calendar content is contained in the import file before importing data into the P6 database. This allows the responsible user to decide whether a calendar should be imported or excluded from import.
The proimporter displays the following configuration information:
• Time Periods
• Standard Workweek
• Exceptions (Non-Work Days/Holidays)
Furthermore, the proimporter gives the user the possibility to convert global calendars into project calendars. This leaves the global database elements untouched and the existing content P6 configuration cannot be contaminated by deviating naming conventions.

Secure, faster, easier – proimporter

You know the exchange of project schedules via xer or mpp files and the inconsistencies associated with it in Oracle Primavera P6? You want to avoid importing corrupt and irrelevant data into your database and reduce the effort of time-consuming cleanup after the import?

With the proimporter, we offer you a solution for fast, precise and secure xer and mpp imports into Oracle Primavera P6 databases - directly and without any detours!

Application area

The proimporter has a wide range of uses in various applications

Consortium partners

Exchanging monthly schedule updates via xer and mpp files with customers and suppliers.


Migration of data between different Primavera P6 databases.

New P6 customers

Transfer of existing schedules in MS Project to Oracle Primavera P6.

Project managers and scheduler

Exchange schedules from different service areas of a project in xer or mpp format and consolidate project data in Primavera P6.

Your Benefit

Increase in data quality

Increase in data quality

Verification and individual mapping of data to be imported
Cost savings

Cost savings

Avoid manual database cleanup and no need to clear up corrupt data after importing
Training expense savings

Training expense savings

User interface simplicity for intuitive use of the toll
Straightforward collaboration

Straightforward collaboration

Exchange of data between partners, suppliers, customers and Primavera P6 databases
Importing Baselines

Importing Baselines

Baselines that have been converted into projects in P6 can be imported as baselines into the target database
Trouble free migration

Trouble free migration

Trouble-free transfer of data during reorganization or tool-rollout

proimporter Roadmap – Outlook on our functional expansions


  Function implemented in the tool
  Function in planning

2nd quarter of 2022

Extension validation of activity codes after quick fix function (after application of quick fix)
Advanced validation of data via API to be written to the database)
Feature ".Pait Templates": compatibility of projects with import templates
Additional validation of relationships, activity codes and UDF values to avoid possible duplicates in the DB
Optimization Quick Fixes Data Date and Activity Codes
Various Bug-Fixes
Q2 2022

3rd quarter of 2022

Message when after quickfix the import action of the project changes from "create" to "update
Validation function of Cost Accounts names
Display of the import strategy for MS Project in the import log of the proimporter
visual display of the status during data import
Validation enhancement and extended import actions when importing baselines that already exist in P6
Multi-client capability (Connection Manager)
Display of performed quick fixes in the import log
Various Bug-Fixes
Q3 2022

4th quarter of 2022

Search function for P6 objects in proimporter
Various Bugfixes
Q4 2022