Migrate your web2Project data

Projects are the core object in web2Project. Every project has a name, color, owner, and is assigned to a Company. We migrate all standard project fields including start/end dates, priority, and status. The Project Queue (index page) filter state is not migratable — we preserve the active project data only.

Tasks are the primary work unit and are created, tracked, and assigned within Projects. Tasks support parent-child hierarchy (subtasks), assignees, start/end dates, and priority. We migrate the full task structure including subtasks and preserve all task-level custom fields.

web2Project supports inter-task dependency management. We map dependency relationships to the destination platform's native dependency model (Finish-to-Start, Start-to-Start, etc.) where supported.

Users are the platform's user accounts tied to permissions and task assignments. We migrate user records including username, email, and role assignments. Active/inactive status is preserved and mapped to the destination's equivalent user state.

Companies in web2Project are the organizational entities to which projects and users can be assigned. This is distinct from departments. We migrate company records including name and contact information and map them to Accounts or Organizations in the destination.

Departments are sub-organizational units within Companies. We preserve the department hierarchy and map it to the destination's equivalent org structure (Departments, Teams, or similar).

web2Project has a custom field system that was rebuilt in v2.4 using SOLID OOP principles. Custom field types include text, number, date, dropdown, and checkbox. We map custom fields 1:1 where the destination supports equivalent types, and flag fields that require manual recreation if the destination lacks the matching type.

web2Project provides both project-wide and group Gantt charts for visual planning. We migrate the underlying task dates, durations, and dependencies that drive Gantt visualization. The Gantt chart rendering itself is destination-platform-dependent.

The platform includes a unified calendar with iCalendar export support for tasks and events. We migrate calendar events and map them to the destination's calendar or tasks with date fields. iCalendar feed URLs are preserved as references.

Project-specific forums can be attached to projects. Forum structures (categories and thread metadata) are migratable. Post content is migrated as comments or discussion items. Note that forum posts do not include rich-media attachments.

web2Project supports file attachments at the project and task level. We migrate file references and metadata. Actual file content requires a separate file transfer step — we coordinate this alongside the database migration to ensure linked files are available post-migration.

Budget fields exist in the web2Project schema but are explicitly documented as for documentation purposes only — they are not used for tracking, evaluation, or reporting. We migrate them as read-only text fields and flag them explicitly so customers do not expect live budget tracking in the destination.

web2Project logs user activity and rebuilt this system in v2.4 to be timezone-aware. We migrate activity log entries as historical audit records where the destination supports an equivalent audit trail. Timezone handling requires explicit mapping during migration.