Merge & Consolidate Two Loxo Instances with zero downtime

Fold one Loxo org into another — deduplicate records, reconcile custom fields and IDs, and unify agent lists without losing history. Engineer-led, validated end-to-end.

Book free consultation

Last updated August 2026

Loxo
Loxo
MIGRATION OVERVIEW

Why teams migrate from Loxo to Loxo

The core problem
Migrating between two Loxo instances is fundamentally a schema-alignment and ID-remapping challenge rather than a platform translation, since both source and target share the identical Talent Intelligence Platform data model encompassing People, Companies, Jobs, Activities, Deals, and Attachments. No native drag-and-drop transfer path exists; every internal record ID changes between instances, every relationship must be explicitly re-linked using a persistent ID-mapping table, and every pipeline stage configuration must be manually mapped in the target environment. The core technical work involves extracting records via CSV or the Loxo REST API, maintaining UUID-to-UUID mapping across all object types, and importing in strict dependency order to preserve Company-to-Person-to-Job relationship chains. Custom transformation logic is required for dynamic fields, activity type mapping, and pipeline stage alignment, with attachment migration handled entirely outside the standard record import flow.
Why this matters for your migration
KEY CHALLENGES

What makes this migration complex

These are the architectural mismatches and technical hurdles specific to a Loxo to Loxo migration.

Most Critical

ID Remapping Across Instances

Every source record UUID is invalid in the target instance, requiring a persistent ID-mapping table that tracks old-to-new identifiers for every object type before any relationship can be re-linked.

Blocks all downstream imports if mapped wrong

Dependency-Ordered Import Sequencing

Records must be created in strict dependency order — Users and Companies before People, People before Jobs, and Jobs before Activities and Placements — or foreign key references will fail and relationships will be orphaned.

Pipeline Stage Configuration Mismatch

Pipeline stages, workflow statuses, and job types are defined independently per instance, so every source stage must be manually mapped to an equivalent target stage before job and application data can be migrated accurately.

Activity and Event History Preservation

Activity records are tied to both a person and a job via their respective IDs, so any gap in the ID-mapping table will silently orphan recruiter call logs, email records, interview events, and submission histories.

Contact-Type vs. Candidate-Type Distinction

Loxo distinguishes People as contact-type or candidate-type, with contact-type events surfacing on the Company Activity Feed, so collapsing this distinction during migration causes permanent loss of company-level activity visibility.

Attachment File Handling

Resumes, contracts, and compliance documents are not included in standard CSV exports and must be downloaded individually from the source API and re-uploaded with correct person or company linkage in the target instance.

COMPLETE COVERAGE

Intelligent Human-Verified Data Mapping

Our migration engineer precisely maps every data point from Loxo to Loxo, ensuring perfect continuity for your customer support operations.

Loxo
Loxo
Contacts (Candidates)
Contacts (Candidates)
Companies
Companies
Jobs
Jobs
Job Candidates (Applications)
Job Candidates (Applications)
Notes
Notes
Tags
Tags
Tasks
Tasks
Sequences (Outreach Campaigns)
Sequences (Outreach Campaigns)
Sequence Steps
Sequence Steps
Custom Fields
Custom Fields
Resumes/Attachments
Resumes/Attachments
Placements
Placements
Contact Sources
Contact Sources
Education
Education
Experience (Work History)
Experience (Work History)

Looking for more entity mappings?

Contact our team
MIGRATION RISK ASSESSMENT

Every migration risk, already solved

Migration between platforms is full of edge cases. Our engineers have identified every risk from Loxo to Loxo and built proven solutions for each one.

