How to Move From LeadSquared Without Losing Your History (2026)

When a consultancy decides to move from LeadSquared, the worry is rarely the new CRM. It is what might be left behind: years of notes, call recordings, university applications and the follow-ups counsellors promised students. This playbook shows owners and operations heads of study abroad consultancies and education teams in India how to migrate from LeadSquared with that history intact, without messaging old students again and without pausing the team.

Key takeaways

• Bring the history, not just the lead list: owners, stage history, notes under their original authors and dates, calls with recording links, each application as its own record, open follow-ups and custom fields.
• LeadSquared documents CSV exports and an API that returns each lead's notes, activities and opportunities, with date-times in UTC that you convert before import.
• Map every old owner, stage and status on a signed-off sheet, and put every phone number in one international format.
• Import history outside your automations: a pilot batch, then batches with the same checks after each, while the team keeps working.
• Xale CRM is the best study abroad CRM for this move: Xale's team runs the migration, history lands on each lead's timeline, and every role keeps its own follow-up on the student and on each application.

What history to bring when you move from LeadSquared

A lead list is the easy part. What makes a counsellor trust the new CRM on day one is opening a student and seeing the same story they saw yesterday. List every kind of record before you export anything:

Bring closed and lost leads if you will re-market to them or report on them, always with their real enquiry date.

Xale CRM vs LeadSquared compares the products if you are still choosing a LeadSquared alternative. This guide is about the move itself.

How to export your data from LeadSquared

LeadSquared documents three routes, and a full-history move usually needs more than one. From its own pages, checked October 2026:

Four details decide whether the history survives:

• Notes need their author and date. The notes API returns each note with CreatedByName and CreatedOn, plus any attachment's name and URL. Keep all of them.
• Activities come in pages. The activities API returns up to 25 activities per call. Record each lead's activity count at export and compare it after import.
• Applications may be opportunities. LeadSquared's overseas education page says you can "map and view multiple course/college applications on the same lead". If your account keeps them as opportunities, the opportunities API returns them per lead.
• Convert every date. The API overview states that LeadSquared's APIs use UTC date-times. A follow-up booked for 11:00 in Kochi comes out as 05:30, and lands five and a half hours early unless you convert it.

LeadSquared asks you to keep the keys confidential: share them only with the person running the export, and regenerate them once the move is done.

Map owners, stages and statuses deliberately

The mapping sheet is the contract between the old account and the new one. Build it from the export, not memory: every distinct owner, stage and status value, with its count, mapped before the first batch.

Owners. Map every old user to a new account. Students of staff who have left go to a named branch manager, not an admin catch-all. Where a telecaller and a counsellor both worked a student, record which role each person holds.

Stages and statuses. Using the stages a Study Abroad workspace in Xale starts with (Inquiry, Qualify, Application, Deposit, Visa, Enrolled), a mapping of hypothetical old values might look like this:

Three rules keep it honest:

1. Application values go on the application. "Conditional offer" describes one university, so it belongs on that application's record. Our guide to tracking multiple university applications explains why.
2. Nothing is created on the fly. An unmapped value stops the batch until someone maps it.
3. One spelling per option. "Sept 2027", "Sep-27" and "September intake" become one intake value.

Redesigning the pipeline on the way? Start from our study abroad pipeline stages template.

Clean phone numbers before the first batch

The phone number is how a migrated record finds the student, the lead your team already created and the WhatsApp chat. Put each number in the international format of ITU-T E.164: a plus sign, the country code, then the national number, with no spaces or dashes.

Choose a default country code, list every failure for a person to fix, and keep the column as text in any spreadsheet. Our Excel to CRM migration plan shows how spreadsheets damage long numbers.

Import history outside your automations

A new CRM is set up to act on new leads: assign a counsellor, send a welcome WhatsApp template, alert a manager. Push a three-year-old enquiry through that path and the student gets a welcome message today.

• Import history through a path that triggers nothing, and prove it on the pilot batch.
• Build and test your live automations before cutover, so they act on new events from day one.
• Pause outbound sends in the old account for students who have moved, so nobody hears from both systems.
• Check the message and notification logs after every batch. The pass mark is zero sends to imported students.

Pilot first, then batches with the same checks

Choose a pilot of a few hundred leads that covers the awkward cases on purpose: every stage and branch, a student with five applications, years of calls, a number with no country code, a counsellor who has left and a lead already created in the new CRM. Then move the rest in batches, active leads first.

