Introduction
This guide explains the full V1 → V2 migration process, what you need to prepare, what to review on staging, and how ads can be handled before or after launch.
What to expect after moving to V2
Your website domain stays the same
After launch, your public website will continue to use the same domain (for example:
www.yourwebsite.com). Visitors won’t need to change anything.Your dashboard (admin) link will change
After moving to V2, the dashboard/admin URL will change.
We will share the new dashboard link with you after the launch so you can log in , share it with your team and continue managing your website as usual.
Before you start
Confirm custom features compatibility (outside the migration scope)
If your current V1 website includes custom features (custom layouts, custom blocks, special integrations, custom code, etc.), these may not be available in V2 by default.
Important: verifying, rebuilding, or re-implementing custom features is not included in the standard V1 → V2 migration scope.
Please contact Support before starting the migration so we can:
confirm whether your custom features are supported in V2,
propose alternatives if needed,
and (if required) provide a separate estimate for additional work.
Migration steps
Step 1: Confirm the migration scope and estimate with Support
Before we start the migration, please contact Support to confirm:
The expected scope of the V1 → V2 migration for your website
The estimated number of hours and the applicable hourly rate
Any constraints related to timelines (e.g., planned launch date)
✅ Once Support confirms the estimate and you approve it, we can proceed to the next step.
Step 2: Choose your V2 template
V2 staging is built based on a selected template/theme.
Browse the available templates here:
https://www.newsifier.com/pick-a-template?theme=All+ThemesChoose the template you want your website to look like.
Send the template name (or link) to Support.
Step 3: We build your staging environment
After you select a template, our team will build a staging website based on your choice.
Staging content note (dummy content)
Staging is created for layout and functionality testing.
Article content, titles, images, menus, and pages may appear as dummy/testing content.
Your goal is to review the design and behavior, not the editorial accuracy of the content.
Step 4: Review staging (testing checklist)
Once the staging environment is ready, we’ll share it with you for review.
Note: Staging uses dummy content for testing. During this phase, you cannot verify real content or final destinations (e.g., whether a menu item points to the correct final page). Please focus on layout, design, and how the website behaves when you interact with it.
What to review on staging
Page templates
Homepage
Category/section pages
Article pages
Any special templates used on your site (if applicable)
New V2 layout (most important)
Since V2 introduces new layout, please verify that each one:
Colors
Typography (font sizes, headings, body text)
Looks correct (spacing, alignment)
Works correctly (opens/closes, clickable elements, no overlap)
Displays properly on mobile and desktop
Examples of components to test (depending on what’s enabled on your site):
Header (sticky behavior, hamburger menu, dropdown menus)
Search UI (open/close and layout)
Article modules (featured image, captions, embeds, quote blocks, lists, galleries if used)
“Most read” / “Trending” / “Related articles”
Social share buttons (layout + interaction)
Author name display, tags, and breadcrumbs (if used)
User features (if enabled): test that comments work as expected (viewing, posting, moderation/visibility rules), and that login/account flows function properly (log in, log out, password reset, and any account-related pages).
Responsiveness
Test on at least:
Mobile
Desktop
Look out for:
Overlapping elements
Broken layouts
Images/embeds not scaling correctly
Buttons/menus that are hard to tap on mobile
How to share feedback
Collect your feedback in one drive document and share it with us so we can address it before launch.
When reporting issues, please include:
Screenshot (or short screen recording)
Device + browser (e.g., iPhone Safari / Desktop Chrome)
Steps to reproduce (if needed)
Expected vs actual result
Priority: Blocker / Major / Minor
Step 5: Schedule the launch
Once staging is approved and everything looks good, we can schedule the launch.
Ads setup options
You can choose one of the following approaches:
Option A: Ad agency sets up ads before launch (recommended)
The ad agency sets up ads on staging
During launch, we automatically copy the ad setup from staging to the live site along with the layout changes.
Option B: Ad agency sets up ads after launch
If the client or the ad agency prefers to configure ads on the live site after launch, please check this guide:
https://support.newsifier.com/en/articles/13334668-setting-up-ads-on-the-live-site-after-launch-ad-agencies
What’s included in the basic V1 → V2 transition
The basic V1 → V2 transition includes:
Building a V2 staging environment based on your selected template
Sharing staging for layout/functionality review
Performing the agreed go-live switch to V2
What’s not included (adjustments after the transition)
The basic transition does not include post-launch adjustments, such as:
Design/layout changes beyond the selected template setup
Extra styling requests (spacing, fonts, colors) beyond standard template configuration
Adding/rebuilding custom features from V1
Additional iterations after staging approval
Any extra requests made after the go-live
If you request changes outside the basic transition scope, these will be quoted separately or billed hourly based on the agreed rate.
Additional work & billing note
The migration estimate covers only the basic V1 → V2 transition described in this article.
Any additional work or adjustments requested (before or after launch) are not included and will be billed separately based on the agreed hourly rate.
Need help?
If you’re unsure about:
template selection,
what to review on staging,
ad setup approach,
or whether your V1 custom features are supported in V2,
contact Support and we’ll guide you through the best path.