High complexity
  • Jobs
    Jobs cannot be migrated via CSV and require either the managed migration service or API-based extraction, with high risk of data loss if pipeline stages and job statuses are not pre-configured and mapped in the target instance before import.
    Solved
  • Activities and Events
    Activity history is excluded from the free managed migration tier and is highly vulnerable to orphaning in any approach that does not maintain complete ID mappings for both the linked person and linked job records.
    Solved
  • Placements
    Placement records require valid person_id, job_id, and start_date references simultaneously, meaning any missing or incorrectly mapped dependency will cause the record to fail silently or import without its required relational context.
    Solved
  • Deals
    Deal records link to People, Companies, and Jobs concurrently, so they must be migrated last in the dependency chain and carry high risk of broken associations if any upstream object fails to map correctly.
    Solved
  • Attachments
    Attachments are explicitly excluded from CSV exports and require separate API-level file download and re-upload workflows, making them the most operationally complex entity and the most commonly lost during poorly executed migrations.
    Solved
Custom engineering
  • People (Candidates/Contacts)
    Core profile fields map cleanly between identical schemas, but dynamic field definitions, contact-type versus candidate-type classification, and deduplication across merged databases introduce meaningful data loss risk if not explicitly handled.
    Handled
  • Companies
    Company records transfer with moderate risk since basic fields are schema-identical, but dynamic fields and the re-linkage of associated People and Jobs depend entirely on the accuracy of the ID-mapping table.
    Handled
  • Custom / Dynamic Fields
    Dynamic field schemas must be manually recreated and configured in the target instance before import, and any field type or option mismatch will cause values to be dropped or stored incorrectly without import-time validation errors.
    Handled
  • Users and Ownership Assignments
    User accounts must be provisioned in the target instance first and mapped to source user IDs before any owned records are imported, otherwise recruiter attribution and ownership across all object types will be lost or misassigned.
    Handled
Clean transfer
  • Lists
    Saved candidate lists reference People by ID only and carry low structural complexity, but they will silently break if any referenced person fails to migrate or receives a new ID that is not reflected in the list membership records.
    Clean
What Our Customers Say

Real migration stories

See all customer stories →
CUSTOM MIGRATION

Fully customizable engineer-led migration

Tailor your migration from Loxo to Loxo exactly to your needs with our flexible customization options. Our experts will configure the perfect migration plan for your business.

Migration Filters

Job Status Filter

Filter by open, closed, drafted, or archived positions

Candidate Stage

Select candidates based on pipeline stages or disposition

Hiring Team/Owner

Migrate records assigned to specific recruiters or managers

Time Range

Migrate candidates or jobs from a specific time period

Data Types

Candidates & Profiles

Resumes, contact details, and full candidate history

Jobs & Requisitions

Job openings, descriptions, and hiring team assignments

Interviews & Feedback

Interviewer scorecards, ratings, and internal notes

Offers & Applications

Application metadata, offer letters, and contract files

ZERO DOWNTIME

Your timeline. Our engineers.

A dedicated engineer runs your migration, planned around your schedule and your data.

No babysitting a wizard. Avoid debugging errors yourself.

Looking for a more detailed migration timeline?

Contact our team

Speed

The migration timeline depends on both our turnaround time and yours.

We can complete a migration in under a day when the accounts are connected and the sample migration is approved promptly.

Background Sync

We also support migrating the newest records first, so you can go live faster while the rest of the data is synced in the background.

Data Volume Impact

Larger data volumes may require longer migration windows.

Continuous Operation

Weekend migrations minimize disruption to your customer service operations.

MIGRATION TIMELINE

Your Loxo to Loxo migration, step by step

See how long your migration will take from start to finish. Drag the slider to estimate based on your data volume.

How many records are you migrating?

<10K 50K 100K 250K 500K 1M 2M 5M 10M+
Checklist ~3 days
Sample 1 day
Review ~2 days
Full 2 days
Delta 1 day
Your team ClonePartner

Estimated total

~9 business days

1

Migration Checklist

1 day · ClonePartner ~2 days · Your team

We prepare the optimal data mapping as a shareable spreadsheet. Your team reviews, approves, and adds any customizations.

2

Sample Migration

1 day · ClonePartner

We run a test migration with a representative sample of your data to verify mapping accuracy and identify any potential issues before the full run.

3

Review & Approve

