Migrate from web2Project to monday Work Management

web2Project Projects map to monday.com Boards. Each web2Project project name, description, color tag, start date, end date, priority, and project owner (assigned user) migrate as Board metadata. We extract project settings directly from MySQL and create the Board via the monday.com API, preserving the project status as a Board state. Multiple web2Project projects map to separate monday.com Boards within a shared Workspace.

web2Project Tasks map to monday.com Items on the target Board. Task name, description, start date, end date, priority, percent complete, and assignee migrate as Item column values. web2Project's parent-child task hierarchy maps to monday.com subtasks within the parent Item. Task status (task_log.proj_task_priority, task_status) maps to a Status column on the Board with values defined during schema design.

web2Project inter-task dependency records (task_dependencies table) map to monday.com's Dependency column between Items. We preserve the dependency type (Finish-to-Start, Start-to-Start, etc.) where supported and use monday's auto-scheduling feature to recalculate downstream Item dates based on the resolved dependencies after migration.

web2Project user accounts (username, email, role, active/inactive status) map to monday.com Workspace members. We resolve users by email match against the monday.com destination account. Any web2Project user without a matching monday.com account is held in a reconciliation queue for the customer's admin to provision before Board assignment migration begins.

web2Project Companies (organizational entities distinct from departments) map to monday.com Teams within the Workspace. Company name, address, phone, and primary contact migrate as Team metadata. If the customer uses monday.com's Contact Boards (CRM features) on higher tiers, Company records can optionally map to a Contacts Board.

web2Project Departments are sub-organizational units within Companies and map to monday.com Team subgroups or Board-level Groups. The department hierarchy is preserved as Board Groups with names matching the source department structure. If web2Project departments span multiple companies, we map them to Teams in monday.com and attach the relevant Boards per department assignment.

web2Project v2.4 custom fields (text, number, date, dropdown, checkbox) map to monday.com custom column types. The v2.4 schema uses SOLID OOP store and delete methods, and we detect the pre-v2.4 versus post-v2.4 field format during database inspection to avoid type mismatches. Dropdown custom fields map to monday.com Dropdown or Tags columns; checkbox fields map to Checkbox columns; date fields map to Date columns with timezone normalized to UTC during extraction.

web2Project Gantt chart task dates, durations, and dependencies migrate as the underlying data driving monday.com's Timeline view. We do not migrate the rendered Gantt visualization itself — the Gantt is a rendering of task start/end dates and dependencies that we map to the Timeline column on the Board. The Timeline view is available on Standard and above plans.

web2Project calendar events and task-based iCalendar entries migrate to monday.com Items with Date column values populated from the event start/end timestamps. Event title and description map to Item name and description. All timestamps are normalized to UTC during extraction and mapped to the destination Workspace timezone setting.

web2Project project forums (thread categories and thread metadata) migrate to monday.com Board-level documentation or Item Updates. Forum post content migrates as Updates on the related Items (Projects/Boards). Note that the flat threaded structure of web2Project forums does not map natively to monday's chronological Updates; we flatten threads into sequential Update entries to preserve the conversation content without reconstructing the nested reply structure.

web2Project file attachments (file references and metadata at project and task level) migrate as file attachment metadata linked to the corresponding Items. Actual file content (uploaded documents, PDFs, images) requires a separate file transfer step coordinated alongside the database migration. We map file names, original upload timestamps, and uploader references; the customer executes the physical file copy to monday.com Drive or the connected file storage integration.

web2Project budget fields are explicitly documented as documentation-only and are not used for tracking, evaluation, or reporting in the source platform. We migrate the values as read-only text fields on the Board or Item in monday.com. Any actual budget tracking must be re-implemented in monday.com using a numeric column, a connected spreadsheet integration, or a third-party budgeting tool. We flag this explicitly in the scope document before migration begins.