Migrate from Rocketlane to Trello

Rocketlane Projects map directly to Trello Boards. Project name, description, start date, and end date transfer to the Board name, description, and optional deadline field (via Calendar Power-Up or manual date in card titles). Project status (active, on hold, completed) does not have a native Trello equivalent — we map active to the Board existing, on hold to a dedicated list label, and completed to archiving the Board post-migration. Multi-workspace Rocketlane accounts require a decision on Board organization (one Board per project vs grouped Boards per workspace).

Rocketlane Phases within a Project map to Trello Lists within the target Board. Phase name becomes the List name, and Phase start/end dates are noted in the List description or in a pinned card. Phase order is preserved by List ordering in Trello. If a Rocketlane project has more than one Phase with overlapping dates, all Lists are created at the top level of the Board — Trello does not support nested or parallel Lists natively. Phase dependencies (one phase blocking another) have no Trello equivalent and are noted in the migration handoff documentation.

Rocketlane Tasks map to Trello Cards within the corresponding List (derived from Phase mapping). Task name becomes Card title, description migrates to Card description in plain text, due date migrates to Card due date, and assignee maps to Card member (resolved by email against Trello Workspace members). Task priority (Low/Medium/High) maps to Card labels with color-coded label names. Task status (todo/in-progress/complete) maps to List position: incomplete tasks go to the List representing their Phase, and completed tasks go to a 'Completed' List at the end of the Board.

Rocketlane Subtasks are represented as checklist items within a Task and map directly to Trello Card checklists. Checklist item text, completion status, and assignee migrate. Nested subtask hierarchies (subtask of a subtask) flatten to a single-level checklist in Trello. Cards with more than 100 checklist items may require splitting into multiple cards or using the Card Size Power-Up; we flag these during scoping.

Rocketlane Documents (rich text with panels, approval workflows, and freeze states) cannot migrate natively to Trello Cards. We extract document body text and rebuild it as Card description or as a linked attachment (PDF extracted from Rocketlane export). Approval history, comments, freeze/unfreeze states, and panel structures do not transfer. Customers who rely on document approval workflows should treat this as a business-process gap and plan for manual re-approval or an alternative document management process post-migration.

Rocketlane custom fields on tasks (SINGLE_CHOICE, MULTIPLE_CHOICE, TEXT, DATE, NUMBER, USER) require the Trello Custom Fields Power-Up at the destination. We enumerate all custom field definitions during scoping and map them to Power-Up field types: SINGLE_CHOICE maps to Dropdown, MULTIPLE_CHOICE maps to Multiple Select, TEXT maps to Text, DATE maps to Date, NUMBER maps to Number. Fields that cannot be represented (RATING on project fields) are noted as unsupported. Customers on Trello Standard plan can use the Custom Fields Power-Up; Free tier users must use labels or card titles as a workaround.

Rocketlane Users and Members map to Trello Workspace members. We resolve by email match. Guest accounts (Rocketlane Clients with portal-only access) require a decision: they can be invited as Workspace members (if on a Trello paid plan) or excluded and noted in the handoff. Inactive Rocketlane users are not invited to Trello unless they have open task assignments, in which case their tasks are reassigned to the project owner during migration.

Rocketlane Clients are external stakeholders with portal access distinct from team Members. Trello has no native client portal equivalent. We map Clients to Trello Workspace members if the destination is on a Standard+ plan (which allows guest members), or we tag their project involvement with a 'Client' label on the Board for visibility. Client-specific comments and portal activity do not migrate. This is a structural gap that requires manual client re-onboarding at Trello.

Rocketlane Spaces provide the client-facing workspace within a Project containing a shared timeline, document library, and activity feed. Trello has no native Space or client portal equivalent. We map Space associations to the Board with a 'Client-facing' label and a note in the Board description. If client access is required, we recommend Trello Standard or Enterprise guest member invitations with Board-level permissions; this is a manual configuration step post-migration.

Rocketlane Project templates and document templates define reusable project blueprints. Template content migrates as Board content (Lists and Cards) but template-level settings (default assignees, pre-populated phases, default due dates) do not transfer. We document the template structure in the migration handoff so the customer's admin can create Trello Board Templates manually from the migrated Boards. Document templates are excluded as noted in the Document mapping.

File attachments on Rocketlane Tasks and Documents are downloaded and re-uploaded to the corresponding Trello Card. We preserve the original filename and the linked task association. Attachments exceeding Trello's size limits (10 MB on Free, higher on paid plans) are flagged for the customer's admin to handle via cloud storage links. Attachments on completed or archived Cards are attached to those Cards regardless of status.

Rocketlane Time Entries (available on Premium and Enterprise plans) linked to Tasks do not have a native Trello equivalent. Time tracking requires a Power-Up (Time Tracking by Bluefeather, or similar) that is not included in standard Trello plans. We document every time entry with its task association, hours logged, and date in a migration handoff CSV. Customers who rely on time tracking for billing or utilization should install a time tracking Power-Up before migration and configure it post-migration; we do not install Power-Ups as part of standard migration scope.

Rocketlane Automations (property-triggered workflows gated by plan tier) do not migrate to Trello Butler as executable rules. Butler uses a different rule model (card triggers, list triggers, board triggers, due date triggers) that is not structurally compatible with Rocketlane's property-based conditions. We deliver a written inventory of every active Rocketlane Automation with its trigger, conditions, and actions, mapped to a recommended Butler equivalent where one exists. The customer's admin rebuilds Butler rules post-migration.

Rocketlane Forms (project intake, client onboarding) do not migrate. We document form field names and conditional logic in the migration handoff for the customer's admin to rebuild using Trello forms (native in Standard+) or a third-party form tool (JotForm, Typeform) linked to Trello via Power-Up or Zapier. Form submission history does not transfer.