Migrate your farmerswife data

Projects are the central container in farmerswife, holding Activities, Bookings, Budgets, and Files. We map them 1:1 and preserve all standard fields (name, status, dates, client link). Custom fields on Projects are exported via CSV and mapped to equivalent custom fields in the destination.

Objects is the umbrella term for people contacts, physical resources (equipment), rooms, and services. Each sub-type has distinct standard fields. We export them by Object Type and re-import into the destination's equivalent entity type. Object Custom Fields are preserved as structured CSV columns.

Object Types are broad categorical labels (e.g. 'Crew', 'Equipment', 'Studio') that organize Objects. The destination may use flat tag lists or a fixed taxonomy. We map Object Types to destination tags or custom list fields and flag any Object Types with no direct equivalent.

Activities are scheduled work items attached to Projects, often containing the same set of Objects (e.g. a shoot day with 150 crew members). We export Activities with their Project linkage, dates, status, and assigned Objects intact. Recurring Activity patterns are preserved where documented.

Bookings represent resource assignments within Activities—each booking links a Resource/Object to an Activity at specific times. We map Bookings as line items preserving the resource reference, time window, and booking type. Rate references from Project Rate Cards are carried as metadata.

Budgets in farmerswife contain line items with Price Agreements (fixed-price per item) and track cost-to-completion. We export the full budget hierarchy including line-item agreements, but note that complex per-item fixed-price structures often require manual verification in the destination's budget module.

Rate Cards are scoped to Clients or Projects and define day rates, overtime rates, and custom pricing tiers. We export the full Rate Card structure and map it to the destination's rate or pricing module, but nested rate hierarchies (Client Rates feeding Project Rates) require explicit value-mapping.

Users have role-based permissions that layer Project Rates Permissions and Client Rates Permissions. We export Users with their permission flags and replicate the permission structure in the destination, noting that most destination systems use a simpler role model that may not support the same granularity.

Files are stored in a server-side files folder and referenced by Project. We catalogue all file references, reconstruct folder paths from the farmerswife server directory, and remap them to the destination's document attachment structure. Large media files are flagged for separate transfer.

Custom Fields can be added to Projects, Objects, and other entities. We export them as key-value pairs alongside standard fields. Since each customer's Custom Field schema is unique, we perform field-level mapping during the scoping call and note any destination objects that lack equivalent custom field support.

Time entries are logged against Activities and Bookings and feed into invoicing. We export time entries with their Activity and User references and map them to the destination's time tracking entity, preserving billable/non-billable flags and hours.

Clients are distinct entities linked to Projects and Rate Cards. We export Client records with contact details and map them to the destination's Company/Account object, preserving Client Rate Card linkage as a metadata reference.