Migrate from farmerswife to Microsoft Project

farmerswife Projects map 1:1 to Microsoft Project plans. We extract the project name, status, start and end dates, description, and custom fields from CSV export. Project-level metadata such as the linked Client and the Project Rate Card reference are preserved in a custom Project Summary field for the customer's admin to action post-migration.

farmerswife Objects export by Object Type (Crew, Equipment, Studio, Service) and re-import into the Microsoft Project Resource Sheet as named resources. Resource Type maps from Object Type: People map to Work resources, Rooms and Equipment map to Material or Work resources, Services map to Work resources. Each resource gets a custom Object Type field to preserve the farmerswife category for filtering and reporting.

farmerswife Object Types are categorical labels organizing Objects. We map them to a custom Resource text field (e.g., ResourceCategory) on the Microsoft Project Resource Sheet. This allows resource-level filtering by type (Crew, Equipment, Studio) in the Resource Usage view without modifying the standard Microsoft Project schema.

farmerswife Activities (shoot days, edit sessions, prep blocks) map to Microsoft Project Tasks. We extract the Activity name, start date, end date, and duration, and reconstruct the task in Project with the appropriate start or finish constraint. Activities that span multiple days become summary tasks with sub-tasks per resource booking.

Bookings are resource assignments within Activities. Each Booking linking an Object to an Activity becomes a Task Resource Assignment in Microsoft Project. We map the booking's start and end timestamps to Assignment Start and Finish, and the resource allocation (e.g., 8 hours, half-day) to Assignment Units. The Activity-Object linkage is preserved as the assignment relationship.

Budgets in farmerswife contain line items with Price Agreements (fixed-price per item) and track cost-to-completion against rate cards. Microsoft Project has no native per-item billing module. We flatten each Budget into a project-level total cost stored in a custom Budget field, and we deliver a detailed line-item inventory CSV listing every Budget line with its Price Agreement value, rate reference, and mapped task. The customer's finance team re-ingests this into their invoicing system post-migration.

Rate Cards in farmerswife define day rates, overtime rates, and custom pricing tiers scoped to Clients or Projects. Microsoft Project has no rate-card module. We export the full Rate Card structure as a standalone pricing spreadsheet keyed by resource name and rate type, with columns for day rate, overtime rate, and any tiered pricing. The customer maintains this externally or in Excel Online linked to the project.

farmerswife's dual-layer rate permission hierarchy (Project Rates Permissions and Client Rates Permissions) with Always Allow lists does not map directly to Microsoft Project's role model (Owner, Member, Viewer). During scoping we ask the customer to define their desired visibility model: simplest is to collapse to Owner=full access, Member=view and edit, Viewer=read-only. For orgs requiring per-field rate visibility, we document the gap and recommend a SharePoint-based access control list outside Project.

farmerswife Clients are distinct entities linked to Projects and Rate Cards. Microsoft Project has no native Client or Account object. We map Clients to a Microsoft 365 Group or SharePoint site that hosts the Project plan, allowing the client name to appear in the site title and SharePoint document library for document sharing. For organizations with a CRM, we recommend linking the client context through a Dynamics 365 or external lookup rather than within Project.

Time entries logged against Activities and Bookings in farmerswife feed into invoicing. Microsoft Project tracks actual work against assignments but not as a standalone time-tracking entity. We map Time Entries to Assignment Actual Work on the corresponding Task-Resource Assignment, and we deliver a time-entry summary CSV grouped by project and resource for re-ingestion into the customer's billing tool.

Custom Fields on farmerswife Projects, Objects, and Activities are exported as key-value pairs alongside standard fields. We map them to Microsoft Project custom fields by type: text properties to Text custom fields, numeric values to Number custom fields, dates to Date custom fields, and yes/no flags to Flag custom fields. Since each customer's farmerswife Custom Field schema is unique, we perform field-by-field mapping during the discovery phase.

farmerswife files are stored in server-side folders and referenced by Project. We catalogue all file references, reconstruct the original folder paths from the farmerswife server directory, and remap them to the destination SharePoint Document Library attached to the Microsoft 365 Group or Project Online site. File contents do not transfer automatically; we provide the path mapping inventory so the customer's admin can copy or re-upload the files.