Migrate from web2Project to Jira

web2Project Projects map directly to Jira Projects. Each web2Project project name becomes the Jira Project name, and the project's owner becomes the Jira Project Lead. We extract the project start and end dates as the Jira Project's start date and the target end date. If the web2Project instance uses the Project Importer module for initial structure, we supplement its output with direct database queries to ensure all related records are captured.

web2Project Tasks map to Jira Issues with an Issue Type decision based on structure: Tasks with no children and no blockers map to Jira Stories or Tasks depending on the customer's naming convention preference; Tasks with subtasks map to Jira Stories with Subtask children. Tasks with only one level of hierarchy map to Jira Stories with Jira Subtasks; deeply nested task trees map to Jira Epics containing Stories containing Subtasks. We preserve the original web2Project task_id in the Jira issue description for traceability.

web2Project Finish-to-Start and Start-to-Start dependencies map to Jira Issue Links with type Blocks and is blocked by respectively. We create the Jira Issue Links during the issue import phase after all Issues have been assigned Jira issue keys, then back-fill the link references using a lookup table generated during the first pass.

web2Project user accounts map to Jira users by email address match. We extract username, email, display_name, and active/inactive status from the web2Project users table. Inactive web2Project users are provisioned as inactive Jira users to preserve historical assignment data without granting active login permissions.

web2Project Companies are organizational entities to which projects and users can be assigned. In Jira, Companies map either to Jira Projects (if each web2Project Company represents a distinct product or client) or to Jira Components (if Companies represent internal divisions within a single project). We confirm the mapping strategy during scoping based on the customer's data model and Jira project structure.

web2Project Departments are sub-organizational units within Companies. Jira has no native department concept, so we map Departments to Jira Components within the relevant project, or to Labels with a department: prefix for cross-project organizational tagging. The customer chooses during scoping.

web2Project custom fields (text, number, date, dropdown, checkbox, rebuilt in v2.4 with SOLID OOP) map to Jira custom fields of the equivalent type. Pre-v2.4 and post-v2.4 web2Project instances have different custom field schemas; we detect the source version during database inspection and adjust field mapping logic accordingly. Custom fields are pre-created in Jira via the REST API before any issues are imported.

web2Project Gantt chart data (task start dates, end dates, durations, and dependencies) migrates as Jira issue dates: Start Date maps to Jira Due Date or custom Start Date field, and duration maps to Estimated Hours. The Gantt visualization itself is not migratable; Jira's board and timeline views are the equivalent visualization layer that the customer's team configures post-migration.

web2Project calendar events migrate as Jira issues with scheduled dates if the events represent deliverables, or as Jira Project Calendar events if they represent cross-project meetings. iCalendar export from web2Project can be ingested as a source reference for the mapping.

web2Project project forums with thread metadata migrate as Jira issue descriptions or Jira Comments on the corresponding migrated issue. Forum post content migrates as Jira Comments attached to the Issue, with the original post date and author preserved. Forum categories that do not map to specific issues are documented as Jira project-level Comments for the customer's admin to route.

web2Project file references at the project and task level migrate as Jira Issue Attachments. Actual file content transfer is a separate coordination step — we extract file metadata and URLs from the web2Project database and provide a file transfer runbook that maps each file to the corresponding Jira issue by cross-referencing the task_id stored in the file record.

web2Project budget fields exist in the schema but are explicitly documentation-only per official documentation — they are not used for tracking, evaluation, or reporting. We migrate budget values as read-only custom text fields in Jira so that the financial data is visible in issue records, but the customer must implement any actual budget tracking workflow through Jira apps or third-party integrations post-migration.