Migrate from AceProject to Trello

AceProject Projects map directly to Trello Boards. We export project name, description, status (Active/Completed/On Hold), start date, and end date via the admin Export Data tool. Project status maps to Board visibility (Active maps to Private or Team Board; Archived maps to Closed Board state). If the AceProject account has multiple Projects with overlapping names, we apply a naming prefix or suffix to prevent board name collision in Trello.

AceProject Tasks map to Trello Cards. Each Task becomes a Card in a designated List (default List name is derived from the Task's status field or a configurable 'To Do / In Progress / Done' list mapping). Task name becomes Card title, description maps to Card description, Assignee maps to Card members, Due Date maps to Card due date, and Priority maps to Card label color. Custom task fields (Boolean, Date, List, Numeric, Text, User) map to Trello Custom Fields Power-Up field types. AceProject's new-interface requirement for custom field visibility applies — we verify which interface version was used during export.

AceProject Subtasks have no direct Trello equivalent and are represented as Checklist items on the parent Card. We flatten the task-subtask tree during export, generating one parent-child pair per subtask, then reconstruct them as Checklist items with the checklist name matching the parent task name. Checklist item completion state (Done/Pending) maps from Subtask status. This approach preserves the work breakdown without creating separate Card records for each subtask. Nested subtasks (sub-subtasks) are flattened to one level of Checklist item to stay within Trello's single-level checklist structure.

Trello has no native time tracking object. We represent AceProject time entries as custom fields on the parent Card: a Number custom field for hours logged, a Date custom field for the entry date, and a Text custom field for billing rate or notes. Multiple time entries against a single task are aggregated into summary custom fields (total hours, total billing amount) since Trello cards support only one value per custom field. If the customer licenses a time tracking Power-Up (Time Tracking by Bluefeet or Corenuts), we configure that Power-Up instead of custom fields and import entries as tracked time.

AceProject expense records are tied to Projects and optionally Tasks. We map expense data to Trello custom fields on the relevant Card: a Number field for amount, a Text field for currency, a Text field for expense category, and a Date field for expense date. Expense records gated by AceProject user role (non-admin users may not see expense fields) require the export to run under an administrator account — we confirm admin access during scoping. If the customer has high-volume expense data, we may recommend a separate Expenses Board in Trello with one Card per expense, linked back to the source project Card via a label or checklist reference.

AceProject Users are exported at the account level with their name, email, and custom User fields. We create Trello member accounts by email invitation and map the AceProject user to the Trello member. User custom fields migrate to Trello member profile fields if the customer's Trello Enterprise plan supports them; otherwise they are stored as a written reference for manual entry. AceProject's project membership gating applies: imported users do not automatically become Board members — we generate a Board invitation list during migration and the customer's admin sends invitations or bulk-adds members post-migration.

AceProject User-level custom fields (Boolean, Date, List, Numeric, Text, User type) are exported as key-value pairs. We map User-type custom fields to Trello Card member fields (assigning the referenced user as a Card member) and other types to Text or Number custom fields on the Card. If a User-type custom field references a user not yet invited to the Trello workspace, we flag the unresolved reference in the scoping report and hold that mapping until the user is provisioned.

AceProject task dependencies with type (Finish-to-Start, Start-to-Start, etc.) and linked Task ID do not have a native Trello equivalent. Trello has no built-in dependency or blocking relationship between cards. We export the full dependency graph from AceProject, produce a written dependency map document (card A blocks card B, card C depends on card D), and recommend a Power-Up (Planyway, Card Dependencies, or Project Management for Trello) for rebuilding the dependency logic in Trello. The migration does not install or configure the Power-Up — we deliver the reference documentation for the customer's admin to implement post-migration.

AceProject documents are associated with Projects and carry metadata (filename, upload date, author, file size). We export document metadata and file references. If the destination Trello workspace uses a connected cloud storage service (Google Drive, Dropbox, OneDrive/SharePoint via Power-Up), we map document references to external links on the Card. Direct file attachment migration depends on file size limits and cloud storage configuration — we flag any documents exceeding Trello's 10MB per-attachment limit and recommend a cloud link strategy instead.

AceProject task comments and document comments are exported as text with author and timestamp. Trello cards have a single description field and a Card Activity log (accessible via premium), but no native comment thread on cards without Power-Ups. We append comments as a formatted block in the Card description (commenter name, timestamp, comment text) to preserve the content. If the customer licenses a commenting Power-Up (such as GitHub-style comments or a third-party card comment tool), we note the mapping for that Power-Up configuration. Nested comment threads are flattened to maintain chronological order without thread hierarchy.

AceProject task priority levels (Urgent, High, Normal, Low) map to Trello Card labels. We configure label colors in the target Board to match the AceProject priority schema: e.g., Red for Urgent, Orange for High, Yellow for Normal, Green for Low. If the AceProject account uses a custom priority label set, we align Trello label colors to the customer's existing convention during Board setup.

AceProject task statuses (Not Started, In Progress, Completed, On Hold, Cancelled) map to Trello Lists within each Board. We configure Lists per Board based on the AceProject workflow states present in the source data. If AceProject uses a custom status workflow per project, we create a corresponding list configuration per Board. Tasks with status Completed are placed in the configured 'Done' or equivalent list; cancelled tasks are placed in a separate 'Cancelled' list or closed (archived) in Trello based on the customer's preference.