Vendors answer the question they are given. If your request for proposal says only that you want to move your CRM to HubSpot, you will get quotes for different projects, written in different formats, built on different assumptions. They cannot be compared, and the gaps show up later as change requests.
A CRM migration RFP template fixes that. It gives every vendor the same scope, the same questions, and the same format for the answer. This guide walks through each section of the RFP, what to put in it, and the CRM migration vendor questions that separate a vague proposal from a usable one. It ends with a scoring matrix and a list of questions for the demo. Where it helps, it also shows how SuprSwitch, SuprDense’s CRM migration platform, answers the same questions, so you can see what a specific answer looks like.
What to Include in a CRM Migration RFP
An RFP is a short, structured document. Most of the work is in being specific about your own situation, because the vendor can only be as precise as you are. A useful RFP has ten parts.
| RFP section | What you write | Why it matters |
|---|---|---|
| 1. Background and goals | Who you are, why you are moving, and what success looks like | Vendors design for the outcome, not only the transfer |
| 2. Scope | Source CRM, destination HubSpot plan, what is in and out of scope | Keeps quotes for the same work |
| 3. Data and objects | Record counts, custom objects, history to keep | Drives effort and the HubSpot plan you need |
| 4. Integrations and automations | Connected tools, workflows, reports | These are rebuilt, not copied |
| 5. Security and compliance | Access, certifications, data handling, privacy terms | Decides who may touch your data |
| 6. Testing and acceptance | Pilot, reconciliation, sign-off rules | Defines what done means |
| 7. Timeline, roles, and pricing | Dates, your team, the format for the price | Makes quotes comparable |
| 8. Response format | Questions the vendor must answer, in order | Makes scoring possible |
| 9. Evaluation criteria | How you will score the responses | Vendors see what you value |
| 10. Process and deadlines | Deadline for questions, response date, demo window | Keeps the process on schedule |
Send the same document to every vendor, and share any answer you give one vendor with all of them. This applies whether you are asking a freelancer, an agency, or a firm that offers CRM migration services. A vendor that cannot answer the questions in a structured way is telling you something before the project starts.
Define Business Goals and Scope
Start with why you are moving. A migration to cut license cost, a migration to unify marketing and sales data, and a migration forced by a contract end date lead to different priorities, and vendors should know which one is yours.
Then write the scope as a list of what is in and what is out. Name the source CRM and version or edition, the HubSpot subscription you have or plan to buy, and the teams that will use the new system. Say which objects must move, which data you are happy to leave behind, and whether anything else is part of the project, such as new pipelines, new properties, or training.
Decide early whether you want a pure migration or a migration plus a redesign. They are different projects with different quotes, and mixing them in one RFP is a common source of confusion. Our guide to CRM migration vs. implementation explains where they overlap and how to sequence them.
Include the constraints that vendors cannot guess:
- A fixed go-live date, and the reason for it, such as a renewal or a launch.
- A freeze period when nobody can change data in the source system.
- The people on your side who can make decisions, and how quickly they can answer.
- Budget range, if you are willing to share it. It lets vendors propose the right size of project.
Document Data and Object Requirements
This is the section that most changes the quotes. Give vendors numbers, not descriptions. A vendor who has to guess the size of your data will either quote high to cover the risk or quote low and revisit the price later.
Ask for a data inventory from your own team before you write the RFP, and include it:
- Record counts. Contacts, companies, deals, tickets, and any other standard object, with the number of records for each.
- Custom objects and fields. A list of custom objects, with record counts and the main relationships between them. HubSpot custom objects need an Enterprise subscription, so say which plan you are on.
- History to keep. State how far back you need emails, calls, meetings, notes, and tasks, and whether attachments must move.
- Data quality. Known duplicates, records with no email address or company domain, and fields nobody uses.
- What you can leave behind. Closed records, old campaigns, and unused fields. Every record you do not move is time you do not pay for.
It helps vendors to know how the destination works. HubSpot matches contacts by email address and companies by domain name, and an import without a unique identifier creates duplicates. HubSpot also limits how much you can import at once. On a paid account, an import file can be up to 512 MB and 1,048,576 rows, with up to 10,000,000 rows and 500 imports in a rolling 24 hours. Large data sets are split and sequenced, and that planning is part of the vendor’s work.
Ask the vendor how it will move activity history. HubSpot’s import tool can create emails, meetings, notes, and tasks, but it cannot update the ones that already exist, so a mistake in an activity load cannot be fixed by importing the file again.
Finally, ask which method the vendor will use. HubSpot’s Smart Transfer is built for a one-time, one-way migration from a fixed list of apps, and it can only be run by a Super Admin. Mapping your own custom fields through it requires a Data Hub subscription, and it does not transfer custom objects. If your source app is on the list, ask how the vendor uses Smart Transfer and what it does outside it. If it is not on the list, ask how the data will move instead.
A migration platform is one answer to that question. SuprSwitch connects to the source CRM and to HubSpot through their APIs and maps any field or object that lives in the source CRM, including custom objects, along with activities, owners, and associations. Its Schema Analysis phase also produces much of the data inventory above: every custom field, record count, and property type, with duplicates, empty required fields, and broken associations flagged before any data moves.
List Integrations and Automation Dependencies
A CRM rarely works alone. List every tool that reads from or writes to it: email, calendar, billing, support desk, marketing platform, data warehouse, forms, and any custom API connections. For each, give the owner on your side and what would break if it stopped.
Automations need the same treatment. Workflows, assignment rules, scoring, approvals, and scheduled reports are logic, and logic is rebuilt rather than moved. HubSpot’s import and transfer tools carry data, not the rules around it. HubSpot workflows also need a Professional or Enterprise subscription, so the plan you buy affects what can be rebuilt.
Ask each vendor to respond to this table for your list:
| Dependency | What the RFP should say | What the vendor should answer |
|---|---|---|
| Connected apps | Name, owner, direction of sync | Reconnect, replace, or retire, and who does it |
| Workflows and rules | Count, purpose, owner | Which are rebuilt, simplified, or dropped |
| Reports and dashboards | The ones you rely on weekly | Which are rebuilt and how they are checked |
| Custom code and APIs | Where it exists, what it does | How it is reviewed and what it costs |
Do not let the answer be that integrations are handled during the project. Each integration is either in the quoted scope or it is a change request, and you want to know which before you sign.
Specify Security and Compliance Needs
Your CRM holds personal data and often commercial data that competitors would value. The RFP should say plainly what you require, and it should ask for evidence, not only promises.
What to ask for
- Access. Who will have access to the source CRM and to HubSpot, at what permission level, and when it will be removed. Ask for named people and a removal date.
- Data handling. Where data is stored during the project, how it is transferred, whether copies are kept, and how they are deleted when the project ends.
- Certifications. Ask for any security reports the vendor holds and when they were issued. A SOC 2 report comes in two kinds: Type 1 looks at controls at a single point in time, and Type 2 looks at whether they operated over a period. ISO/IEC 27001 is a standard for an information security management system, and organizations can choose to be certified against it. Ask what the certification covers, because it may not cover the team assigned to your project.
- Privacy terms. If you process personal data about people in the EU or UK, the vendor will normally be a processor. Article 28 of the GDPR requires a contract that binds the processor to your instructions, covers subcontractors, makes information available for audits, and provides for deleting or returning personal data when the service ends. Ask to see the vendor’s data processing terms and subprocessor list before you sign.
- Incident handling. How you will be told about a problem, and how fast.
Do not treat a certificate as a replacement for these questions. It tells you the vendor has a security program. It does not tell you how your data will be handled on this project.
Hold every vendor to this standard, including us. For SuprSwitch, the specific answers are that data moves directly from the source CRM to HubSpot under a no-storage architecture, so it is never held on SuprSwitch servers, and that on SuprDense’s Salesforce to HubSpot migrations the OAuth tokens used for access are revoked after each migration. Ask for the same detail, in writing, from every vendor you shortlist.
Set Testing and Acceptance Criteria
Testing is where a migration is proven. Write the acceptance rules into the RFP so that every vendor prices the same amount of testing, and so that you know in advance what you will sign off.
At minimum, ask for:
- A pilot. A trial migration of a representative sample, with the records and the checks described. A pilot proves the mapping works, not that the full run will be perfect.
- Reconciliation. Record counts compared against the source for every object, with differences explained.
- Association and property checks. Spot checks that contacts, companies, and deals are linked correctly and that key properties carry the right values.
- Workflow and integration tests. Each rebuilt workflow tested with test records before it is switched on.
- User acceptance testing. Named people on your side test the daily tasks and sign off in writing.
As a reference point, SuprSwitch builds the pilot into its process. Its Pilot Validation phase runs a sample migration before the full run and checks relational integrity, activity history formatting, field truncation, and association chains. During Final Execution, real-time record validation flags any record that does not appear in HubSpot within the expected window, and a retry mechanism re-runs failed records without restarting the job.
Ask where the pilot will run. HubSpot’s standard sandbox needs an Enterprise subscription. It copies your setup and, if you choose, your 5,000 most recently updated contacts with up to 100 associated deals, companies, and tickets for each. Emails sent from a sandbox to people who are not sandbox users will not send, which keeps test data from reaching real customers. If your plan does not include a sandbox, ask where the vendor will test and how it will protect live data.
Also ask what happens if the migration fails acceptance. A good proposal says how problems are fixed, how long the vendor stays engaged, and what the rollback or correction path is.
Request Timelines, Roles, and Pricing
Ask for a timeline built from phases, not a single number: discovery, mapping, pilot, full migration, validation, go-live, and support. For each phase, ask what the vendor needs from you and by when. Most delays in migration projects come from waiting for decisions and access, so the vendor’s assumptions about your response times matter as much as its own work.
For comparison, SuprSwitch runs a migration in four phases, Schema Analysis, Mapping Logic, Pilot Validation, and Final Execution, typically over 3 to 4 days. A proposal laid out in phases like these makes it easy to see where your decisions are needed.
Ask for a roles table covering both sides: who leads the project, who maps the data, who approves the mapping, who tests, and who signs off. Ask the vendor to name the people it will assign, not just job titles.
For pricing, set the format so quotes line up. Ask each vendor to price separately:
- Discovery and mapping
- Data migration, by object where relevant
- Workflow and integration rebuilds
- Testing, pilot, and go-live support
- Post-migration support, with the period and hours included
- Any third-party software or licenses the vendor expects you to buy
Then ask for the assumptions behind the price: the record counts it used, how many workflows, how many integrations, and what happens if those numbers change. Ask how change requests are priced and approved. A fixed price with hidden assumptions is not cheaper than a time-and-materials quote with clear ones.
Record counts usually drive the price. SuprDense prices SuprSwitch migrations on the total number of records in the source CRM, with self-service, guided, and custom options, so the counts in your data inventory feed directly into the quote.
Do not forget your own costs. The HubSpot subscription, your team’s time for decisions and testing, and any overlap while both systems run are outside the vendor’s quote, but belong in your budget.
Vendor Scoring Matrix
Score every response against the same criteria, written before the proposals arrive. That keeps the decision about fit, not about the best presentation. Use two steps: a pass or fail gate, then weighted scores.
Step one: must-haves
Some requirements are not a matter of degree. If a vendor cannot meet them, it does not go through to scoring. Typical examples are accepting your data protection terms, naming the people with access to your data, and committing to a written scope.
Step two: weighted scoring
Give each criterion a weight that adds up to 100, then score each vendor from 1 to 5. The weights below are an example and should reflect your priorities.
| Criterion | Weight | Vendor A (1 to 5) | Vendor B (1 to 5) |
|---|---|---|---|
| Experience with your source CRM | 20 | 4 | 5 |
| Data mapping and validation approach | 20 | 5 | 3 |
| Security and compliance | 15 | 3 | 5 |
| Integrations and automation rebuild | 15 | 4 | 3 |
| Testing and acceptance plan | 10 | 4 | 3 |
| Timeline and team | 10 | 3 | 4 |
| Pricing clarity and assumptions | 10 | 5 | 3 |
| Weighted total (out of 100) | 100 | 81 | 76 |
The weighted total is each score multiplied by its weight, added together, then divided by 5. For vendor A that is (20 x 4 + 20 x 5 + 15 x 3 + 15 x 4 + 10 x 4 + 10 x 3 + 10 x 5) divided by 5, which is 81. For vendor B it is 76. The numbers are illustrative, not a benchmark.
Two habits make the matrix more useful. Have two or three people score separately before comparing, and ask for references before the final decision. A reference from a project like yours, with a source CRM like yours, is worth more than a polished proposal.
Questions to Ask During Vendor Demos
A demo shows how a vendor communicates and what it has built before. Use it to test the answers in the proposal, not to repeat them. These questions work for any vendor.
| Area | Questions |
|---|---|
| Experience | How many migrations have you done from our source CRM to HubSpot? What went wrong on the last one, and how was it fixed? Can we speak to that client? |
| Method | Will you use Smart Transfer, imports, the API, or a mix? Why? What does each move, and what is left for manual work? |
| Mapping | Can you show a sample mapping document with client details removed? How do you handle fields that have no destination? |
| Testing | Where will the pilot run? How many records, and what will it prove? How do you reconcile counts against the source? |
| Automation | Which of our workflows will you rebuild, and which will you advise dropping? How is each one tested? |
| Security | Who will have access to our data? Where is it stored during the project? How and when is it deleted? |
| Team | Who works on our project day to day? What happens if that person leaves? |
| Change | How are scope changes raised, priced, and approved? What is outside this quote? |
| After go-live | What does support cover, for how long, and who answers when something breaks? |
Pay attention to how specific the answers are. A vendor that has done the work can describe what went wrong. A vendor that has not will talk about its process in general terms.
The most useful demo uses your own data. SuprSwitch offers a free sample migration, so you can check the mapping on a slice of your records before you commit, and you can ask other vendors for the same.
Conclusion
A good CRM migration RFP is specific about your data, your integrations, your security requirements, and how the work will be tested. It asks every vendor the same questions in the same format, and it tells them how you will score the answers. That is what makes a CRM migration proposal comparable, and what protects you from a project that grows after the contract is signed.
Frequently Asked Questions
01 What should a CRM migration RFP include?
It should include your goals, a written scope, a data inventory with record counts, a list of integrations and automations, security and compliance requirements, testing and acceptance criteria, the timeline and roles, the pricing format you want, and the criteria you will use to score the responses.
02 How do you evaluate CRM migration vendors?
Set the criteria before proposals arrive, apply a pass or fail gate for must-haves, then score each vendor against the same weighted criteria. Check references from migrations similar to yours, and compare what each quote includes and leaves out, not only the total.
03 Should an RFP include data security requirements?
Yes. State who may access your data, how it is handled and deleted, and which security evidence you expect. If you process personal data about people in the EU or UK, ask for the vendor’s data processing terms, because the GDPR requires a contract with a processor.
04 How should vendors be compared?
Send every vendor the same scope and the same questions, and ask for pricing in the same format. Score the responses against the same weighted criteria, with more than one person scoring, and test the answers in a demo. A sample migration on your own data, which SuprSwitch offers free, is a quick way to compare mapping quality.
05 What deliverables should be included in a migration proposal?
A written scope, a source-to-HubSpot mapping, a timeline with phases, a named team, a pilot plan, a validation and acceptance plan, rebuilt workflows and integrations if they are in scope, a price with its assumptions, and a support period that says what it covers.
Manual migrations cost more than engineer hours.
Skip the QA cycles, data cleanup, and errors found weeks after go-live. SuprSwitch runs the full migration in 3-4 days, validated record by record.