NetSapiens Migration RFP Template: 14 Partner Requirements
A strong NetSapiens migration RFP should evaluate more than price and timing. It should examine each vendor's source-platform experience, discovery process, automation capabilities, feature mapping, validation, testing, cutover planning, accountability, and post-cutover support.
An incomplete vendor evaluation can contribute to migration exceptions, delays, and subscriber issues that continue after cutover. A structured RFP helps service providers compare methodology, evidence, responsibilities, and support before selecting a migration partner.
The 14 requirements below can be used in a formal RFP, vendor scorecard, or migration-partner evaluation. Crexendo reports that its platform supports more than eight million users through a global community of more than 250 platform licensees, making repeatable migration planning increasingly relevant to the service-provider ecosystem.
Before Evaluation
Not every requirement will carry the same importance for every migration. Before issuing the RFP, identify any mandatory requirements a vendor must meet to proceed, then assign weights to the remaining criteria based on your environment, migration complexity, subscriber impact, and business priorities. This creates a consistent evaluation process while ensuring that critical requirements are addressed before vendors are compared by score.
Security and Data Handling
Migration work may require access to customer records, configurations, credentials, API keys, and other sensitive information. Before a prospective vendor proceeds to the scored portion of the RFP, evaluate how that information will be protected throughout extraction, transformation, testing, provisioning, and project closeout. Ask the vendor to document how migration data is transferred and stored, who can access it, what encryption and activity-logging controls are used, how credentials and API keys are secured, how long data is retained, and how it is deleted when no longer required. Look for written security controls, restricted and auditable access, defined retention periods, secure credential-management practices, and a documented data-disposal process. Vendors that cannot provide satisfactory evidence of these controls should not proceed to the scored evaluation.
How to Use This Template
Assign a weight to each requirement, score each vendor from 1 to 5, document the evidence provided, and calculate a weighted total. Mark any non-negotiable requirements as mandatory.
1: No demonstrated capability
2: Limited capability or insufficient evidence
3: Meets the basic requirement
4: Strong capability with supporting evidence
5: Proven capability with relevant references and documented results
The 14 RFP Requirements
1. Supported Source Platforms
What to evaluate: Documented experience on your specific source platform.
What to ask: Which platforms have you migrated from into NetSapiens, such as Metaswitch, BroadWorks, Ribbon, or 3CX? How many from ours specifically? Can you provide references?
What to look for: Named platforms, project counts, and references available on request.
2. Discovery and Pre-Migration Assessment
What to evaluate: A structured discovery process with written outputs before migration work begins.
What to ask: What does discovery produce? How do you identify exceptions, unsupported features, and data quality issues?
What to look for: A defined methodology with specific deliverables, such as an environment inventory and an exceptions list.
3. Automation Capabilities
What to evaluate: A clear breakdown of what is automated and what is still manual.
What to ask: Which parts of the migration are automated, such as extraction, transformation, provisioning, and validation? Where do engineers step in?
What to look for: A specific description of the automation framework, what it covers, and how it handles large subscriber volumes or multi-tenant environments.
4. Feature Mapping
What to evaluate: A written map of features from your source platform to NetSapiens, including how gaps are handled.
What to ask: How do you map our users and account hierarchy into NetSapiens resellers, domains, and configuration profiles? How do you handle features with no direct equivalent, such as call recording, receptionist consoles, or fax? Who owns those decisions?
What to look for: A sample feature mapping document and a clear gap-handling process.
5. Data Validation
What to evaluate: Migration validation before cutover, with defined checks and repeatable outputs.
What to ask: What checks are performed, at what stages, and at what level (user, domain, account)? What triggers a hold on cutover?
What to look for: A defined validation process with specific checks and clear go/no-go criteria.
6. Exception Handling
What to evaluate: A process for catching and resolving records that fall outside normal migration parameters.
What to ask: How are exceptions identified, who owns resolution, and how do they affect the timeline?
What to look for: A defined process with clear ownership and a resolution workflow.
7. Provisioning
What to evaluate: A defined provisioning process with verification steps and error correction.
What to ask: Is provisioning manual, automated, or a combination? Can it be staged by customer, domain, or reseller?
What to look for: A documented process, ideally automated, with error detection built in.
8. Test Plans
What to evaluate: A written plan for pre-cutover testing and validation.
What to ask: Do you test migrated configurations in a sandbox environment before cutover? Does testing include client-side checks in end-user apps such as SNAPmobile? What are the pass/fail criteria for cutover readiness?
What to look for: A sample test plan showing a structured, repeatable approach.
9. Rollback Plans
What to evaluate: How rollback or recovery is planned if an issue occurs during cutover.
What to ask: What would trigger a rollback, who makes the call, and what is the expected impact on subscribers?
What to look for: A written plan agreed before cutover, with clear responsibilities.
10. Ownership and Accountability
What to evaluate: Clear ownership of each phase, including decision rights and escalation paths.
What to ask: Who is the project owner on your side? What decisions can they make without escalation? What do you need from our team, and when?
What to look for: A RACI or equivalent matrix with named contacts and escalation paths.
11. SLAs and Performance Standards
What to evaluate: Written commitments for issue response and project performance.
What to ask: What do you commit to in writing, and how are those commitments measured? What happens if they are not met?
What to look for: Clear, written commitments that match the scope and risk of your migration.
12. Post-Cutover Support
What to evaluate: A defined support period after cutover, with response times and escalation contacts.
What to ask: What support do you provide after cutover, for how long, and what is the escalation path for critical issues?
What to look for: A written support plan specifying duration, response times by severity, and escalation contacts.
13. Customer References
What to evaluate: Recent references from service providers who migrated from your source platform at comparable scale.
What to ask: Can you provide references from comparable engagements? Do you have published case studies or documented outcomes?
What to look for: Reachable contacts and published outcomes. References on your exact source platform carry the most weight.
14. Success Criteria
What to evaluate: Written success criteria agreed before the engagement begins.
What to ask: How do you define a successful migration? Who signs off on completion, and what does sign-off require?
What to look for: A draft success criteria document or examples from past engagements.
Vendor Scoring Sheet
Set weights based on your priorities, score each vendor from 1 to 5, and multiply. The weighted totals show where each partner stands before conversations go further.
Planning a NetSapiens Migration?
The right migration partner should be able to demonstrate experience, methodology, validation processes, accountability, and measurable outcomes, not just make promises.
Download the RFP template and use it to compare vendors objectively. Then ask Vox Matic the same 14 requirements and see how our automation-led migration framework measures up.
Get the template. Compare your options. Make an informed decision.
Get the editable RFP template or contact Vox Matic to start the conversation.
It's that simple!
Frequently Asked Questions
What should a NetSapiens migration RFP include?
Requirements for source-platform experience, discovery, automation, feature mapping, data validation, exception handling, provisioning, test plans, rollback, accountability, SLAs, post-cutover support, references, and success criteria. Ask for written deliverables wherever possible.
What should we verify first?
Documented experience on your specific source platform. Ask for references from comparable engagements before any contract is signed.
How important is automation in a migration RFP?
For large or complex migrations, automation can significantly reduce repetitive engineering work and improve consistency. Ask partners to explain clearly what they automate, what remains manual, and why.
What should a rollback plan include?
Agreed triggers, who makes the call, how the team will respond, and the expected subscriber impact. Ask for it in writing before cutover is scheduled.
How should success criteria be defined?
In writing, before the engagement begins, covering accuracy, subscriber impact, cutover duration, and who signs off on completion.
Comments