Migrate from farmerswife to Trello

farmerswife Projects (the central container holding Activities, Bookings, Budgets, and Files) map directly to Trello Boards. Project name, status, dates, and client link migrate as Board name, background colour (for status indication), and description. Project-level custom fields migrate as Board custom fields via the Custom Fields Power-Up. The one-to-one mapping is straightforward because both represent the top-level production container.

farmerswife Activities (scheduled work items attached to Projects, such as shoot days or post-production phases) map to Trello Lists within each Board. Activity name, dates, status, and linked client preserve directly. If Activities contain large numbers of Bookings (a shoot day with 150 crew members, per one verified reviewer), we create a Card per distinct resource booking group rather than one card per individual booking, to avoid Trello card-count sprawl.

farmerswife Bookings (resource assignments within Activities linking an Object to specific times) map to Trello Cards. Each Card receives the resource name, booking times, and rate from the Booking record. When a single Activity contains many Bookings for the same resource type (e.g. 40 background actors for one shoot day), we aggregate these into one Card per resource type with a checklist of individual names rather than 40 separate Cards. The original Booking details are preserved in the Card description.

farmerswife People Objects (crew, staff, contractors) map to Trello Board Members. We resolve by email match. Any Person Object without an email is added as a Board Member with a generated placeholder email and flagged for the customer's admin to complete before inviting. Permission levels (Project Rates Permissions, Client Rates Permissions) from farmerswife cannot be represented in Trello's three-tier Board permission model and are documented separately for manual review.

farmerswife Objects sub-typed as Equipment, Rooms, or Services have no direct Trello equivalent since Trello has no resource inventory concept. We map these to Card Labels (categorical: Equipment, Studio, Edit Suite, Catering) and/or checklist items within the Card describing what was booked. Object Type information from farmerswife becomes the Label name. The customer decides during scoping whether to use Labels, checklists, or both based on their reporting needs.

farmerswife Object Types (broad categorical labels such as Crew, Equipment, Studio, Edit Suite, Service) that organise Objects into groups map to Trello Label sets. We extract every distinct Object Type from the source, create a corresponding Label in each destination Board with the same name, and assign Labels to Cards based on the Object Type of each Booking's resource. Labels are colour-coded per type during migration setup.

farmerswife Clients (distinct entities linked to Projects and Rate Cards) map to Trello Board descriptions (for single-client Boards) or to Trello Organisations (for multi-client workspaces where the customer wants client-level separation). We preserve Client contact details in the Board description. Client Rate Card linkage cannot be represented in Trello and is documented as a manual rebuild item in the migration handoff.

farmerswife Budgets contain line items with Price Agreements (per-item fixed-price terms) and track cost-to-completion. We export the full budget hierarchy and flatten it into Card descriptions as structured text (Budget name, total amount, key line-item summaries). Per-item Price Agreement terms are too granular for Trello's data model and are flagged in the migration handoff document. If the customer uses a budget-tracking Power-Up (such as a custom integration or a third-party Trello power-up), we configure it during the migration setup phase.

farmerswife Rate Cards (day rates, overtime rates, custom pricing tiers scoped to Clients or Projects) cannot map to any native Trello structure. We export Rate Card values and map them as Card-level custom fields (Rate, Overtime Rate) using the Custom Fields Power-Up. Multi-layer rate permission hierarchy (Project Rates Permissions vs Client Rates Permissions) is documented separately because Trello's Board-level Admin/Member/Observer permissions cannot replicate this granularity.

farmerswife Users (internal staff with login credentials) map to Trello Board Members by email match. The multi-layer rate permission hierarchy (Project Rates Permissions and Client Rates Permissions) cannot be represented in Trello's three-tier permission model. We document the existing permission matrix and recommend a simplified Trello permission assignment during scoping. Users who have no corresponding email in the destination Trello workspace go to a reconciliation queue.

farmerswife Custom Fields (key-value pairs added to Projects, Objects, Activities) are exported as key-value pairs and mapped to Trello Custom Fields Power-Up equivalents. Since each customer's Custom Field schema is unique, we perform field-by-field matching during scoping. Custom field types (text, number, date, selector) map to the corresponding Trello Custom Field type. This is the most customer-specific portion of the mapping and requires a custom field audit before migration begins.

farmerswife stores files in a server-side files folder with per-project Media Library locations. Trello Cards support file attachments via Power-Up but does not have a native media library concept. We catalogue every file reference from the farmerswife server directory, reconstruct folder paths, and produce a written index of file locations alongside the migration record. The customer's admin remaps attachment paths in Trello or a linked storage system post-migration. This is a manual handoff, not an automated migration of file content.