Migrate your WeTrack data
Event delivery and operations platform for major sporting events, federations, and venues. Built for complex multi-project, multi-stakeholder delivery cycles with Planning, Risk, and Sustainability modules.
In its favor
Why people choose WeTrack
The signal that keeps WeTrack on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Built specifically for major multi-stakeholder events like Wimbledon and Expo 2020, giving venue operators and event teams a purpose-built platform rather than a generic project management tool.
Combines Planning, Sustainability, Risk, and Operations modules in one platform, reducing the need for multiple disconnected tools across a large event programme.
Acquired by Momentus Technologies in 2023, giving the platform a deeper pool of venue management expertise and long-term product investment.
Mobile-first design allows field teams to access planning, operational, and sustainability modules on any device, which is critical for distributed event delivery teams.
Template risk registers use industry-standard Inherent Likelihood/Impact terminology that aligns with enterprise risk management frameworks.
Limited third-party integration flexibility, with one reviewer noting the platform should allow more seamless integration with external tools.
Low review volume and sparse public documentation make it difficult to assess the platform's current state and roadmap before committing.
The platform's niche focus on major events means small teams or organisations running fewer, smaller projects may find the feature set over-engineered for their needs.
Post-acquisition by Momentus Technologies, some existing customers report uncertainty about pricing changes and support continuity.
Reasons to switch
Why people leave WeTrack
The recurring reasons buyers give for replacing WeTrack. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where WeTrack 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
What gets migrated
WeTrack object support
Object-by-object support for WeTrack migrations. Per-pair details surface during scoping.
Projects
Fully supportedProjects are the top-level container in WeTrack's data model, holding Tasks, Subtasks, and associated metadata including date ranges and status fields. We map them 1:1 to the destination project object, preserving custom fields and owner assignments.
Tasks
Fully supportedTasks belong to Projects and carry date fields, status, and RAG indicators. We map standard task fields directly; subtasks are handled as nested child records under the parent task relationship.
Subtasks
Mapping requiredSubtasks are linked to parent Tasks with auto-sync behavior on dates. We preserve the parent-child linkage during migration and flag any subtasks that may have conflicting date logic in the destination system.
Attachments
Mapping requiredAttachments of all types are supported via a three-dot menu in the UI. We map file metadata and references; actual file content depends on whether the destination has an equivalent attachment storage mechanism.
Risk Registers
Mapping requiredRisk Registers use industry-standard Inherent Likelihood and Impact terminology in template risks. We preserve RAG values and risk owner assignments, mapping them to the destination's risk or issue object with custom fields where needed.
Job Categories
Mapping requiredJob Categories restrict valid options to prevent data errors. We map category values and flag any categories that have no equivalent in the destination schema for manual reassignment.
RAG Status Fields
Mapping requiredRAG updates run on predictable schedules and cascade from parent tasks to subtasks. We preserve the RAG state values and note that some destination systems may not have a native RAG equivalent, requiring a custom field mapping.
Sustainability/ESG Records
Mapping requiredThe Sustainability module tracks ESG indicators. We map these records and their associated metric values; destination systems may require a custom object or extended fields to accommodate ESG data.
Incident Reports
Mapping requiredIncident Reports are operational records that may not have a direct equivalent in general-purpose PM tools. We map them to the destination's closest risk, issue, or ticket object and flag any metadata that requires custom field mapping.
Users and Owners
Mapping requiredUser accounts and task owners are referenced by ID. We map user records and their assignments, flagging any inactive or orphaned users that may need to be deactivated or reassigned in the destination.
Custom Fields
Mapping requiredWeTrack supports custom fields on Projects and Tasks. We map these as key-value pairs or extended properties depending on what the destination schema supports, flagging any that exceed the destination's field type constraints.
| Object | Support | Notes |
|---|---|---|
| Projects | Fully supported | Projects are the top-level container in WeTrack's data model, holding Tasks, Subtasks, and associated metadata including date ranges and status fields. We map them 1:1 to the destination project object, preserving custom fields and owner assignments. |
| Tasks | Fully supported | Tasks belong to Projects and carry date fields, status, and RAG indicators. We map standard task fields directly; subtasks are handled as nested child records under the parent task relationship. |
| Subtasks | Mapping required | Subtasks are linked to parent Tasks with auto-sync behavior on dates. We preserve the parent-child linkage during migration and flag any subtasks that may have conflicting date logic in the destination system. |
| Attachments | Mapping required | Attachments of all types are supported via a three-dot menu in the UI. We map file metadata and references; actual file content depends on whether the destination has an equivalent attachment storage mechanism. |
| Risk Registers | Mapping required | Risk Registers use industry-standard Inherent Likelihood and Impact terminology in template risks. We preserve RAG values and risk owner assignments, mapping them to the destination's risk or issue object with custom fields where needed. |
| Job Categories | Mapping required | Job Categories restrict valid options to prevent data errors. We map category values and flag any categories that have no equivalent in the destination schema for manual reassignment. |
| RAG Status Fields | Mapping required | RAG updates run on predictable schedules and cascade from parent tasks to subtasks. We preserve the RAG state values and note that some destination systems may not have a native RAG equivalent, requiring a custom field mapping. |
| Sustainability/ESG Records | Mapping required | The Sustainability module tracks ESG indicators. We map these records and their associated metric values; destination systems may require a custom object or extended fields to accommodate ESG data. |
| Incident Reports | Mapping required | Incident Reports are operational records that may not have a direct equivalent in general-purpose PM tools. We map them to the destination's closest risk, issue, or ticket object and flag any metadata that requires custom field mapping. |
| Users and Owners | Mapping required | User accounts and task owners are referenced by ID. We map user records and their assignments, flagging any inactive or orphaned users that may need to be deactivated or reassigned in the destination. |
| Custom Fields | Mapping required | WeTrack supports custom fields on Projects and Tasks. We map these as key-value pairs or extended properties depending on what the destination schema supports, flagging any that exceed the destination's field type constraints. |
Gotchas
What to watch for in WeTrack migrations
Issues we've hit on past WeTrack migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
No publicly documented API endpoint reference
Post-acquisition product positioning is unclear
Custom fields may not be exportable via standard reports
| Severity | Issue |
|---|---|
| High | No publicly documented API endpoint reference |
| Medium | Post-acquisition product positioning is unclear |
| Medium | Custom fields may not be exportable via standard reports |
Leaving WeTrack?
Where WeTrack customers move next
5 destinations WeTrack can migrate to.
How a WeTrack migration works
Four steps, WeTrack-specific
Connect
Not publicly documented. WeTrack (now part of Momentus Technologies) does not publish a developer portal or public OAuth flow. Customer-specific integrations are scoped through the WeTrack/Momentus integration team. into WeTrack. Scopes limited to read-only on the data we move.
Map
We translate WeTrack-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate WeTrack quirks before production.
Migrate
Full migration with WeTrack rate-limit handling. Rollback available throughout.
FAQ
WeTrack migration FAQ
Answers to the questions buyers ask most during WeTrack migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your WeTrack 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 WeTrack.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your WeTrack setup and destination — written quote back within a business day.