~2 days · Your team

Your team reviews the sample migration results, confirms data accuracy and mapping, and gives the go-ahead for the full migration.

4

Full Migration

2 days · ClonePartner

We execute the complete migration of all your data to your new Loxo, with real-time progress tracking and comprehensive logging.

5

Delta Migration

1 day · ClonePartner

We capture and transfer any new data that was added or updated during the main migration to ensure no data is lost. This final sync keeps everything current.

Related Guides

Pros and cons of different migration options

Choosing the right approach is key because migrating from Loxo to Loxo isn't just about moving data – it's about protecting your candidate experience and hiring pipeline.

Feature / Criteria ClonePartner Automated Tools CSV Import In-house migration
Custom Scripting for complex data Engineers build & maintain No Manual Yes – but costly
Sandbox & Pilot Migrations Full sandbox + pilot plans Limited No Often Informal
Manual validation & reconciliation Automated + manual QA No Yes (Manual) Heavy manual effort
Backup & rollback plan Robust procedures No No Often incomplete
Handles automation and integrations Full support Partial No Possible but fragmented
Post-migration engineer support Dedicated engineers No No Limited hiring support
Adaptable to API changes Proactive adaptation No Manual fixes Slower response
Turnaround / hiring predictability Predictable hiring timelines Fast but brittle Slow and manual Often slower
Data Security & Compliance High – enterprise grade Medium (depends) Low (manual) Hidden gaps common
Pricing predictability Transparent & fixed Low (per-job) Low (manual hours) High/variable OPEX
End-to-end project management Full E2E delivery & PM No No Often partial
Business impact & opportunity cost No diversion of staff No No Diverts engineering

What does an Engineer-led migration mean anyway?

Speed & Accuracy: Our Blended Method

We blend automation (smart scripts, bulk APIs) with human expertise for speed without risk. Our engineers manually check every mapping, validation, and exception.

You get:

  1. Speed of automation for bulk record migration
  2. Precision of engineers verifying integrity and business logic
  3. Pilot migrations and sandbox testing to catch issues early
  4. Real-time validation reports and rollback readiness
Result: 50x faster migrations than manual imports — with near-zero error rates.

Handling the Tricky Tech and API Details

The Loxo and Loxo APIs each behave differently, which is where our engineers shine. We build custom logic to handle the data quirks where generic tools typically break.

We handcraft API logic for:

  1. Field mapping and transformation
  2. Pagination, rate-limit handling, and throttling
  3. Preserving candidate history, resumes, and scorecards
  4. Syncing custom fields, pipelines, and scorecards without breaking structure
Our scripts: Natively retry failed calls, re-queue large attachments, and ensure data parity.

No Guesswork

We don't just promise smooth migrations—we measure and prove them. Every client receives a Migration Validation Report with all metrics.

Typical results across projects:

  1. 100% record-count parity between your Loxo data and Loxo
  2. Zero downtime during staged cutovers
  3. 99.9% attachment integrity (verified via checksum)
  4. Full automation and preservation of all business rules
Our standard: Includes full pipeline and scorecard preservation and 48 hours of engineer-assigned support post go-live.

We Adapt to Your Setup (Not the Other Way Around)

No two teams configure Loxo or Loxo exactly the same way—with unique hiring workflows and data. We customize every migration script to fit your exact workflow, pipelines, and scorecards.

Our engineers adapt for:

  1. Custom fields, hiring workflows, and scorecards
  2. Multi-brand or multi-role setups
  3. Historical imports and partial (date-based) migrations
  4. Integration re-mapping for HRIS, background-check, or assessment tools
The promise: If your data doesn't fit a standard template, we build one just for you.

Enterprise-Grade Security & Compliance

Your customer data is precious. Our migration process maintains the highest standards of security and regulatory compliance.

SOC 2 Type II

Independently audited compliance with rigorous security standards

ISO 27001

Certified information security management system

GDPR

Full compliance with EU data protection regulations

HIPAA

