Migrate from EZ Office to Pipedrive

Pipedrive has no custom objects — asset records require custom field design on Deals

Pipedrive does not offer a custom objects module. Every data point from EZ Office that does not map to a native Pipedrive field must be stored as a custom field on Person, Organization, or Deal. This means that assets with 15 custom properties (condition rating, depreciation schedule, warranty end date, insurance carrier, insurance policy number, last service date, next service due, serial number, manufacturer, model, lot number, location hierarchy, custodian, procurement date, and salvage value) all require Pipedrive custom field creation before migration. We design the custom field schema first and deliver a Pipedrive field setup plan so your account is ready before data lands.

EZ Office activity history requires manual export and careful Pipedrive Activity mapping

EZ Office exports activity data (custody events, maintenance logs, check-in/check-out records) through its canned reports feature rather than a structured API endpoint. The CSV export contains event type, timestamp, user, and linked asset or member ID. Migrating this history into Pipedrive Activities requires matching each event to a Pipedrive Person or Deal record using the source IDs stored during the migration, then setting the correct activity type, subject, and done date. We handle this mapping during the migration run and validate that the linked records exist in Pipedrive before committing the activity.

Pipedrive file attachment size limits may require manual handling for large documents

Pipedrive attachments on Person, Organization, or Deal records have size constraints enforced at the API level. Large documents from EZ Office — specification sheets, maintenance contracts, or bundled PDF reports — may exceed this limit and fail during the migration run. We flag oversized files during the pre-migration audit and handle them by either linking to a shared Google Drive or Dropbox folder from the Pipedrive record, or alerting your team for manual re-attachment after migration. We do not skip files silently.

Pipedrive API v2 rate limits require batched migration runs

Pipedrive introduced token-based rate limits in December 2024 with the rollout of API v2. Bulk data ingestion through the API must be throttled to respect per-token limits, which can extend migration clock time on large datasets. We monitor API response headers during migration and apply exponential backoff when 429 responses occur. For migrations exceeding 50,000 records, we recommend scheduling the migration run during off-peak hours to avoid contention with any active Pipedrive automations or integrations in your account.

EZ Office location hierarchies collapse to flat Pipedrive Organization address fields

EZ Office supports hierarchical locations (site name > building > floor > room) stored as parent-child relationships. Pipedrive Organizations have a single flat address structure (street, city, state, postal code, country) with no native hierarchy. We preserve the top-level site as the Organization address and store the full location path as a searchable custom text field, but Pipedrive's native location filters will only reference the top-level address. If your team relies on multi-level location filtering in Pipedrive reporting, we recommend configuring the full path as a separate searchable custom field and using it as a filter dimension in your Pipedrive reports.