PS Data Migration - inflight

Table of Contents

• Data Identification and Mapping
• Categorize Project Status
• Prioritize Migration Based on Status
• Adapt Data Migration Approach
• Elaborating on Previous Points with Project Status in Mind
• Cutover and Go-Live

1. Data Identification and Mapping

In SAP Project Systems (PS), identifying and mapping the correct data is essential for a smooth migration. Below are key considerations:

• Project Structures: Identify WBS elements, networks, and activities from the legacy system and map them to SAP PS structures.
• Master Data: Migrate master data like WBS, networks, activities, cost centers, internal orders, and equipment.
• Cost Elements and Objects: Ensure proper mapping of cost elements and objects for accurate financial data handling.
• Personnel and Resource Data: Migrate personnel assignments (labor, materials, etc.) linked to specific project tasks.

2. Categorize Project Status

Managing projects at various stages of completion requires special consideration. Below is how to categorize the status of projects:

• Completed with Warranty: Retain financial and historical data for warranty claims and analysis.
• In-Progress: Migrate all data, including planned and actual costs, schedules, and open commitments.
• On Hold/Suspended: Capture reasons for the hold and associated costs up to that point.
• Cancelled: Maintain records of the cancellation reasons and related costs.

3. Prioritize Migration Based on Status

To minimize disruption, prioritize migration based on project status:

• In-Progress Projects: Prioritize to ensure minimal disruption to ongoing operations. Focus on budgets, schedules, and actual costs.
• Completed with Warranty: Migrate next, focusing on financial data and open commitments.
• On Hold/Suspended and Cancelled: These can be migrated later, as they do not impact ongoing operations.

4. Adapt Data Migration Approach

Adapting the migration strategy based on project status helps with a smoother process:

• Phased Approach: Migrate in phases, starting with the most critical projects. Each phase should include thorough testing and validation.
• Data Transformation: Develop transformation rules for each project category. For example, completed projects may need to archive certain data.

5. Elaborating on Previous Points with Project Status in Mind

Each project status category requires specific considerations in project structure, budgeting, execution, and integration:

• Project Structure: Ensure accurate migration of WBS for completed projects and precise mapping for in-progress projects.
• Budgeting and Costing: Migrate final cost figures and budgets for completed projects and detailed costing for in-progress projects.
• Execution and Control: Migrate completion dates and performance data for completed projects and schedules, milestones, and assignments for in-progress projects.
• Integration with Other Modules: Ensure seamless integration with other modules (MM, FI) for completed and in-progress projects.

6. Cutover and Go-Live

The cutover process should be well-planned for each project status category to ensure smooth migration and minimal disruption:

• Cutover Planning: Define cutover points for each project category, considering different timelines and procedures.
• Data Migration Execution: Execute migration in phases, starting with critical in-progress projects.
• Post-Migration Validation: Conduct detailed validation for each project status category to ensure data integrity.