Migrate from 24SevenOffice to Trello

24SevenOffice Projects map directly to Trello Boards. Project name becomes the board name, description migrates to the board description field, status (active/archived) maps to board visibility (private board for active, archived board for closed), and start/end dates are noted in the board description since Trello boards do not have native date range fields. Milestones within a project are mapped to a dedicated List named Milestones with date-filtered cards. Owner assignment migrates to board membership with the original owner granted Admin-level access.

24SevenOffice Tasks map to Trello Cards on the corresponding board. Parent-child task hierarchy (subtasks) cannot be represented natively in Trello without the Card Growth Power-Up. We map top-level tasks to cards on appropriate Lists (mapped from the task's status column), and subtasks are either flattened into checklist items on the parent card or placed on a Subtasks list at the customer's discretion during scoping. Assignee, due date, estimated hours, and custom task fields migrate to card assignee, due date, and Power-Up custom fields respectively.

24SevenOffice subtasks nested under a parent task are mapped to Trello Checklist items on the parent card. Each subtask's name becomes a checklist item, and subtask assignees, due dates, and completion status map to checklist item metadata where Trello supports it. This is a lossy transformation: Trello checklists do not support due dates per item on the free plan (Premium is required), and nested checklist item hierarchies are not supported. We flag this as a structural limitation and recommend the customer upgrade to Premium or evaluate a Card Growth Power-Up if per-subtask date tracking is required.

Time Entries linked to Projects and Tasks have no native equivalent in Trello. We handle this in two ways based on customer need: entries are appended as a structured text comment on the linked card (showing date, duration, user, and description), or a dedicated Time Tracking checklist is added to the card with entries as checklist items. Neither approach preserves billable/non-billable flags natively. We flag the limitation and recommend pairing with a Trello time tracking Power-Up (Harvest, Toggl, or TimeCamp) for teams that rely on time-to-bill workflows.

24SevenOffice Users map to Trello Workspace Members. We extract active users by email, name, and role from the source API, provision Trello workspace invitations (the customer's admin sends invitations), and resolve owner assignments on Projects and Tasks to the matched Trello member. Users who were deactivated in 24SevenOffice are not migrated; this is by design to keep the destination clean. Role names (Standard tier vs Custom tier role names) are not preserved as Trello has no equivalent role-permission model at the board level.

Custom fields on 24SevenOffice Tasks (dropdown, text, number, date types) migrate to Trello Custom Fields via the Custom Fields Power-Up. Text fields map to Trello text custom fields directly; number fields map to Trello number fields; date fields map to Trello date fields; dropdown fields map to Trello dropdown custom fields with the source options as choices. The Custom Fields Power-Up is required on all Trello plans and is free to install. Custom field labels are preserved verbatim. We note that Trello limits custom field types per card depending on plan; the Standard plan supports all field types but Premium unlocks advanced field types like formula and relation.

File attachments on 24SevenOffice Tasks and Projects are referenced by URL in the source API. We download attachments to temporary storage, then re-upload to the destination Trello card. Trello limits individual file attachments to 250MB per file on Standard and Premium plans. Files exceeding 250MB cannot be attached and are flagged in the reconciliation report. We recommend using Google Drive or Dropbox Power-Up for large file references if the attachment volume is significant.

24SevenOffice Tags applied to Contacts, Companies, and Deals map to Trello Labels on Cards. Each distinct tag becomes a label with a generated color (we cycle through the 25 available Trello label colors when tag count exceeds 25, grouping overflow labels under a generic Misc label). Tags applied at the Contact or Company level (CRM objects not natively present in Trello) are not migrated unless the customer requests a CRM Power-Up such as Commutative or Salesforce for Trello.

24SevenOffice Deals and Pipeline stage values have no native equivalent in Trello's data model. We handle Deals as a structured Card migration to a dedicated Deals board with Lists representing pipeline stages (Prospecting, Qualification, Proposal, Negotiation, Closed Won, Closed Lost). Deal value migrates to a number custom field on the card; deal owner becomes card member; and deal name becomes card title. Stage mapping is applied from the 24SevenOffice pipeline schema to the new Trello Lists. We flag that this is a lossy representation: deal probability, weighted revenue, and multi-touch attribution have no home in Trello and require manual reconciliation post-migration.

24SevenOffice Contacts (CRM) cannot map to a native Trello object since Trello has no contact management module. We offer two options: contacts referenced as card members if the contact is also a Trello workspace user, or contact details (name, email, company, phone) appended to the card description as a structured text block. CRM lifecycle stage and owner assignment are not preserved in Trello. We recommend the customer evaluate a CRM Power-Up for Trello (Commutative, Salesforce, or Pipedrive integration) if ongoing CRM data needs to live alongside project management.

24SevenOffice Company records map to a text block in the destination Trello card description, similar to Contact mapping. Company name, industry, size, and address are included. Trello has no company or account object, so this data is denormalized into card-level text. We recommend the customer maintain 24SevenOffice (or a dedicated CRM) for ongoing CRM records and use Trello exclusively for project and task management if the CRM layer is critical to operations.

24SevenOffice Invoices, Accounts Payable, and Accounts Receivable records carry country-specific tax codes, chart of accounts structures, and payment terms that have no equivalent in Trello. Trello has no invoice, AP, or AR object. We do not migrate these records. For customers who rely on 24SevenOffice for accounting, we recommend maintaining 24SevenOffice for the finance module and migrating only the PM layer to Trello, resulting in a dual-system workflow where project tasks live in Trello and billing remains in 24SevenOffice.

24SevenOffice workflow rules and notification automations do not migrate as code. Trello Butler operates on its own trigger-action model (board-level or card-level commands) that is architecturally distinct from 24SevenOffice's module-based workflow rules. We deliver a written inventory of every active 24SevenOffice automation with its trigger, conditions, and actions, plus a recommended Butler equivalent for the customer's admin to configure post-migration. Complex automations with conditional branching or external API calls may require Butler Power-Ups or a third-party automation tool (Zapier, Make).