Migrate from farmerswife to monday Work Management

farmerswife Projects map 1:1 to monday.com Boards. Each Project's name, status, start and end dates, client link, and description transfer to the Board's name, group status columns, and description field. Custom fields on Project migrate as additional columns on the Board. Projects with nested sub-projects flatten into subitems on the primary Board, with the subitem hierarchy preserved as a Parent Link column if the destination board uses the Subitems integration.

farmerswife Activities map to monday.com Groups (representing the shoot day, edit session, or production phase) containing Items (representing individual tasks or bookings within that Activity). The Activity's dates, status, and notes transfer to the Group's date range columns and item description fields. Activities with large resource rosters (e.g., 150 crew on a shoot day) become items with Assignees set to the migrated People Objects, and resource-specific details migrate as custom columns.

farmerswife Bookings (the assignment of a Resource or Person to an Activity at specific times) map to monday.com Items with a Timeline column capturing the start and end datetime. The resource reference (Object ID) resolves to the monday.com Person or Contact assigned to the Item. For equipment or room Bookings where no monday.com Person exists, we create a static text column with the resource name and a linked Contact record in a Resources board for cross-reference.

farmerswife People Objects (crew, staff, contractors) map to monday.com Person columns on Items or Contact records in a dedicated Contacts board. Email, phone, role/title, and Object Type (e.g., 'Crew', 'Freelancer') migrate to the corresponding monday.com contact fields or as custom text fields. Object Types map to monday.com tags on the Contact record.

farmerswife Resources (equipment, rooms, edit suites) and Services do not have a native monday.com equivalent. We split them: physical resources map to Items in a dedicated Resources board with custom columns for resource type, availability status, and hourly/daily rate. Services map to Items in a Services board with pricing columns. Both boards link back to Project Boards via Connect Board columns or Item linking for cross-board reference.

farmerswife Room Objects map to Items in a Resources board with a 'Room' tag. Room-specific fields (capacity, facilities, location) migrate as custom columns. We create a separate Room Availability board with a calendar view if the customer requires scheduling visibility, using date columns and Status columns for booking state.

farmerswife Object Types (e.g., 'Crew', 'Equipment', 'Studio', 'Freelancer') are categorical labels that group Objects. We map these to monday.com Tags on Items. Tags are flat in monday.com and do not support hierarchical nesting, so multi-level Object Type taxonomies flatten to a single tag level. Customers choose the primary classification level during scoping.

farmerswife Budgets with line items and Price Agreements require significant transformation. Each Budget maps to a Board or a Group within the Project Board, with Budget line items as Items. The per-line Price Agreement (fixed price per item) migrates as a static numeric column and the line-item total as a separate column. We flag any line items where the individual Price Agreement exceeded the project-level rate for the customer to review during UAT. farmerswife's cost-to-completion tracking does not have a monday.com equivalent; we document it as a manual reporting process or integration recommendation.

farmerswife Rate Cards (Client Rates and Project Rates with day rate, overtime rate, and custom pricing tiers) do not have a native monday.com equivalent. We flatten the applicable rate card into static numeric columns on the Contact or Resource Item: a Day Rate column, an Overtime Rate column, and a Rate Card Name column for reference. The multi-layer rate visibility rules (who can see Project Rates vs Client Rates) cannot be reproduced in monday.com's Admin/Member/Guest model; we document the desired visibility as a role configuration recommendation.

farmerswife Client records (linked to Projects and Rate Cards) map to monday.com Company records in the Contacts integration or as Items in a Clients board. Client name, contact details, billing address, and Client Rate Card linkage migrate to the Company record. Client Rate Card reference is preserved as a text column pointing to the applicable Rate Card Item.

farmerswife Time Entries (logged against Activities and Bookings) migrate to monday.com Time Tracking columns on Items. Each Time Entry's date, duration, and linked Object reference resolve to the corresponding monday.com Item and Person assignment. Historical Time Entries with no remaining open Items become read-only Items with Time Tracking entries pre-populated in a completed state.

farmerswife files are stored server-side in the 'files' folder and referenced by Project. We catalogue all file paths from the farmerswife server directory, reconstruct the full file URLs, and populate a Link column on the corresponding monday.com Item with the file reference. For active production files, we recommend migrating to a cloud storage integration (Google Drive, SharePoint, or Dropbox) and storing the share link in the Link column. The actual binary files do not migrate; only the path references do.

farmerswife Users map to monday.com Team Members by email match. The farmerswife permission model (Project Rates Permissions, Client Rates Permissions, and the 'Always Allow' list) cannot map directly to monday.com's three-tier role model (Admin, Member, Guest). We document the permission mapping for each migrated user role and flag the two most granular permission gaps: rate visibility and project-level access restrictions. Customers configure equivalent roles post-migration in monday.com's Team settings.

farmerswife Custom Fields on Projects, Objects, and Activities are exported as key-value pairs alongside standard fields. Each unique Custom Field schema is unique per customer. We perform field-level discovery during scoping, map each Custom Field to the nearest monday.com column type (text, number, date, dropdown, checkbox, link), and create the columns in the destination Board before data import. Custom field dependencies or formulas do not migrate.