Migrate from Allegra to Trello

Allegra Items are the primary record type and map 1:1 to Trello Cards. We query the Allegra schema endpoint to retrieve all item attributes and values, then create Trello Cards via POST /1/cards with name, desc (from Allegra description attribute), and due dates mapped from Allegra date attributes. Each Allegra Item becomes a Trello Card placed in the List corresponding to its Allegra workflow status or project assignment. Parent-child item relationships from Allegra (sub-items) map to Trello Card attachments or checklist parent-child structure depending on the customer's preference.

Allegra item attributes (item-native properties) map to Trello Custom Fields. Custom Fields are a Premium and Enterprise feature in Trello; for Standard-tier destinations, we map text attributes to the card description (desc) and flag unsupported types in the inventory. We discover all attribute definitions via the Allegra schema endpoint before creating corresponding Custom Field definitions in Trello. Date, number, and select-type attributes become typed Custom Fields; long-text attributes migrate to the card description with a header noting the original attribute name.

Allegra Form Fields belong to input forms rather than items, which requires a separate discovery step. We extract the form-field definitions separately from item attributes via GET /v2/forms and map each field to a Trello Custom Field or to the card description. Form-field picklist values map to Trello Custom Field options. If the form field references a Custom List, we resolve that lookup and map to the corresponding Trello Label.

Allegra attachments reside in the ALLEGRA_HOME filesystem, not the database. We export the entire attachments directory simultaneously with the database export, preserving the directory structure and item-to-file mapping from the Allegra database records. We upload each file to Trello via POST /1/cards/{id}/attachments using the Trello REST API. Files are stored in Atlassian's S3-backed cloud storage. We validate attachment integrity (checksum) before upload and flag any files that exceed Trello's 10 MB per-attachment limit for customer action before migration.

Allegra Custom Lists with list entries accessible via GET /v2/lists map to Trello Labels. We retrieve all Custom List definitions and their entries via the Allegra REST API, then create Trello Labels with names matching the list entry values. Label colors are assigned automatically by Trello or optionally mapped from Allegra color attributes if present. A Custom List entry used as a lookup on an Allegra Item attribute becomes a Label filter on the Trello Card.

Allegra Users and Roles are exported from the Allegra database and mapped to Trello Members. We match by email address. If a Trello Member account does not exist at migration time, we hold the user in a reconciliation queue and the customer provisions the Trello account before record assignment proceeds. Role-based permissions from Allegra (Viewer, Editor, Manager) are noted in the Trello Member invite inventory for the customer to reassign at their discretion; Trello permission management is workspace-level rather than item-level.

Allegra supports MS Project file import with task recognition, storing tasks as Allegra Items with hierarchy metadata. When the source Allegra instance has imported MS Project files, we parse the task hierarchy, dependencies, start dates, and end dates. We map each MS Project task to a Trello Card with a Checklist that includes task name, start date, end date, duration, and percent complete as checklist items. Summary tasks from MS Project become parent Cards with child Cards for sub-tasks. MS Project task dependencies are noted in card descriptions as Trello does not natively support task dependency visualization.

Allegra Item comments are extracted from the database and ingested into Trello Cards via POST /1/cards/{id}/actions/comments. Comment authorship (user) is preserved as the Trello comment author by matching the Allegra user to the migrated Trello Member. Comment timestamps are preserved by setting the comment date to the original Allegra timestamp. Rich-text comments are rendered as plain text in Trello comments with HTML stripped to Trello-supported formatting.

Allegra Item checklists (if present as a custom attribute type) map directly to Trello Card checklists. We discover checklist definitions from Allegra's attribute schema, then create Trello Checklists via POST /1/cards/{id}/checklists with checklist items preserving name, completion status, and assignee if available. Checklist item order is preserved from Allegra's sequence.

Allegra workflow statuses and project assignments define the state progression for Items. We discover the full set of workflow status values from the Allegra schema and map each distinct status to a Trello List within the target Board. The customer defines the board structure during scoping (one board per Allegra project, or a unified board with Lists per status). Trello List names are created to match Allegra status names exactly, preserving the workflow sequence as the List ordering.

Allegra Projects group Items, Custom Lists, and workflow statuses. Each Allegra Project maps to a Trello Board. We export the project hierarchy, project description, project start and end dates, and project members. Board members are set to the corresponding Trello Members. Project metadata is stored in the Board description field. If the customer has multiple Allegra Projects, we create one Trello Board per Project with the option to consolidate into a workspace with multiple boards.

Allegra automations and workflows cannot migrate to Trello as code because Butler uses a different trigger-action model. We do not migrate workflows. We audit every Allegra workflow and automation during discovery, document its trigger conditions and actions in a written Butler rebuild guide, and deliver this to the customer at cutover. The customer or a Trello partner rebuilds automations in Butler or selects equivalent Power-Ups post-migration.

Allegra reporting and dashboard configurations do not have a direct Trello equivalent. Trello's reporting is limited to board-level activity and card counts. We do not migrate reports as code. We deliver a written inventory of every Allegra report with its definition, filters, and chart type, and the customer rebuilds them in Trello-compatible formats (using Power-Ups like Corrello, Screenful, or native Trello workspace views) post-migration.