Migrate from PROAD to Trello

PROAD Projects map directly to Trello Boards, with the project name becoming the board title, the project description as the board description, and the project status (active, archived) reflected by whether the board is live or archived. Start and end dates transfer as board metadata or as custom fields on the board if Trello Business Class or Enterprise is in use. Each PROAD project generates one Trello board; the customer's admin decides whether to create boards within a single workspace or distribute across multiple workspaces during scoping.

PROAD Subprojects do not have a native Trello equivalent — Trello has no hierarchical container between Board and List. We represent each Subproject as a parent Card with a title prefixed by a scoping-agreed convention (such as [Subproject] or the original subproject name in bold), and all Tasks within that Subproject become subtasks (checklist items) of that parent card. A Custom Field named 'Subproject' stores the original subproject name so that it can be surfaced on every child card. This preserves the relationship context that would otherwise be lost in a flat card structure.

PROAD Client records contain company-level information and a primary contact. These split into Trello Organization (for the company entity) and a member-level Contact attached to that Organization. The Organization name, website, and address fields map directly. The primary client contact email migrates as the Organization admin invite email. Additional contact details from PROAD custom fields on Client records map to Organization custom fields or member profile fields.

PROAD Tasks are the granular work units within Subprojects. Each Task becomes a Trello Card, with the task name as the card title, task description as the card description (markdown preserved), due date mapping from the task's due date field, and assignee mapping from the PROAD user assignment to Trello card members. Priority from PROAD maps to a custom Priority label (High, Medium, Low) on the card. Task comments migrate as card comments with the original author and timestamp preserved.

PROAD Milestones are standalone date markers with names and completion status tied to the project timeline. Trello has no native milestone object, so we represent milestones as Cards with titles prefixed to indicate milestone status (such as [Milestone] or [Completed Milestone]), with the milestone target date set as the card due date. Milestone completion status is stored as a custom label or a 'Milestone Status' custom field. If multiple milestones share a single target date, we create one milestone card and add the milestone names as a checklist so the grouping is preserved.

PROAD Time Entries carry hours logged, the associated task or project, user attribution, billable flags, and per-user or per-project rate settings. Trello has no native time entry object, so we migrate hours logged and billable flags as Custom Fields on the Card (using the Custom Fields power-up, which requires Trello Business Class or above). For billing rate data, we generate a CSV attachment per card or per board listing the time entry details (date, hours, rate, total) and link it in the card description so the billing context is preserved without requiring a power-up upgrade. We flag during scoping whether the destination account has the Custom Fields power-up available.

PROAD Tickets are issue requests linked to Clients or Projects with status, priority, and conversation history. We create a dedicated Trello board for migrated tickets and represent each ticket as a Card with status mapped to the board's list structure (typically Open, In Progress, Waiting, Resolved, Closed). Priority migrates as a card label. Conversation history migrates as chronological card comments with the original responder and timestamp. The original PROAD parent-project or parent-client linkage is stored as a 'Source Project' custom field on the card so the association is recoverable.

PROAD user accounts map to Trello workspace members by email address. We extract all distinct PROAD users referenced as task assignees, ticket owners, or time-entry loggers and match them against the destination Trello workspace membership. Any PROAD user without a matching Trello member invitation goes to a reconciliation queue for the customer's admin to provision. Role and permission data from PROAD does not map to Trello roles because Trello's permission model is workspace-wide and board-level rather than object-level.

PROAD custom fields on Projects, Tasks, and Contacts migrate to Trello Custom Fields where the destination board has the Custom Fields power-up enabled (Business Class or Enterprise required). PROAD field names are truncated to Trello's 25-character limit and validated against supported types (text, number, date, dropdown, checkbox). Unsupported PROAD field types (such as formula fields or multi-select without equivalent) convert to text fields with an advisory in the mapping notes. Fields on Projects that have no natural card-level home migrate as board description annotations.

PROAD tags on Projects, Tasks, and Contacts migrate to Trello Labels on the corresponding board or card. We normalize tag names during the transform step to eliminate duplicates introduced by inconsistent casing or spacing in PROAD — for example, 'Client反馈' and 'client反馈' merge into a single label. Label color assignments are generated from a deterministic hash of the tag name to ensure consistent coloring across boards without requiring manual color mapping.

PROAD's accounting and KPI dashboard data (financial summaries, budget totals, utilization metrics) has no native Trello equivalent. We export the KPI summary as a structured CSV or PDF attachment on the project board or project-level card, preserving the metric names, values, and reporting period. Detailed ledger entries or granular accounting records are flagged as out of scope for the standard migration pass; we recommend a separate accounting-focused migration or export if the customer requires the full financial history in a structured format.

File attachments on PROAD Tasks, Projects, and Tickets migrate as card attachments in Trello. We flag attachments exceeding 10 MB during the audit phase because Trello attachment handling at scale can be memory-intensive during migration. Large file sets are migrated in batches with a pause between boards to avoid rate-limit throttling. If an attachment references a URL from an external system that is no longer accessible, we note it as a broken link in the migration reconciliation report.