Migrate your TaskRay data

The root container object. Projects support custom fields, file attachments, and Chatter threads. We export and import TaskRay__Project__c records using Salesforce REST or Bulk API. Project-level settings such as archiving state and template associations are preserved. We re-map the Field Trickler Account and Opportunity lookups at the project level during import.

Intermediate grouping object that rolls up into Projects. Task Groups can represent phases or themes within a project plan. We preserve the Task Group-to-Project parent linkage during migration and re-apply ordering if it is stored as a sequence field on the record.

The core work unit, assigned to Resources with due dates, statuses, and Checklist containers. We migrate task records including custom fields, blocked/locked states, repeating flags, and predecessor dependency references. Checklist Items are migrated as child records of their parent Task.

Child records that roll up to a parent Project. Sub-Projects carry the same field structure as top-level Projects and can contain their own Task Groups and Tasks. We preserve the parent-project lookup to maintain the full hierarchy chain.

Single-day tasks visually rendered as diamond icons in Plan View. Milestones are a distinct Task record type in TaskRay. We identify and migrate them separately so their milestone flag and date are preserved in the destination org.

TaskRay exposes custom fields on Project, TaskGroup, and Task objects through standard Salesforce field management. We detect and migrate all custom fields but require a field-mapping pass because custom field names and data types vary per org. Boolean picklists and date fields map cleanly; complex multi-select picklists may need value remapping.

Each task can hold a Checklist container with granular Checklist Items tracking sub-todo states. We migrate Checklist Items as child records under their parent Task, preserving completion status and ordering.

TaskRay stores files on the Salesforce ContentDocumentLink model, accessible via standard Salesforce file APIs. We export files attached to TaskRay records and re-attach them at the corresponding record in the destination org. Very large files may be constrained by Salesforce storage limits.

Dependencies between Tasks are tracked via predecessor/successor links on the TaskRay Task object. We preserve these references and validate them after migration to avoid dangling predecessor links when source tasks are absent in the destination.

Template Projects and the Template Builder feature allow reusable project skeletons. Templates are standard Salesforce records and are migratable, but the Template Migration feature (Premium-only) must be manually replicated in lower tiers. We flag this difference during scoping.

Resources represent individual users who own and complete work. Roles describe job functions and serve as placeholder owners. We map Resources to Salesforce Users in the destination org, matching by email or username. Role-based placeholder ownership requires reconfiguration post-migration if the destination org uses different role naming.

Capacity is calculated from Availability and Utilization and is only available on the Premium tier. Capacity data is stored as custom fields on Resources and is migratable, but the Dynamic Team Builder visualization does not carry over automatically and must be reconfigured.

TaskRay provides Basic Reports and Basic Dashboards on Starter, with more advanced reporting on higher tiers. Reports are Salesforce report records and are migratable via Salesforce API, but custom report types and dashboard snapshots require reconfiguration and permission sharing adjustments in the destination org.