Migrate from Service In Sync to Pipedrive

Service In Sync clients map directly to Pipedrive Persons. Name, email, phone, address, and custom properties transfer as-is. Pipedrive Persons have no mandatory first-name/last-name split — FlitStack splits full names or preserves as a single-name field based on the source format.

Service In Sync business entities (companies associated with clients) map to Pipedrive Organizations. Company name, domain, industry, and employee count transfer as standard fields. Pipedrive Organizations can have multiple Persons linked — the primary contact gets assigned first.

Service In Sync jobs translate into Pipedrive Deals. The job name becomes the Deal name, the job status maps to Deal stage via value mapping (Open, Scheduled, Completed, Invoiced → pipeline stages), and service-type metadata becomes custom fields on the Deal. Job ID is preserved as Source_System_ID__c for traceability.

Estimates in Service In Sync carry line items, quantities, and amounts. These merge into a Pipedrive Deal with the estimate total as the Deal value, and line items become Deal Products if Pipedrive Products are configured. If no products exist in Pipedrive, estimate details migrate as a custom text field on the Deal.

Service In Sync payment records (amount, status, date, method) do not have a native Pipedrive equivalent. FlitStack creates Activity Notes with type='payment' on the associated Deal, capturing payment amount, date, and status. Partial deposits are represented as separate Activity entries linked to the same Deal.

Service In Sync's review-booster records (stars, platform, date) migrate as Activity Notes on the Person record. Pipedrive has no native review object — these are preserved for reference in a custom field (Review_Score__c) and linked via Activity note.

Service In Sync reminders map to Pipedrive Activities of type 'task'. Original due dates and assigned owners transfer. Note: Pipedrive Tasks do not automatically fire — the automation to re-create the trigger behavior must be rebuilt in Pipedrive Automations.

Service In Sync online booking submissions (name, contact info, requested service, date) map to Pipedrive Leads. If the booking belongs to an existing Person or Organization, FlitStack links the Lead to the matching Person/Org and converts it to a Deal representing the booked service. Status field captures the booking pipeline state.

Service In Sync custom client properties (beyond name, email, phone) require Pipedrive custom fields. FlitStack creates Person custom fields matching the source type (text, number, date, picklist). Pipedrive stores custom field keys as 40-character hashes — field names are created in Pipedrive first, then mapped by key.

Service In Sync job-level custom properties (equipment type, service category, technician skill required) map to Deal custom fields. If Pipedrive Products are used, some properties may map to Product custom fields instead. The migration plan documents which custom properties map to Deal versus Product fields based on your Pipedrive configuration.

Service In Sync users (technicians, coordinators, admins) map to Pipedrive Users. FlitStack resolves each Service In Sync user by email match against Pipedrive users. Unmatched users are flagged before migration — either invited to Pipedrive or reassigned to a fallback owner. Jobs and activities link via OwnerId on the Deal or Activity.

Client communication threads in Service In Sync (confirmations, updates, follow-ups) migrate as Pipedrive Notes on the Person record. If the thread contains email content, FlitStack attempts to parse and recreate as Email Activities. Plain-text message content without email headers becomes a Note.