Migrate your SP Project Tracker data
Lightweight web-based project tracker built for small businesses wanting to move beyond spreadsheets. No native API means migration is export-heavy and manual by default.
In its favor
Why people choose SP Project Tracker
The signal that keeps SP Project Tracker on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Affordable entry point for small businesses that need basic project tracking without the overhead of enterprise PM suites.
Simple, low-complexity interface that team members can adopt without formal training or lengthy onboarding.
Includes task management, time tracking, and team communication in a single tool, reducing reliance on multiple disconnected platforms.
Easy to set up and customize for non-technical users who need a lightweight alternative to spreadsheet-based tracking.
Provides time tracking and reporting capabilities that small teams find sufficient for basic project visibility and billing support.
No documented public API, which blocks automation and forces teams to manually export and re-enter data as the organization scales.
Lacks advanced project management features such as Gantt charts, resource management, or dependency tracking that growing teams eventually require.
Limited collaboration features compared to modern alternatives, leading teams to outgrow the platform as remote and distributed work becomes standard.
Performance or reliability concerns emerge at scale, with some users reporting the platform becomes sluggish with larger project portfolios.
Support responsiveness and product development pace lag behind faster-moving competitors, leaving customers without critical updates or fixes.
Reasons to switch
Why people leave SP Project Tracker
The recurring reasons buyers give for replacing SP Project Tracker. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where SP Project Tracker fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
SP Project Tracker pricing overview
Published pricing is not available in public documentation. The platform is positioned for small-to-midsize businesses and appears to offer a per-user or flat-rate model, but specific tier names and feature gates are not publicly documented. Prospective customers must contact sales directly for a quote.
Per-user monthly subscription
Tier 1 of 3
Custom (per-user/month; published as 'per user monthly subscription' without a specific rate)
What's included
Need help selecting your Project Management?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on SP Project Tracker's schedule — see our quote-based pricing →
What gets migrated
SP Project Tracker object support
Object-by-object support for SP Project Tracker migrations. Per-pair details surface during scoping.
Projects
Mapping requiredProjects are the top-level container. Each project carries a name, description, status, and start/end dates. We preserve project-level custom fields as simple key-value pairs and remap them to the destination's equivalent structure.
Tasks
Mapping requiredTasks are the primary work unit. SP Project Tracker tracks task name, assignee, due date, priority, and completion percentage. Subtasks are not a separate object; they are stored as a flat list with a parent reference. We reconstruct the hierarchy during migration.
Time Entries
Mapping requiredTime entries attach to tasks and record hours worked. The platform does not enforce a billable/non-billable flag consistently. We extract total hours per task and map them to the destination's time-entry or logged-hours field, flagging any entries with missing task associations for correction.
Attachments
Mapping requiredAttachments live at the task or project level. The platform references file URLs or stored blobs. We download each file, attach it to the corresponding record in the destination system, and log any orphaned attachments that cannot be matched to a target record.
Team Members / Users
Mapping requiredTeam members are referenced by name and email in tasks and time entries. We resolve each to a user identity using email matching, creating placeholder users in the destination where no match exists.
Comments
Mapping requiredTask-level comments are stored as threaded notes. We import them as chronological entries on the destination task, preserving the author name and timestamp but not threaded nesting if the target does not support it.
Tags
Mapping requiredTags are flat labels applied to tasks. We map them to the destination's tagging or labeling system, converting any tag containing special characters to a slug-safe format.
Custom Fields
Mapping requiredCustom fields at the project or task level are stored as property bags. We extract all key-value pairs, match them against the destination schema, and create unmapped custom fields as fallback properties with a migration-source annotation.
| Object | Support | Notes |
|---|---|---|
| Projects | Mapping required | Projects are the top-level container. Each project carries a name, description, status, and start/end dates. We preserve project-level custom fields as simple key-value pairs and remap them to the destination's equivalent structure. |
| Tasks | Mapping required | Tasks are the primary work unit. SP Project Tracker tracks task name, assignee, due date, priority, and completion percentage. Subtasks are not a separate object; they are stored as a flat list with a parent reference. We reconstruct the hierarchy during migration. |
| Time Entries | Mapping required | Time entries attach to tasks and record hours worked. The platform does not enforce a billable/non-billable flag consistently. We extract total hours per task and map them to the destination's time-entry or logged-hours field, flagging any entries with missing task associations for correction. |
| Attachments | Mapping required | Attachments live at the task or project level. The platform references file URLs or stored blobs. We download each file, attach it to the corresponding record in the destination system, and log any orphaned attachments that cannot be matched to a target record. |
| Team Members / Users | Mapping required | Team members are referenced by name and email in tasks and time entries. We resolve each to a user identity using email matching, creating placeholder users in the destination where no match exists. |
| Comments | Mapping required | Task-level comments are stored as threaded notes. We import them as chronological entries on the destination task, preserving the author name and timestamp but not threaded nesting if the target does not support it. |
| Tags | Mapping required | Tags are flat labels applied to tasks. We map them to the destination's tagging or labeling system, converting any tag containing special characters to a slug-safe format. |
| Custom Fields | Mapping required | Custom fields at the project or task level are stored as property bags. We extract all key-value pairs, match them against the destination schema, and create unmapped custom fields as fallback properties with a migration-source annotation. |
Gotchas
What to watch for in SP Project Tracker migrations
Issues we've hit on past SP Project Tracker migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
No public API requires export-first migration
Owner assignment drops during bulk CSV export
Attachment URLs become inaccessible after export
Subtask hierarchy flattened in CSV output
| Severity | Issue |
|---|---|
| High | No public API requires export-first migration |
| High | Owner assignment drops during bulk CSV export |
| Medium | Attachment URLs become inaccessible after export |
| Medium | Subtask hierarchy flattened in CSV output |
Leaving SP Project Tracker?
Where SP Project Tracker customers move next
5 destinations SP Project Tracker can migrate to.
How a SP Project Tracker migration works
Four steps, SP Project Tracker-specific
Connect
Inherits SharePoint authentication — Azure AD / Entra ID OAuth 2.0 for Microsoft 365 deployments or NTLM/Kerberos for on-premise SharePoint. SP Project Tracker is implemented as native SharePoint lists and pages rather than a separate SaaS, so there is no dedicated 'SP Project Tracker API' to authenticate against. into SP Project Tracker. Scopes limited to read-only on the data we move.
Map
We translate SP Project Tracker-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate SP Project Tracker quirks before production.
Migrate
Full migration with SP Project Tracker rate-limit handling. Rollback available throughout.
FAQ
SP Project Tracker migration FAQ
Answers to the questions buyers ask most during SP Project Tracker migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your SP Project Tracker migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther project management tools we support
Ready when you are
Migrate SP Project Tracker.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your SP Project Tracker setup and destination — written quote back within a business day.