Migrate your Service In Sync data

Customers (also called Clients in some workflows) are the primary contact records in Service In Sync. Name, phone, email, address, and communication history are standard fields that map cleanly to Contact/Account objects in most destination CRMs.

Jobs are the central work record — the equivalent of Work Orders in other FSM platforms. They carry status, assigned technician, date/time, and are linked to the Customer record. We preserve the full job history including closed jobs, not just open appointments.

Estimates are distinct objects linked to Jobs, carrying line items, totals, approval status, and signature/deposit data. Not all destination CRMs have a native Quote object, so we may map estimates to Custom Objects or Opportunity line items depending on the target schema.

Scheduling in Service In Sync ties appointments to Jobs and technicians. The scheduling block (date, time window, assigned user) is exportable, but calendar-specific data (recurrence rules, all-day flags) may require field-level mapping to the destination calendar or scheduling object.

Payment records and deposit tracking are stored per Job or Estimate. Amount, status, payment method, and timestamp are available. We do not migrate payment card data — only the financial record (amount, status, date) for accounting reconciliation in the destination system.

Review requests are triggered post-job and linked to the customer record and the job itself. The request status (sent, opened, clicked, review posted) is migratable, but the actual star ratings live on external platforms (Google, Yelp, Facebook) and are not stored in Service In Sync itself.

Automated reminders (email/SMS confirmations, follow-up triggers, review request automations) are defined as workflow rules in Service In Sync, not as data records. We do not export automation logic — only the fact that a reminder was sent is logged in the communication thread, not the rule definition itself.

Customer confirmations, updates, and follow-up messages sent from within the platform are logged against the Job or Customer record. Thread history is migratable as text/event logs, but attachment support and rich-media content within threads requires case-by-case review.

Reporting data in Service In Sync is generated on-demand from live records — there is no separate reporting database or exported report history. We do not migrate historical report snapshots. The underlying operational data (jobs, payments, reviews) is migrated, which can be used to rebuild reports in the destination system.