As Alex says, there is a bi-directional import. And it could be used (without needing anything else), if used with caution. But I dont recommend it for ongoing use on the same project. Because in the end they are different software, with different underlying architecture and engines.
As soon as you add any of the "more" that is in Primavera 5.0 (such as more than 24 activity codes, more than ten project codes, or any resource codes), P3 wont be able to read that. And if you use more than P3s permitted length of activity id (10 characters, whereas 5.0 has potentially double that) then you wouldnt be able to transfer data at all, because thats the key database field.
you can transfter data between the two stream of software, "BUT" because of their data structure you can not easily transfer back and forth without some sort of integration tool. ie SDK
In you situation of being subby is using P3 and if you are using P3e then its ok because you only need one direction of dataflow P3 to P3e. Therefore if you are using P3e is ok.
Spider Project is most functional and powerful professional project management software.
The first SP version was launched in 1993 and since then it has been constantly improved. Today is used in 34 countries though most Spider Project customers are in Russia. Spider Project offers numerous unique functional features and is the only PM software that optimizes resource, cost, and material constrained schedules and budgets for projects and portfolios.
The unique features of Spider Project include Quantity Based Scheduling, Conditional Scheduling, Skill Scheduling, Optimal Resource, Cost and Material Leveling, Resource Critical Path Calculation, Cash and Material Flows Calculation and Management, Trend Analysis, Advanced Risk Simulation and Analysis, Calculation of Success Probability Trends, Calculation and Management of required Project Time and Cost Buffers, Application of Corporate Norms, Management of many Parallel Budgets, Multiple WBS and many others.
Spider Project was and is used for management of many large scale programs in Russia, including $51bln construction program for 2014 Winter Olympic Games preparation.
The application areas where Spider Project is successfully used include Aerospace, Banking, Construction, Defense, Energy, Engineering, Infrastructure, Manufacturing, Metallurgy, Mining, Oil & Gas, Railways, Retail, Shipbuilding, Software Development, Telecommunications, Utilities, etc.
P6-Auditor - Display information from Primavera P6 audit tables in a user-friendly format
Unifier-Archiver - Extract and archive important documents and attachments from Primavera Unifier
Unifier-Loader - Load data into and out of Unifier via Excel
PCM-Loader - Import data into Primavera Contract Management with flexible and secure, template-driven Excel spreadsheets
PCM-Archiver - Extract and archive important documents and attachments from Primavera Contract Management
PCM-Unifier Migrator - Automatically transfer live and historical data from Primavera Contract Management to Primavera Unifier with ease
Create Radically Better Construction Schedules with ALICE Technologies
Use the power of AI to create construction schedules that reduce risk while cutting costs and build time. With ALICE, develop the ideal schedule during preconstruction -- or recover projects that are off schedule and over budget.
As Alex says, there is a bi-directional import. And it could be used (without needing anything else), if used with caution. But I dont recommend it for ongoing use on the same project. Because in the end they are different software, with different underlying architecture and engines.
As soon as you add any of the "more" that is in Primavera 5.0 (such as more than 24 activity codes, more than ten project codes, or any resource codes), P3 wont be able to read that. And if you use more than P3s permitted length of activity id (10 characters, whereas 5.0 has potentially double that) then you wouldnt be able to transfer data at all, because thats the key database field.
Adrian
The quick answer is NO.
you can transfter data between the two stream of software, "BUT" because of their data structure you can not easily transfer back and forth without some sort of integration tool. ie SDK
In you situation of being subby is using P3 and if you are using P3e then its ok because you only need one direction of dataflow P3 to P3e. Therefore if you are using P3e is ok.
HTH
Alex