Migrate from OptimoRoute to Pipedrive

OptimoRoute orders map directly to Pipedrive deals. The order title becomes the deal name, monetary order value becomes deal value, and order status maps to Pipedrive stage values via a value-mapping table. Delivery address, time window, priority, driver assignment, and POD flags migrate as custom deal fields. Custom order fields of all types (text, number, single-select) map to Pipedrive deal custom fields.

OptimoRoute's customer reference on an order may include a name, phone, email, and company. We split this into a Pipedrive Person record (name, phone, email) and, if a company is present, an Organization record. The Person is then linked to the Deal as the primary contact. If the customer is a business with no individual contact, we create an Organization and optionally a Person for the primary point of contact.

OptimoRoute drivers become Pipedrive Person records when they are customer-facing delivery contacts. For internal-only drivers (not CRM contacts), we create Person records with a role indicator and store driver performance metrics (rating, total deliveries, vehicle type) as custom fields on those Person records. Driver IDs are preserved as Source_Driver_ID__c for reconciliation.

OptimoRoute locations — customer delivery addresses and depots — map to Pipedrive Organizations. Address fields, city, state, postal code, and country map directly to Organization address fields. Location names become Organization names. If a location has a contact person, that person is created as a Person linked to the Organization.

Pipedrive has no native vehicle object. Vehicle type (refrigerated, van, truck), capacity, and loading-ramp flags from OptimoRoute are stored as custom fields on the Person record for drivers and on the Deal record for the assigned vehicle. This gives dispatchers visibility into vehicle constraints without leaving Pipedrive.

OptimoRoute routes define the sequence of stops assigned to a driver on a given day. Pipedrive has no native route object. We create a Pipedrive Activity (type: task or event) representing the route window, and store the route identifier, planned sequence, start/end location, and optimization status as custom fields on the associated Deal records. Route-level performance metrics (estimated vs. actual drive time) become custom fields on the related Deals.

OptimoRoute captures POD as digital signature, photo, and timestamp at the point of delivery. We create Pipedrive Activities (type: note) for each POD event, capturing the timestamp, who confirmed it, and the POD type. Signature and photo URLs are stored as custom URL fields on the Deal. If OptimoRoute captures customer feedback at the door (thumbs up/down or rating), that also maps to a custom field on the Deal.

OptimoRoute custom order fields are created per-account by an admin and can be text (single/multi-line), number (with decimal precision), or single-select (predefined options). We map these to Pipedrive deal custom fields using the same field type. Single-select fields require a value-by-value mapping if the predefined options differ from Pipedrive's pick-list values. Text and number fields map directly.

OptimoRoute tracks order-level events: status changes, driver reassignments, address updates, time-window changes. Each event migrates as a Pipedrive Activity with the original timestamp and a type indicator (e.g., 'Order Update', 'Reassignment'). This preserves the full operational history of each delivery as an activity feed on the associated Deal.

OptimoRoute admin and dispatcher users are resolved by email match against Pipedrive users. If a Pipedrive user account exists for the email, records are assigned to that user. If no match is found, records are assigned to a fallback owner and flagged for admin review. Driver app-only users without CRM access are not created as Pipedrive users.