Under MS Project if you want to make your updated plan as a new baseline, just save a new baseline using the menu command for this purpose depending on MS Project version and the data will be frozen on baseline fields. These fields will be kept across your updates and will only be changed until you re-baseline the set. MS project has a limit on how many baseline data sets can save, take note that it saves only a few selected fields.
I would recommend for every update/new baseline to keep a separate file, then from any prior update you can work new baselines as best fit, if need be. Then using export/import functionality within MS Project transfer baseline data only. In this way you can overcome the limitation when your software only allows for baseline data to be saved within the current project files without direct access to other project files. Because MS Project Baseline fields are limited, unless you keep separate files of the updates you might lose track of other relevant data, always keep a separate file for every update. Prior to any update save latest version to a new version file and then do your update on this new file.
Other software allows you to save and access your baseline data to a differently named file. This is easier and gives you more flexibility, you will have no need to do cumbersome data import/export.
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.
Under MS Project if you want to make your updated plan as a new baseline, just save a new baseline using the menu command for this purpose depending on MS Project version and the data will be frozen on baseline fields. These fields will be kept across your updates and will only be changed until you re-baseline the set. MS project has a limit on how many baseline data sets can save, take note that it saves only a few selected fields.
I would recommend for every update/new baseline to keep a separate file, then from any prior update you can work new baselines as best fit, if need be. Then using export/import functionality within MS Project transfer baseline data only. In this way you can overcome the limitation when your software only allows for baseline data to be saved within the current project files without direct access to other project files. Because MS Project Baseline fields are limited, unless you keep separate files of the updates you might lose track of other relevant data, always keep a separate file for every update. Prior to any update save latest version to a new version file and then do your update on this new file.
Other software allows you to save and access your baseline data to a differently named file. This is easier and gives you more flexibility, you will have no need to do cumbersome data import/export.
In any case there is no need to double entry.