Import Archive is the workflow at /settings/import-archive. Import archive stores records exported from previous systems (legacy CRM, spreadsheets, competitor tools) so you can review, search. Settings to Import Archive at /settings/import-archive, sometimes reached from Data import, holds batches from the old system.
Settings to Import Archive (/settings/import-archive) Also referenced from Settings to Data import for some import flows. Upload or receive archived import batches (per your migration process). Browse archived records with search and filters. Merge archive records into active customers (and related types as supported). Keep legacy IDs and notes for audit during transition. Migration file prepared per ServiceFlow import spec (coordinate with support for format). Plan for deduplication against existing customers. Settings to Import Archive (or Data import entry point). Upload provider export or ServiceFlow-formatted archive. Wait for processing to review batch status. Open archive list to search by name, phone, legacy ID. Open record to compare to potential live customer match. Merge into customer or create new customer from archive row. Track remaining unmerged rows weekly during migration window. Deactivate archive batch when complete (per admin policy). /settings/import-archive step 4 is Upload archive batch.
Overview
Import archive stores records exported from previous systems (legacy CRM, spreadsheets, competitor tools) so you can review, search, and merge into live ServiceFlow customers and related entities without losing historical context.
How to access
Settings → Import Archive (
/settings/import-archive)Also referenced from Settings → Data import for some import flows.
How do you upload or receive archived import batches (per your migration process)?
Upload or receive archived import batches (per your migration process).
- Upload or receive archived import batches (per your migration process).
- Browse archived records with search and filters.
- Merge archive records into active customers (and related types as supported).
- Keep legacy IDs and notes for audit during transition.
Prerequisites
- Admin or data-import permissions.
- Migration file prepared per ServiceFlow import spec (coordinate with support for format).
- Plan for deduplication against existing customers.
Step-by-step
Upload archive batch
- Settings → Import Archive (or Data import entry point).
- Upload provider export or ServiceFlow-formatted archive.
- Wait for processing → review batch status.
Review and merge
- Open archive list → search by name, phone, legacy ID.
- Open record → compare to potential live customer match.
- Merge into customer or create new customer from archive row.
- Confirm merged fields and notes.
Ongoing cleanup
- Track remaining unmerged rows weekly during migration window.
- Deactivate archive batch when complete (per admin policy).
Current limitations
- Not a live two-way sync with old system—one-way migration tool.
- Merge rules may require manual confirmation for ambiguous matches.
- Some related entities (full job history PDFs) may stay archive-only.
- Very large archives may process asynchronously—check status indicators.
Roadmap
- Auto-match scoring for customer dedupe.
- Bulk merge with preview.
- Import from common competitors’ export formats out of the box.
Example: a Housecall export that should not create a second Maria
Settings → Import Archive at /settings/import-archive, sometimes reached from Data import, holds batches from the old system. Upload the provider file or the ServiceFlow-formatted archive, wait for processing, then search by name, phone, or the legacy id. Merge into a live customer when the person already exists. Keep the legacy id in the archive so a later dispute can be traced. Merging is the supported dedupe. A second customer with the same phone is the mistake this screen exists to prevent.
Format is whatever support gave you for that migration. A random spreadsheet will fail validation. Test on a small batch. Admin or data-import permission is required. Archive rows are not jobs until you merge them into live records and then create work the normal way. There is no automatic "import and schedule next Tuesday."
Customer detail has an Archived Data tab for what was brought across. That tab is history. The archive screen is where you review the batch before it becomes a live customer.