01
Define the operating truth
Review what customers, jobs, statuses, assignments, dates, locations, and relationships mean in the current system before mapping columns.
Switching and migration
Preview the move, prove the records, and cut over without gambling on a blind import.
Ironline provides a controlled customer-and-job migration path for service businesses leaving spreadsheets or common service platforms. Preserve the source, dry-run the mapping, inspect duplicates and row errors, approve the supported scope, and reconcile before the old system is retired.
Owner-Operator and Team customers can self-serve supported files · Growth and Scale migrations should be reviewed before broad rollout
Supported commit
Customers and jobs
Committed only after the dry run, mapping, duplicates, and errors are reviewed.
Separate migration decisions
Financial and unsupported records
Kept outside the live import when meaning, authority, or relationships cannot be preserved.
Separate activation
Provider connections
Accounting, payments, messaging, calendars, and maps require their own customer authorization and proof.
A controlled migration path
Six checks before the old system is retired.
02
Preserve the original export
Keep the source file and its fingerprint unchanged. Corrected data becomes a new review version instead of silently rewriting the first attempt.
03
Dry-run the mapping
Detect the file format, map supported fields, identify duplicates, and surface row-level errors before anything is committed to the live workspace.
04
Approve the supported scope
Customers and jobs are the current commit scope. Unsupported or ambiguous records stay outside the live import until an authoritative workflow exists.
05
Commit, retry, and reconcile
Preserve created, updated, skipped, replayed, and error counts. Correct failed rows through the controlled retry path and reconcile the resulting records.
06
Pilot and cut over deliberately
Confirm counts, relationships, permissions, and the first real workflows before retiring the old system or expanding the rollout.
Common export sources
Export-based guidance—not a one-click migration claim.
Selecting a source means Ironline can guide a supported customer-and-job export review. It does not mean every field, file, financial record, workflow, or relationship transfers automatically.
Supported field-service customer export
Use a customer CSV from the current service platform as the source for mapping, duplicate review, and a server dry run.
Supported field-service job export
Map supported job fields, inspect customer relationships and row errors, and preserve every commit outcome.
QuickBooks exports
Use customer or supported job-oriented export data as a migration source; QuickBooks remains authoritative for bookkeeping records.
Generic CSV
Map a representative sample first, then approve the exact supported fields and relationships before committing.
Ironline responsibilities
Provide a reviewable migration process.
- Provide the supported file intake, mapping, dry-run, duplicate, error, commit, retry, and reconciliation controls
- Explain which fields and record types can be committed and which must remain outside the import
- Preserve import outcomes and retry lineage so a partial result is visible and reviewable
- Review a representative sample and rollout expectations for Growth or Scale migrations
Customer responsibilities
Own the source meaning and cutover decision.
- Export the data from the current system and keep the original source file
- Provide a person who understands the current workflow, statuses, relationships, and edge cases
- Review mappings, duplicate choices, row errors, and the supported commit scope
- Own the cutover, rollback, retention, and decision to retire the previous system
Outside the current commit scope
Records that need a separate authoritative plan.
Ironline will not force ambiguous or unsupported information into live customer data merely to make an import count look complete.
- Estimates, invoices, payments, refunds, disputes, and historical financial transactions
- Attachments, custom fields, and relationships that cannot be represented without losing meaning
- Team, wage, payroll, unsupported catalog, and provider-connection records
- Recurring schedules whose source rules cannot be preserved accurately in the supported model
Growth and Scale rollout review
The people building Ironline can review the migration before the company commits to it.
Direct review makes fast decisions possible, but it does not make unsupported data safe. The source, supported scope, recovery plan, responsibilities, and cutover conditions remain explicit.
Bring one representative export
A sample containing real duplicates, missing values, relationships, and edge cases is more useful than a perfectly cleaned demonstration file.
Start with one export and one representative workflow.
Review the data, prove the operating fit, and decide on cutover only after the resulting records make sense.
See the rollout model