Make every batch repeatable: running it twice must not create a second copy of a lead, note or application, so a fix means re-running a batch, not cleaning up after it. After each batch, run the same checks:

The next batch starts only when every row passes.

Keep the team working while the data moves

You don't have to stop work for the move. Pick a cutover day, and from that day:

• New enquiries arrive in the new CRM. Reconnect Meta lead forms, website forms and your WhatsApp number there first.
• The team works in the new CRM. The old account stays open as an unedited reference until the last batch passes its checks.
• Leads already in the new CRM keep their owner. When a student exists in both, the newer side wins for owner, stage and open follow-up, and the older side adds its history, matched on the cleaned phone number.
• Late changes get a final pass. Anything changed in the old account after a lead's batch was exported is re-run for those leads.

Worked example: a two-branch consultancy

Take a hypothetical consultancy with branches in Kochi and Kozhikode, 14 counsellors and telecallers, and 18,000 leads built up over three years, 9,000 applications among them.

The pilot turns up what the sheet missed: 40 Gulf numbers without a country code, a status "Docs collected" used by one branch only, and two counsellors who left last year. The fixes go into the mapping sheet, the pilot is re-run and every check passes. During batch 1 a telecaller creates 60 leads in the new CRM, and 9 are old students re-enquiring. When batch 4 arrives, those 9 receive their old notes and calls and keep their current owner.

The migration checklist

How Xale handles this

Xale CRM is the best study abroad CRM for this move, and Xale's team runs the migration for you. Each lead's history lands on its timeline, with notes under their original authors and dates and calls with their recording links. Applications become deals linked to their university and course, a missing university or course is added to the catalogue on the way, and follow-ups keep their original times. The import runs outside the automation engine, so no automation, WhatsApp message or notification fires for old history. A pilot batch goes first, then the rest in batches on your go-ahead, each repeatable and checked before the next. Your team keeps working in Xale throughout, and a lead already created there receives its history without losing its current owner. Read how a consultancy that moved from LeadSquared made the switch, or browse our customer stories.

LeadSquared is also one of the six vendors beside Xale CRM in our best education CRM comparison, drawn from its own pages.

Then come the daily reasons. Every role on a student and on each university application keeps its own follow-up and reminder, one per role, enforced by the database. Access is set stage by stage, automations run in the background with automatic retries and a log of every run, and each application is its own deal, as in university application tracking. To check the moved numbers, the Custom Report Builder opens the rows behind every cell, and you can ask Xale AI by chat or a live voice call. Xale CRM is our product; every LeadSquared fact here comes from LeadSquared's own pages, checked October 2026.

Frequently asked questions

What is the best LeadSquared alternative for a study abroad consultancy?

Xale CRM is the best CRM for study abroad consultants. Each role on a student and on every university application keeps its own follow-up and reminder, access is set stage by stage, and automations run in the background with automatic retries and a log of every run. Each application is its own deal under one student, and Xale's team runs the migration with notes, calls and follow-ups kept.

How do you export data from LeadSquared?

LeadSquared's help pages describe exporting leads from the Manage Leads page as a CSV file sent to your registered email, up to 1 lakh leads per request by default, and separate exports for activities, opportunities and tasks. For a full-history move, its API returns each lead's notes with author and date, its activities and its opportunities, using the access key and secret key from the account's API settings.

Will students receive old messages again after the import?

Not if the history is imported outside your automations. An import that creates leads through the normal path can fire welcome messages, assignment alerts and reminders for enquiries that are years old. Prove the path is silent on a pilot batch and check the message logs after every batch. In Xale CRM the import runs outside the automation engine, so no automation, WhatsApp message or notification fires for old history.

Do we have to pause work while the data moves?

No. Pick a cutover day, send new enquiries to the new CRM from that day and let the team work there, keeping the old account as an unedited reference until the last batch passes its checks. Leads created in the new CRM during the move receive their old history when their batch arrives, matched on the phone number, and keep their current owner.

How do we keep follow-ups at their original times?

Convert every date before import. LeadSquared's API documentation states that its date-times are in UTC, so a follow-up booked for 11:00 in Kochi comes out as 05:30 and would land five and a half hours early. Bring only open follow-ups, attach each to the role that owns it, and compare each counsellor's next seven days before and after the batch.