Migrate from SP Project Tracker to monday Work Management

SP Project Tracker Projects map to monday.com Boards. Each project name becomes the board name, project description becomes the board description, and project status (active/archived) maps to the board's Archived status. We create boards under a single Workspace or split across Workspaces based on the customer's folder structure in SP Project Tracker. Start and end dates from the project become optional columns on the board for timeline planning.

SP Project Tracker Tasks map to monday.com Items within a Board. Task name becomes Item name, assignee maps to the Person column (resolved via email matching against monday.com team members), due date maps to the Date column, priority maps to a Status column with labels (High, Medium, Low), and completion percentage maps to a Numbers column. We insert all Items before creating subitems to satisfy the parent record dependency.

SP Project Tracker exports subtasks as a flat list with a parent_task_id column rather than as a nested structure. We detect subtask rows by checking for non-null parent_task_id values, group them by parent, then create monday.com Subitems under each parent Item in a second pass. Subitem columns (assignee, due date, status) map identically to top-level Items. We validate the reconstructed hierarchy against the source row count before closing the migration.

Time entries attach to tasks in SP Project Tracker and record hours worked. The destination depends on the customer's monday.com plan: on Pro ($16/seat) we create a native Time Tracking column on each board and populate it with entry-level data; on Standard ($9/seat) we create a Numbers column labeled Total Hours and sum hours per task. SP Project Tracker does not enforce a billable/non-billable flag consistently, so we flag entries with missing billable data for the customer to review before import.

SP Project Tracker stores some attachments as internal URLs valid only within the active session. We request temporary elevated access credentials during the attachment phase, download each file, validate the URL resolves to a downloadable asset, then re-upload to monday.com via the File column. For large attachment volumes (over 1,000 files), we recommend a mirror approach: store files in Google Drive or SharePoint and link them via the Integration column rather than uploading directly to monday.com storage.

Team members are referenced by name and email in SP Project Tracker tasks and time entries. We resolve each to a monday.com user identity using email matching. Any SP Project Tracker assignee without a matching email in monday.com becomes a placeholder entry in our reconciliation queue, and the customer provisions the corresponding monday.com account before record import resumes.

SP Project Tracker task-level comments migrate as monday.com Updates on the corresponding Item. We preserve the author name, timestamp, and comment body as a chronological feed entry. Threaded nesting in SP Project Tracker flattens to a single Update chain in monday.com because monday.com does not support nested reply threads natively.

SP Project Tracker tags are flat labels applied to tasks. We map them to monday.com Tags (universal labels across boards) or a Labels column (board-scoped) depending on the customer's tag usage. Tags containing special characters are converted to slug-safe format during import. We recommend Tags if the customer uses the same label across multiple boards.

SP Project Tracker project-level custom fields are stored as property bags. We extract all key-value pairs, assess each against monday.com's column type options (Text, Number, Date, Person, Status, Dropdown, Link, File), and create the closest matching column type on the destination board. Fields with no monday.com equivalent become a Text column with the original key:value format for manual restructuring.

SP Project Tracker task-level custom fields map to Item columns on the destination board. We create each custom field as a dedicated column before importing Items so that the column exists at insert time. Multi-value custom fields map to Labels or Tags columns; date-formatted custom fields map to Date columns; numeric custom fields map to Numbers columns. The customer reviews unmapped fields during the staging validation pass.

SP Project Tracker project status (Active, On Hold, Completed, Archived) maps to monday.com board state. Active and On Hold map to open boards; Completed maps to a board with all Items marked Done; Archived maps to the monday.com Archived status. We validate that archived boards in monday.com are accessible for read-only recovery if needed.

SP Project Tracker priority values (High, Medium, Low, None) map to a monday.com Status column with color-coded labels (Red for High, Yellow for Medium, Green for Low, Gray for None). If the customer prefers visual tagging over status, we configure a Labels column instead and match the priority value to the corresponding label color.