Overview
Migrating an on-prem Evoq deployment to Evoq OnDemand is a service request. This type of migration requires a paid Professional Services engagement (and often coordination with Sales) to assess your environment, scope the work, and provide a timeline and quote.
<supportagent>
Agent Notes
Investigation Summary:
Reviewed the request for general migration steps and pricing to move from on-prem Evoq to Evoq OnDemand, including a request to add an additional contact to communications, and identified the correct fulfillment path for this work.
Findings:
- This is not a break/fix support issue; migration from on-prem Evoq to Evoq OnDemand requires a paid Professional Services engagement.
- Professional Services scope includes assessing installed Evoq version, database size, and custom/third-party modules; defining migration scope; and executing planning through production (including upgrades and security monitoring as part of the SaaS offering).
- To route the request for scoping and quoting, required intake includes: (1) migration details and (2) the organization’s complete legal name.
- The request also included: adding additional stakeholders to correspondence and requesting direct outreach from Sales.
- No error message, stack trace, or technical failure symptoms were reported (informational/service request only).
- No Evoq version, database size, or customization inventory was provided at the time of review.
Escalation: Not applicable (Professional Services engagement/intake required).
Required intake fields: Migration details (current hosting, desired timeline, constraints, special requirements); organization complete legal name; installed Evoq version/edition (if available); database size and content volume (if available); custom modules/third-party integrations list (if available); additional contacts to CC (use placeholders like <cc_email>).
</supportagent>
Key Information
- This is a migration/service request; there is typically no error message to troubleshoot.
- End-to-end migration from on-prem Evoq to Evoq OnDemand is performed via a paid Professional Services engagement (not standard support).
- Professional Services will assess your environment (Evoq version, database size, custom/third-party modules), define scope and approach, and execute the migration from planning through production.
- The engagement may include required upgrades and includes SaaS security monitoring as part of the OnDemand solution.
- Pricing and timeline are provided after scoping and depend on complexity (version, database/content volume, customizations/integrations, and timeline constraints).
Customer Impact
Action required: Provide the intake details below so the request can be routed for scoping and a quote/timeline.
Expected outcome: You receive confirmation that the request has been routed to Professional Services (and Sales, if requested), followed by a scoped migration plan and pricing/timeline based on your environment.
What to provide to start the migration intake
- Migration details (what you are moving, desired target date/timeframe, critical constraints, and any special requirements).
- Your organization’s complete legal name (required for routing/engagement intake).
- If available, include:
- Current Evoq version/edition
- Approximate database size and file asset volume
- List of custom modules and third-party integrations
- Any compliance/security requirements
- If additional stakeholders should be included, provide the email address(es) to CC (for example:
<cc_email>). - If you want pricing/contracting outreach, request that Sales contact you directly.
How to verify you’re on track
- You receive confirmation that the request has been routed to Professional Services (and/or Sales, if requested).
- Professional Services provides a scoped plan and a quote/timeline based on an assessment of your environment.
Frequently Asked Questions
- 1. How do I know my request requires Professional Services?
- If you are asking to migrate from an on-prem Evoq instance to Evoq OnDemand (including data/content movement and environment setup), it requires a paid Professional Services engagement rather than standard support troubleshooting.
- 2. Can Support provide an exact migration cost without details?
- No. Pricing depends on your environment complexity (Evoq version, database size, custom modules/integrations, content volume, and timeline). Provide migration details and your organization’s complete legal name so the request can be scoped and quoted.
- 3. What information should I gather before asking for the migration?
- Provide (1) migration details and (2) your organization’s complete legal name. If possible, also include your current Evoq version/edition, database size, asset volume, and a list of custom modules and third-party integrations.
- 4. When should I ask for Sales to get involved?
- If you want direct outreach regarding purchasing Evoq OnDemand or to discuss commercial terms alongside the migration engagement, request Sales contact as part of your request.
Priyanka Bhotika
Comments