Help4 Builder Import, Export and Migrations
Before the first click
Confirm what you are editing and where each kind of change belongs.
Read the page or template title first, select the exact element in the canvas or Navigator, then use the inspector tab that matches the job. This prevents a content change from becoming an accidental layout change.
Content
Change words, links, images, icons, data sources, shortcodes, and element-specific information.
Design
Change colors, typography, spacing, borders, radius, alignment, states, and desktop, tablet, or mobile values.
Advanced
Change labels, anchors, classes, attributes, visibility rules, motion, and other expert controls.
Page Settings
Use page-wide history, globals, publishing, template assignment, and recovery controls instead of editing one element.
Visual orientation
Match the screen before following the steps.
Open each image at full size. The numbered notes explain what the screen controls and what to confirm before changing customer content.
Screen 1
Templates in Studio
Browse reusable structures and choose an insertion or replacement path intentionally.
Confirm: the page title, selected item, plugin version, and intended responsive view match the task.
Screen 2
Template Library
Search page-purpose starters, insert a section, or deliberately replace a page instead of beginning from an empty screen.
Confirm: the page title, selected item, plugin version, and intended responsive view match the task.
Screen 3
Current Studio workspace
See the element library, device controls, live page frame, inspector, performance guidance, and save state together.
Confirm: the page title, selected item, plugin version, and intended responsive view match the task.
Screen 4
Builder Studio
Use the live page frame, element library, template library, inspector, responsive controls, performance guidance, and save state in one workspace.
Confirm: the page title, selected item, plugin version, and intended responsive view match the task.
Screen 5
Updates
Confirm the installed version, free update status, manifest URLs, beta or stable channel behavior, and package checks.
Confirm: the page title, selected item, plugin version, and intended responsive view match the task.
Watch the real workflow
Watch the clicks before making the change.
Use the narrated walkthrough first, then follow the written steps and verification checks on this page.
Lesson 34
Migration, Import, Export, and Cutover
Move Builder layouts and settings through guarded exports, structural checks, media mapping, and a verified launch sequence.
Read the complete transcript
- Inventory Before Moving
Open the migration and cutover tools only after inventorying pages, templates, global styles, custom fields, menus, forms, media, redirects, SEO metadata, commerce data, users, and addon dependencies. Record the source and target versions. A migration is more than copying page HTML.
- Export a Guarded Bundle
Export the supported Builder bundle and keep its manifest and checksum with the recovery record. Do not place credentials, private customer records, payment secrets, or unrelated uploads in a portable design package. When a script will run through WP CLI eval-file, avoid first-statement assumptions and preserve every host and dry-run guard.
- Import Without Replacing by Accident
Choose style-only, merge, or explicit layout replacement according to the migration plan. Verify the import target and expected current hash before the first write. Preserve stable element identifiers, parent relationships, extension data, and non-pack global tokens unless replacement was approved.
- Validate Then Cut Over
Check block counts, unique identifiers, parent and slot graphs, media URLs, forms, menus, responsive layout, Studio parity, public pages, SEO output, and logs before changing traffic. After cutover, verify redirects, canonical host, sitemap, cache, SSL, checkout bypasses, and the exact rollback path while the recovery window is still open.
Lesson 10
Templates, Site Kits, and Safe Imports
Choose reusable templates or style packs, understand import modes, and protect existing page content during application.
Read the complete transcript
- Browse Templates
Open Templates in Studio to browse reusable sections and page structures. Preview the purpose and responsive shape before inserting anything into the current page.
- Review Site Kits
Site Kits coordinate colors, typography, buttons, spacing, and related templates. Choose a kit that matches the site's purpose, not only its thumbnail.
- Choose the Right Mode
Use style-only application when existing content and block IDs must remain. Use a starter-layout replacement only when you intentionally want to replace the current structure.
- Verify the Result
After applying a template or kit, check content, links, global styles, desktop, tablet, and mobile. Use history immediately if the selected mode changed more than intended.
Migration workflow
Preserve structure before polishing the destination.
A successful migration keeps content, IDs, relationships, media ownership, URLs, responsive intent, and public behavior understandable.
Back up once
Keep a bounded recovery package and avoid filling the server with repeated archive copies.
No visual substitutions
Do not replace source media with merely similar images during migration.
No silent loss
Unknown namespaced extension data should survive a round trip.
Guided walkthrough
Make one verified change at a time.
Each step includes the action, why it belongs in this order, and the checkpoint to verify before moving forward.
-
Inventory the source
Record pages, templates, menus, custom fields, post types, forms, shortcodes, media URLs, redirects, and third-party dependencies.
Why nowStarting from a confirmed target prevents a correct edit from being applied to the wrong page, template, product, or responsive view.
Done whenThe inventory the source result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Export versioned data
Keep layout schema, global tokens, theme packs, template conditions, and namespaced extension data together.
Why nowCompleting and checking this step creates a known-good checkpoint before the next control changes the page state again.
Done whenThe export versioned data result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Map media and links
Preserve uploaded-media URLs when valid and explicitly map old source URLs, internal links, and canonical destinations.
Why nowCompleting and checking this step creates a known-good checkpoint before the next control changes the page state again.
Done whenThe map media and links result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Choose import mode
Use style-only for tokens, append for selected sections, and replacement only after confirming the target layout may be replaced.
Why nowCompleting and checking this step creates a known-good checkpoint before the next control changes the page state again.
Done whenThe choose import mode result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Check structure
Compare ordered element IDs, parent graph, content hashes, template assignments, and full-width/canvas settings before and after.
Why nowCompleting and checking this step creates a known-good checkpoint before the next control changes the page state again.
Done whenThe check structure result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
-
Run acceptance
Verify public and Studio styles, responsive widths, menus, forms, dynamic data, shortcodes, SEO, redirects, and logs.
Why nowThe final verification separates an editor preview from a result that is actually saved, responsive, interactive, and ready for visitors.
Done whenThe run acceptance result is visible, remains after reselecting the item, and has not changed unrelated content or styling.
How to know it worked
Verify the edit in Studio and on the real page.
A successful edit stays visible when the element is reselected, matches the intended responsive view, survives publish, and appears on the public URL without clipping or lost styling.
Studio preview
Reselect the element and confirm the saved value and visual result are still present.
Responsive preview
Check desktop, tablet, 390px, and 360px widths for overflow, squeezed controls, and inherited values.
Public page
Open the public route in a new tab after publishing and confirm content, interactions, assets, and spacing.
Recovery
If the result is wrong, stop editing and use History or a known-good revision instead of rebuilding the page.
Avoid the expensive mistakes
Stop when the page stops behaving predictably.
More edits do not repair a bad state. Preserve the evidence, return to a known revision, and reproduce the smallest failing action.
Changing several controls at once
Change one content, design, or responsive value, then confirm it in the preview. A small edit is easier to understand and recover.
Editing the wrong layer
Use Navigator and read the inspector heading. Deleting a parent section can remove every child even when the selected text or image looked harmless.
Checking only desktop
Review tablet, 390px, and 360px before publish. Width, gap, padding, type, alignment, controls, and menus can inherit differently.
Publishing before values persist
Reselect the element and reopen the responsive view. If the value disappears or another tab has a newer revision, reconcile it before publishing.
Continue learning
Use the next guide that matches the work in front of you.
The full tutorial hub remains available without repeating dozens of unrelated cards on this page.
Start here
Install and setup
Download the ZIP, activate Builder Suite, understand the blank-theme path, and run the first clean check.
First page
Build a page safely
Open Builder Pages, launch Studio, build structure first, check mobile, then publish or hand it to Help4.
Editor controls
Know which tab changes what
Use Content for information, Design for appearance and responsive values, and Advanced for identity, attributes, visibility, and motion.
Recovery
Edit without losing work
Replace media safely, recognize stale drafts, and restore a known-good page snapshot from Page Settings History.
Responsive
Control every viewport
Set spacing, widths, columns, alignment, and typography independently for desktop, tablet, and mobile.
Templates
Choose a starter
Pick a starter spec by page job: service, product, support, recent work, local SEO, launch, or checkout recovery.
Need help with this step?
Send Help4 the page, screenshot, or site goal.
Include the URL, what you are trying to build, what looks wrong, and whether this is a draft, staging site, or live customer page.