Migrate from Method:Field Services to Pipedrive

Method's Contact table holds both people and organizations flagged as 'customer' or 'vendor'. FlitStack splits each Contact into a Pipedrive Person record and, when the entity is a company, a Pipedrive Organization record, then links them via the Person's Organization relationship field.

Method Work Orders have status, priority, service type, technician, and signature fields with no Pipedrive equivalent. FlitStack maps each Work Order to a Pipedrive Deal, adds custom fields for priority, service type, and technician, and maps Method's status values to Pipedrive stage names.

Method technician records hold role, availability, and routing preferences. FlitStack resolves technician email addresses to Pipedrive users and populates a 'Assigned Technician' custom field on the Deal. Unmatched technicians are flagged for admin review before migration commits. FlitStack also records the original role and availability as custom fields on the Deal, and preserves any routing preferences in a 'Preferred Route' custom field when present.

Method stores service location on the Work Order. FlitStack migrates service addresses to Organization records and adds a 'Service Address' custom field on the related Deal for display continuity. If the address contains multiple lines or suite information, FlitStack normalizes the format before writing to the Organization, preserving the full address in the custom field for reference. Geocode data can be added later via Pipedrive's map feature.

Method activities (calls logged, emails sent, notes attached) map to Pipedrive Activities with original timestamps, owners, and subject lines preserved. Activity type determines the Pipedrive Activity type field. Each activity is linked to the related Person or Organization, and any due date set in Method is transferred as the Pipedrive Activity's due date. If the subject line is missing, FlitStack creates a default from activity type and date.

Method custom fields on Contact and Work Order map to Pipedrive custom fields on Person and Deal respectively. Custom field data types are mapped: text to text, number to number, picklist to drop-down, date to date. Pipedrive assigns hash-key names that are captured in the migration plan.

Method file attachments on Work Orders and Contacts are downloaded and re-uploaded to Pipedrive Files, linked to the corresponding Person, Organization, or Deal record. Original file names and upload timestamps are retained in Pipedrive's metadata. Files larger than Pipedrive's 100 MB limit are flagged for manual upload or stored in linked cloud storage with a reference URL added to the record.

Method's QuickBooks customer/vendor ID is preserved as a 'QuickBooks_ID__c' custom field on the Pipedrive Organization record, enabling accounting teams to re-establish QuickBooks sync without losing the link to historical Method transactions. This custom field can be referenced by Zapier, Make, or QuickBooks-Pipedrive apps to rebuild the sync. If additional QuickBooks metadata such as class or invoice ID exists in Method, FlitStack can map those to custom fields as needed.

Method Time Tracking entries generated by Field Crew map to Pipedrive Activities with type 'Task' and a custom 'Hours Worked' field. Duration, technician, and Work Order association are preserved as activity metadata. If a time entry includes a billable flag, FlitStack stores it as a custom 'Billable' checkbox on the Activity. All entries are linked to the originating Deal to maintain a complete labor history in Pipedrive.

Method workflows and custom app logic do not have a direct equivalent in Pipedrive. FlitStack exports workflow definitions as a reference document for rebuilding in Pipedrive Automations or Sequences. The exported document includes trigger conditions, action steps, and any custom field dependencies, allowing Pipedrive admins to recreate logic using Automations' visual builder or the Sequences email cadence tool.