Certified for handling protected health information

AES-256 Encryption

Bank-grade encryption for all stored credentials

Latest TLS

Secure transfer protocol for all data in transit

Role-Based Access

We follow role-based access control for every migration project

Scheduled Deletion

Automatic data purging after migration completion

FAQ

Frequently Asked Questions

Everything you need to know about consolidating two Loxo instances. Can't find what you're looking for? Talk to our team.

Can I do a full Loxo-to-Loxo migration with CSV only?
No. Loxo's CSV export only includes fields visible on the People or Companies List view. Resumes, activity history, work experience, education, and attachments are excluded. Jobs cannot be imported via CSV at all. Loxo's free migration scope also excludes jobs, activities/events, and notes. For full-fidelity migration, you need the API or Loxo's paid managed migration service.
Does Loxo have a bulk migration API?
Loxo's Open API supports reading and writing individual records (People, Companies, Jobs, Applications, Attachments), but there is no documented bulk API for mass import/export. You need to paginate reads and loop through single-record POST calls, respecting undocumented rate limits. The person_events endpoint supports scroll_id pagination.
How do I preserve activity history in a Loxo-to-Loxo migration?
CSV exports strip activity history entirely. Use the Loxo API to extract activities (person_events) from the source instance, then re-create them in the target via API in chronological order, linking them to the correct People and Job records using an ID-mapping table. Note that intake notes and AI Notetaker transcripts are separate from person_events and require different handling.
What data typically breaks in a Loxo-to-Loxo migration?
Job associations, placements, person events, intake notes, file attachments, and dynamic fields are the usual failure points because they depend on correct load order, ID remapping, and separate API endpoints. Pipeline stage mismatches between instances also cause silent data corruption if not mapped before migration.
How long does a Loxo-to-Loxo migration take?
It depends on the method. CSV transfer of basic contact data takes hours. Loxo's managed migration service can take 2-4 weeks including the export request queue. An API-based migration with a dedicated engineer typically completes in 3-7 days for datasets under 100,000 records, though large datasets with hundreds of thousands of records can take longer due to rate limits.
How long does the Loxo to Loxo migration take?
Most migrations complete within 1–5 business days, depending on data volume and complexity. We provide a detailed timeline after the initial assessment and can often complete small migrations in under 24 hours.
Will my team lose access to Loxo during the migration?
No. Your source system remains fully operational throughout the entire migration. We run the migration in the background with zero downtime to your current operations.
Will there be downtime when migrating from Loxo to Loxo?
No. Our migration process is designed for zero downtime. We use a staged approach with background sync and a fast cutover, ensuring no disruption to your live business operations.
How do I validate that everything migrated correctly?
Every client receives a Migration Validation Report with comprehensive metrics including record-count parity, attachment integrity verification via checksum, and full audit logs. We also offer unlimited sample migrations so you can verify before committing.
Do I need professional help for this migration?
While simple migrations can sometimes be handled in-house, professional help ensures zero data loss, proper field mapping, and preservation of relationships between records. Our engineer-led approach catches edge cases that automated tools miss.
Does ClonePartner provide guidance before committing?
Yes. We provide a free consultation and assessment. We'll review your data structure, discuss your requirements, and provide a detailed migration plan and fixed-price quote before you commit to anything.

Still have questions?

Book a free 30-minute consultation with our migration engineers. We'll walk you through the exact approach for your Loxo→Loxo migration.

Contact our team

Ready to start your
Loxo Migration?

Join hundreds of businesses who have successfully migrated with ClonePartner. Let's discuss your migration needs and build a plan that works for you.

Book free consultation

Attention to Detail

We meticulously handle every aspect of your migration, ensuring no data is lost during transfer and mapping every field correctly between platforms.

Custom Solutions

Every business is unique. We tailor your migration strategy to match your specific requirements, workflows, and data structures.

Security & Compliance

Your customer data is handled with enterprise-grade security protocols, ensuring compliance with GDPR, HIPAA, and industry standards.