When choosing a CMS or changing website suppliers, export a sample of products, Chinese and English content, and attachments. Import and edit it in the receiving system, then simulate source-site unavailability to test independent use. Record field meanings, translation gaps, actual files and target-record mappings. For the full handover, follow the asset, account, restoration, migration, cutover and maintenance steps below.
When changing website suppliers or moving to a new CMS, use six steps: inventory assets, confirm account access, restore an isolated copy, test content migration, switch production, and complete the handover. The company should receive the agreed materials, enter the authorized management accounts, and have the incoming team restore representative pages independently. Record each asset, owner, test result and outstanding item before scheduling the switch.
This guide is for business websites with product information, news and bilingual enquiries. It covers operational takeover and redesign migration. The project agreement and applicable licenses determine the delivery and use of materials, source code and services. Use the source-code and SaaS cost guide to budget separately for export, conversion, restoration and ongoing maintenance.
1. Inventory deliverables and verify retrieval
Appoint a company handover owner. The outgoing supplier provides the materials, and the incoming technical team verifies them. Record the site, provider, company recipient, version or backup time, delivery location, verification task, result and deadline. Keep receipt status in the ordinary checklist; transfer credentials and backups containing customer information through an authorized secure channel.
| Asset | Deliverable | Verification |
|---|---|---|
| Domain and DNS | Registration and DNS services, expiry, management arrangements and existing records | An authorized company representative signs in and checks the domain, recovery contacts and renewal owner |
| Application and theme | Agreed source, custom changes, dependency lock files, theme versions, build artifacts or instructions | The incoming team deploys the package and checks the running version |
| Database | Backup time, database version, export method and data scope | Restore to a separate database and check records by site and language |
| Images and downloads | Original files, directory structure, revisions and page references | Open sample images and manuals; verify links and file contents |
| Runtime configuration | Environment notes, configuration inventory, storage, scheduled tasks and queue arrangements | Authorized staff configure the test environment and inspect the running tasks |
| External services | Email, analytics, search tools and CDN accounts, with renewal owners | Verify each login or authorization, service target and notification channel |
| Historical enquiries | Agreed records, sources, timestamps and follow-up arrangements | Sales checks counts, samples and access rights |
Record file package sizes and checksums, and corresponding database and attachment backup times. Mark each item as required, available under the agreement, or awaiting confirmation. The recipient signs off after testing usability; every unresolved item receives a named contact.
2. Test editing access, account transfer and independent deployment separately
An editor account supports daily content work. Domain, cloud, platform owner and billing accounts control the underlying resources. An authorized company representative should sign in and check the organization, recovery email, verification methods, active services and renewal responsibility. For a supplier's shared account, agree on project access or the provider's supported transfer procedure before acting.
A registrar transfer, a DNS change and a hosting migration each need their own steps. When changing hosting, identify the DNS records to change and preserve the records used by company email. Follow the current provider's procedure for registrar or registrant changes. Save the existing configuration and rollback conditions before execution.
A transfer within a platform and an export to another system have separate scopes. Wix's site transfer documentation describes recipient acceptance and options for associated plans and domains. Confirm each service in your own project. Its collection export guide describes CSV export; test the selected fields and the receiving system.
WordPress.com's content export guide treats written content and media retrieval separately: XML contains media references, while the actual files require separate retrieval or copying during import. Check content, media, design and application deliverables individually. Maintain authorized access to the source until media copying has been verified. These examples describe the documented scope of specific products; confirm the actual platform and plan for your project.
3. Restore an isolated sample to prove the materials work
Technical staff should prepare a separate database, file location and test domain, limit access to the acceptance team, and inspect test settings for email, notifications and external integrations. Check connection targets before and after restoration so tests stay within the approved environment. See the staging and production checklist.
- Record application, theme, dependency and database versions and backup times; deploy and restore using the supplied instructions.
- Check a product, a news item, an attachment and their English counterparts, including images, parameters and original publication dates.
- Use the incoming team's account to edit a sample, read the saved value back, and inspect the public test page.
- Submit an enquiry explicitly labelled as a test. Verify its record, test notification and recipient separately.
- Record restoration duration, missing materials and resolutions. Use the actual result to assess readiness for production.
For full-site acceptance, reconcile totals by site, category and language and agree on sampling for ordinary historical records. Expand checks when a sample reveals a repeated problem. Mark missing secrets, dependencies or attachments as outstanding materials, while continuing independent checks on the remaining assets.
4. Map fields and content before changing CMS
Inventory pages using the old admin system, sitemap and business materials. Mark each for retention, revision, consolidation or archiving. Record the old content ID, URL and language, target model and category, new ID and target URL. Product owners confirm model numbers, values, units and applicability; marketing confirms text and approved assets; language owners confirm translations and terminology.
Trial a product, a news item with an attachment and a Chinese-English page pair. Parameters previously stored in prose can become configured business fields in the new model. Project staff implement the conversion rules. Check titles, text, parameters, images, files, dates and publication status before processing a larger batch. Preserve language relationships and document revisions for the same product. See the multilingual update checklist and download management guide.
CatchCMS provides content models and dynamic fields, multilingual content and theme management. Missing translations can fall back to the default language, so inspect the text visitors actually see on English pages. Old-system export, batch conversion and migration scripts depend on source data and project scope. Preserve original values, read back saved records and inspect public pages for each batch.
Agree on fields, languages and files before exporting
Ask the provider for a readable sample and a field specification before scheduling a full export. The delivery sheet should record source site and record ID, stable product ID, model and category, language, field name and type, conversion rule, attachment ID, target record and result. A database backup supports restoring the same application. Moving to another CMS requires the receiving team to transform data for its target models. Include a sample export and import in the procurement trial.
- Identifiers and relationships: Keep the source site, record ID and business product ID, plus mappings for categories, related products and attachments. The new system can generate its own IDs; retain the correspondence between both systems. Chinese and English versions should belong to the same product. Check identical model names on different sites separately.
- Fields and empty values: Specify formats for text, numbers, units, dates and multiple selections. For fields that allow these states, define the meaning of an absent value,
null, an empty string, numeric0and Booleanfalseseparately. Record whether a translated field actually exists and preserve its stored value. If an English page displays fallback text from the base language, record a translation gap for that field. Apply an agreed destination rule to each state. - Dates and status: Preserve original publication and modification times and publishing status. Retain the original time zone or UTC offset and a normalized UTC value for comparison. Record the import date separately. Map drafts, archived records and public content individually so that test or historical material retains its intended visibility.
- Images and PDFs: Receive the actual files, names, languages, revisions, checksums and page references. After copying, replace old references with files in the target storage. Check embedded images, relative paths and download links. Maintain authorized access to the source files until file acceptance is complete.
CatchCMS provides content models, custom fields, multilingual content and MCP queries and updates governed by admin account permissions. Cross-system export packages, format conversion, attachment copying and bulk imports require project implementation. Ask the delivery team to demonstrate the agreed sample and include formats, costs, delivery deadlines and maintenance ownership in the scope.
Rehearse an import with source-site access blocked
Fictional example: prepare 20 product records, Chinese base content for each, 19 complete English translations, one Chinese PDF and one English PDF. The twentieth product is missing an English parameter translation. The source may expose 40 accessible language pages. The reconciliation sheet should still distinguish 20 products, 19 complete English translations and one translation gap. Reuse the two PDFs according to their actual references, counting files and page references separately. These figures illustrate reconciliation only.
- Start with a small group: Import samples with complete translations, missing translations and attachments into an isolated environment. Read saved values back and check model numbers, parameters, units, empty-value states, original publication dates, categories and language relationships. Use the everyday editor account to update one sample and verify that the receiving team can maintain it.
- Include failure cases: Use dedicated test data to exercise duplicate source IDs, unknown categories, relationships across site boundaries and missing attachments. Log the reason, source record and owner for each exception. Verify that the importer rejects or isolates invalid records and reuses the existing target record when the same source-site and source-ID pair is processed again. The project developers should validate the tool's handling of these cases.
- Check independent operation: Temporarily block the source domain and disable caching in a controlled test browser, then reload and open target product pages, images and PDFs while inspecting network requests in developer tools. Files copied to the new storage should remain readable. List intentionally retained external services as dependencies. Preserve source access under the agreed arrangements and record the results of simulated source unavailability.
- Reconcile the full batch before sign-off: Compare source records, successful imports, explicit exclusions, pending failures and the file manifest by site, category, language and status. Give every source record an outcome. Resolve the English gap and retest the 40 expected language entries, then check visibility, internal links, old URL destinations and mobile reading. Record task duration, conversion costs and remaining dependencies for joint business and technical approval.
Copy these acceptance columns: source site and ID, target ID and URL, language and field results, attachment checksum and new location, source-blocking result, editing result, exception and owner, retest date. Once content is readable and editable in the new system and files can be retrieved independently, proceed under the approved production migration plan.
5. Assign destinations to old links and search entry points
Include bookmarks, brochure QR codes, email links, downloads and search entry points in the URL map. Retain existing URLs when their purpose and structure remain suitable. For a permanent address change with a corresponding page, configure a direct permanent server redirect to that page. Consolidated content should answer the original needs. Products with ongoing service demand can retain clearly labelled archive pages. Technical staff should assess 404 or 410 for permanently removed content without a relevant replacement.
Google's site move guide covers URL mapping, redirects and target-site checks. Test the first HTTP response, destination, final status and content. Update internal links, sitemaps, canonical URLs and language associations. Server and application redirect rules are project implementation work. Check titles, descriptions, text and files on pages that retain their URLs as well.
Give Chinese and English URLs separate rows. Language switching should reach the corresponding version of the same content. Review test access restrictions, noindex and robots rules against the intended production scope. Record page accessibility separately from these checks. Publication, search discovery, indexing, rankings and actual AI citations each require their own evidence.
6. Agree on final data collection and rollback before switching
Record the content freeze, final extraction time, switch owner and incident contacts. Put products, files and enquiries added after the freeze into an incremental register with a named reconciliation owner. If the old site continues to receive enquiries, define how to reconcile its final record with the first records on the new site.
Save recoverable data, files and configuration. Document rollback triggers, restoration steps and retention of the old environment. Preserve new enquiries and content created after the switch separately and plan reconciliation before rollback. Test DNS rollback, theme switching and database restoration according to their individual roles. Rehearse the operations the project will actually use.
After the company confirms takeover, update passwords, keys, collaborator permissions and recovery contacts according to responsibility. Retest services that use those credentials. Agree on closure of old services and retention or disposal of materials, and record completion.
7. Fictional example: proceed while two materials are outstanding
Fictional project: an equipment business is transferring 30 products and a bilingual website to a new supplier. The first delivery includes code and a database, with manual source files and email settings still outstanding. The count organizes testing; restoration duration and performance require separate measurements.
The owner marks manuals and email as separate outstanding items. The incoming team restores the database in isolation and checks three products, two news items, each language and editing access. Download and notification acceptance remain open. Once the files arrive, the team verifies revisions and paths. It tests email using an approved test configuration, then confirms production recipients.
A trial migration row could read: “PX-240 product | old Chinese and English pages | two target URLs | parameters and units match | R3 manual outstanding | owner and deadline.” The model, revision and record are illustrative. The company and suppliers agree on release conditions according to business needs. A project that relies on enquiries should verify both recording and notification before the switch.
8. Complete public-page acceptance and operational handover together
- Assets: the company can access agreed accounts, and the incoming team can retrieve matching code, data and files and restore them.
- Content: totals reconcile by category, language and disposition; product parameters, attachments and original publication dates match.
- Entry points: key old URLs, downloads and QR codes reach the agreed destinations. New-page status, title, description, canonical, language links and applicable structured data are correct.
- Mobile: navigate from a list to a product, read text and specifications, open an attachment and reach the enquiry entry. Check text, tables and buttons.
- Enquiries: verify a labelled test submission in the admin records, agreed notifications and follow-up owner; handle test data under project rules.
- Maintenance: the actual editor completes an update, and technical staff verify restoration, runtime tasks, permission handover and renewal arrangements.
For each item, record the target, actual URL or controlled evidence location, check time, recipient, result, issue and retest time. CatchCMS MCP operations inherit admin account permissions and can query or update content within existing models. Project staff arrange migration conversion, full-site backup and restoration, account takeover and hosting changes. List payments, orders, subscriptions, communities and external business systems separately, with demonstrations and written confirmation of each data and handover workflow.
9. Common handover questions
What else is required after receiving source code?
Check the database, uploads, theme, dependencies, environment configuration, licenses and operating instructions. Ask the incoming team to restore an independent copy and record missing items as evidence of takeover readiness.
Can a new supplier retain the domain and existing URLs?
Plan the new site around the existing domain and suitable paths. Actual takeover depends on domain management, platform capabilities and new-site routing. Map changed addresses individually and test old entry points.
How should historical enquiries reach the new team?
Export, archive or import them separately within the agreed scope, preserving fields, sources, timestamps and follow-up responsibility. Sales verifies access and incremental records. Transfer backups through a controlled channel.
Prepare the asset register and representative product materials before requesting a project review. Describe the current platform, languages, site count, retrievable materials and incoming team so CatchCMS migration and maintenance responsibilities can be confirmed. See current plans for source-code licensing and update entitlements.