Best-practice architecture for scaling a heavily automated Trello system?

[Prestige Bot]

We use Trello Premium to run a growing business. We currently have approximately 5–7 operational users, up to seven leadership users, roughly 50 boards, and a very high volume of automation.

Our present setup grew organically:

• One shared company account administers or owns most of the Workspaces and boards.

• A separate company-controlled “bot” account created most of our automations.

• A central macro-workflow board drives work into departmental boards such as Office, Shop, and Installs.

• Changes to cards and checklists trigger downstream cards, checklists, and personal assignments.

• Completing downstream work advances cards on departmental and macro-workflow boards, which can trigger the next stage.

• We currently use copied, linked, and mirrored cards to create breadcrumbs and pass progress between boards.

This system works, but it has become difficult to navigate and troubleshoot. Finding boards, locating the automation responsible for a particular action, managing permissions, and understanding dependencies are all becoming increasingly cumbersome.

Our desired outcome

We want to redesign the system so that:

• Everyone signs in through an individual, company-managed account.

• Operational users see only the work relevant to them, ideally through one clear and properly prioritized work surface.

• Employees can maintain their live tasks, personal workflow, SOP/checklist templates, and personal convenience buttons.

• Department-wide automations and the underlying business architecture remain centrally governed.

• Leaders retain appropriate visibility and administrative access.

• HR-related boards remain restricted to leadership.

• The system survives staff departures and role changes without losing boards, permissions, or automations.

• We reduce duplicated cards and synchronization rules wherever Trello offers a simpler source-of-truth model.

We are considering organizing approximately 50 boards into functional areas such as Core Workflow, Office, Shop, Installs, Marketing, Clerical, HR, and SOPs. These could become separate Workspaces, Collections inside a smaller number of Workspaces, or any combination.

The questions

1. How should Workspaces be used at this scale?

Should a Workspace represent a genuine security, administration, or billing boundary, while Collections organize departments inside it? Or is creating a separate Workspace for each operational area the better long-term structure?

What automation, mirroring, permission, and billing complications should we expect when workflows cross between Workspaces?

2. Who should create and own business-critical automations?

Would you recommend:

• One company-controlled automation creating/housing account

• Separate company-controlled automation accounts for major workflow areas

• Department leaders creating/housing their department’s automations

• Some hybrid of these approaches

We want automations located near the processes they support, but we do not want critical rules to disappear when someone leaves or changes roles. We are also conscious of Trello’s per-user automation-storage limit.

How do experienced teams divide automation ownership while retaining maintainability and continuity?

3. Should each employee have a personal command board?

Our desired experience is that each person has one clear place showing what to do now, next, and later.

Would you build personal boards using Mirror cards or linked child-task cards, or rely on Trello’s native Home, My Cards, assigned checklist items, and Workspace Table views?

We want to minimize duplication, but personal boards may offer better prioritization and employee-specific buttons. What trade-offs have you encountered?

4. How should role changes be managed?

Ideally, Alice would use alice@company.com while serving as Shop Manager. If Bob later assumes that role, the relevant permissions and responsibilities would move to Bob without either person sharing a generic Shop Manager login.

Does Trello provide any practical role-based or alias-based model for this, or is the recommended approach simply named accounts, multiple administrators, and a documented reassignment process?

5. At what point does Enterprise make more sense than Premium?

Premium Workspaces are billed separately, so overlapping membership across several departmental Workspaces could become expensive. Enterprise appears better suited to multiple centrally administered Workspaces.

For a team of our size, but with many boards and substantial automation, would you consolidate under Premium or consider Enterprise?

6. How would you migrate this system?

If you were rebuilding this architecture without interrupting active work, in what order would you address:

• User accounts and permissions

• Workspace and board structure

• Automation ownership

• Automation documentation

• Duplicate or synchronized cards

• Personal task views

I would especially appreciate examples from people administering similarly interconnected Trello environments.