Migrate from Fieldmagic to Pipedrive

Fieldmagic Customers map 1:1 to Pipedrive Organizations. Company name, phone, website, and industry map directly. Multi-contact associations (Fieldmagic allows N contacts per customer) resolve to the primary contact as the Organization's linked Person, with additional contacts stored as additional Person records linked to the same Organization.

When a Fieldmagic Customer record represents an individual rather than a company (sole trader), it splits to a Pipedrive Person without a parent Organization. We use the customer type flag or a non-empty individual-name pattern to detect this case before migration. The email address serves as the Person record's unique identifier for de-duplication.

Fieldmagic Sites store multi-line addresses with GPS coordinates and site-specific notes. We map the address lines to Pipedrive Organization's combined address field. GPS coordinates, site reference numbers, and site-level custom properties migrate as Pipedrive custom fields on the parent Organization. Sites without a parent Customer are flagged for manual review before migration.

Fieldmagic Contacts map directly to Pipedrive Persons using first name, last name, email, phone, and job title. The primary_contact flag maps to the Person that auto-links to the parent Organization. Secondary contacts on the same Customer are migrated as separate Person records sharing the same Organization.

Fieldmagic's contact-to-customer link uses a customer_id foreign key. During migration we first create all Organizations, then resolve Contact.company_id to the new Pipedrive Organization ID. Unresolved references (deleted customers) land the Person as an unlinked record for your admin to reassign manually.

Fieldmagic Jobs are the core FSM entity with status, assigned technician, scheduled date, line items, and checklist steps. We map Jobs to Pipedrive Deals: job title → Deal title, total_amount → Deal value, status → Deal stage (value mapping), site_id → custom field + org link. The FSM checklist structure (step-by-step tasks) cannot map to any native Pipedrive object and is exported as a JSON attachment or custom field for rebuild reference.

Fieldmagic Quotes (pre-approval sales documents) map to Pipedrive Deals. Quote status (quoted, approved, rejected) maps to Pipedrive Deal stage values via value_mapping. Approved Quotes that convert to Jobs in Fieldmagic create a Deal in Pipedrive with the job reference stored as a custom field, linking the two records for post-migration traceability.

Fieldmagic Asset Types (equipment categories like HVAC, Electrical, Plumbing) map to Pipedrive Product categories or a custom field on the Product object. The category tree structure in Fieldmagic is flattened to a single category string in Pipedrive. We preserve the full type name in a custom field to avoid information loss.

Fieldmagic Assets (individual equipment records with serial numbers, install dates, and location) map to Pipedrive Products. Serial number → Product code, install date → custom date field, warranty expiry → custom date field, location/site → custom field linking back to the Organization. Maintenance schedules and parts histories do not migrate — these are exported as a rebuild reference for Pipedrive automations.

Fieldmagic Users (both office users and mobile technicians) map to Pipedrive Users by email match. All active Fieldmagic users get a corresponding Pipedrive user account. Inactive users are optionally migrated with a deactivated flag. Technician-specific permissions (mobile app access) are not replicated in Pipedrive — those permissions are destination-side configuration.

Fieldmagic Invoices have no Pipedrive equivalent — Pipedrive has no native billing module. We preserve invoice records as a custom field set on the associated Deal (invoice number, amount, date, status) and provide an invoice data export as a CSV for import into your accounting tool (Xero, QuickBooks, MYOB) post-migration.

Fieldmagic custom properties on Customers, Sites, Contacts, Jobs, Quotes, and Assets require pre-created Pipedrive custom fields before migration. We deliver a custom field creation plan with exact names, types (text, number, date, picklist), and object assignments. Pipedrive assigns 40-character hash keys to custom fields at creation — our migration engine resolves these dynamically so field mapping stays accurate per account.

Fieldmagic Schedules (technician time blocks on jobs) map to Pipedrive Activities with Type='Task' or Type='Meeting'. The scheduled start and end times map to the Activity's due date and duration. Full-day schedules with travel time do not have a Pipedrive equivalent and are stored as Activity description text for manual scheduling in Pipedrive.