So Outside Technology Security CMS
AnQiCMS
Online Demonstration

Several thousand articles need to be moved, should it be imported using a compressed package or a table?

📅 2026-11-01 👁️ 0

Several thousand articles need to be moved, the choice of importing as a compressed package or as a table depends on the material form rather than the number of articles themselves. AnQiCMS's batch import document supports two entry methods of ZIP compressed package and Excel table at the same time: for text with images, attachments, and complex layouts, it is more convenient to bring the materials and documents together in a ZIP compressed package.The field is organized, mainly by title, category, and tags. It is faster to fill it in bulk by row in an Excel table. What truly determines the amount of rework is whether the content model is aligned before import, whether there is title duplication, and whether the batch of failures can be rerun without producing duplicate content.

What content is contained in the two import methods

ZIP compressed package import packages related documents together, where the main text and the accompanying files are in the same unit, suitable for retaining the original formatting when exporting from the old system. Table import is structured field bulk fill: column corresponds to field, row corresponds to article, and the main text is written as one of the columns. Tables are suitable for having organized data (title, publication time, category name, tags, abstract) first, and then supplementing the main text; it is not suitable to move scattered images together.

The criteria can be put into a table:

Judgment item Compressed package import (ZIP) Table import (Excel)
Main text with attachments and images Suitable, materials are taken away with the package Not suitable, the attachment should be sent separately
Fields are neat, fill in bulk Each package must be checked manually Suitable, column names match fields
Complexity of layout Maintain the original structure 主要以 plain text
Duplicate check and rerun Check the title once and send a package again Mark as existing directly in the table
Labor cost distribution High cost of preliminary package organization High cost of preliminary column mapping

Judge the material form before moving

Export a sample of old site data with dozens of articles and check three things: whether there are local attachments referenced in the text; whether the categories, tags, and keywords are listed in the old data; and whether the additional properties of each article are consistent. If the fields of the old site are diverse and some properties cannot be imported into the table, they should be added as custom fields in the content model of the target site instead of being forcibly inserted into the text. The content model determines which custom fields can be filled in the article, and the fields must be created first so that they can be mapped during import; if the order is reversed, the imported documents will need to be modified again.

The three most easily overlooked places when aligning fields.

The first is the matching of categories and tags, when importing, categories are found by name, and if the name does not match, it will fall into the default category. The second is the summary and keywords columns, many old systems do not have an independent summary field, and it needs to be generated or supplemented on the new site, otherwise the display on the list page will be very ugly. The third is the publication status and time, releasing thousands of articles at once will form an abnormal concentration, and can be divided into drafts, to be published, and then formal in batches according to the status, to pull the rhythm.

How to use the import interface to check for repeated runs

Batch import is bound to fail halfway, make sure the target site does not already have a document with the same title before rerunning. AnQiCMS provides a document content import interface /api/import/archive, which supports querying whether a document already exists by title, use it to run a title list first, exclude the existing ones before resubmitting, it is much cleaner than rerunning the entire batch. Coordinate with the recycle bin mechanism of the background, deleting a wrong document is moved to the recycle bin instead of physical deletion, clear it after confirming that there are no errors, the rollback space is still there.

Before starting officially, make a backup first. Backup and restore cover data and static files, if import fails or field mapping is incorrect, you can revert to the state before import, which is more secure than manually deleting thousands of articles.

Common questions

Do you have to import thousands of articles at once?No need. Cut them into batches by category, check the list page and content page after each batch is imported, and the problem will only affect one batch.

Is there a length limit for the text in table import?Based on the actual field capacity, it is recommended to use a compressed package for importing long text to avoid truncation of table cells.

Do you need to resubmit for indexing after import?Need. After moving, URL changes will cause fluctuations in inclusion, the site map needs to be regenerated and submitted, and the search engine side can rebuild the index according to the new address.

What should I do if the old address is still being referenced?Keep the old address as a valid entry point, use 301 redirect to transfer the weight to the new location, do not leave an empty page directly.

Related articles

When starting a site with a container image, should the default port and background address be changed together?

When starting a station using a container image, whether to change the default port and backend address at the same time depends on where the traffic comes from: After the site is behind the reverse proxy, the container listening on port 8001 only needs to match in the mapping, the default port does not need to be changed; what needs to be received is the exposed surface of the backend address. Before going online, enable the built-in protections such as JWT authentication, sensitive word filtering, captcha, and rate limiting first, and then verify it once from the external network.

2026-11-01

How to plan the column structure and classification for a single backend to manage multiple sites without conflict

When managing multiple sites with a single backend, the place where column structure and classification are most likely to interfere with each other is when reusable definitions and isolated data are mixed together. This article explains by separating the shared layer and the isolation layer: the definition of the content model can be reused across multiple sites, the classification tree, column aliases, and visibility range should be planned independently for each site, batch operations at the whole-site level are disabled by default and explicitly enabled per site, and a landing sequence and a corresponding table are provided.

2026-11-01

Can deleted articles be retrieved, and how are drafts, pending publication, and recycling stations divided?

Deleted articles can usually be retrieved: In the AnQiCMS backend, deleting formal documents is not a physical deletion, but moving them to the recycle bin, from which they can be restored. Each of the four document statuses has its own boundaries - formal documents are visible to the public, drafts are only in the background and preview links contain the preview tag, pending publication waits for the set time to take effect, and the recycle bin accommodates deleted content. This article explains the appropriate operations for each and the safe sequence for bulk cleaning.

2026-11-01

How to import articles from the old station table once, if the fields do not match

The order of handling the mismatch of fields when importing the exported table of the old station to the new system is: first select the channel and then discuss mapping, the three columns of fixed title, alias, and category must be mapped, then determine the default value strategy for custom fields, and finally use title search to check if it already exists to avoid repeated imports and sample check the import results

2026-11-01

When the sitemap exceeds the limit, it can only be split into files, and before splitting, you need to clear which type of address.

The site map exceeds the single file limit and must be split into multiple files using an index file for aggregation, but before splitting, it is necessary to clean up three types of addresses: pages with error status codes, redirect addresses, and pages with屏蔽 marks that are written into the map. The cleaning order is wrong, and the each file after splitting is still wasting crawling quota, the collection efficiency will not improve.

2026-11-01

The active push protocol is only supported by a few search engines, does another one count as a push?

The active push protocol informs search engines about which URLs have changed, requests priority crawling, but only a few participate. The one that does not participate will not change the crawling and inclusion judgment just because you have sent a notification. You need to separate discovery and inclusion, follow the engine's分流 actions, let the sitemap be responsible for the bottom line, push for incremental, and then use each result to check whether it has really entered the index after the push.

2026-11-01

The page shows that it has been crawled but not indexed, is it a broken link or a quality demotion?

Being crawled means the crawling link is working, and not being indexed is often the result of quality judgment: the system may reduce the number of indexed pages when it is worried about the quality of the entire site. The handling is in order, first分流batch pages by subject, then decide to rewrite, merge, or withdraw, while cleaning up the low-quality content collected, converging the repeated carrying pages and anchor text in the keyword library, and finally resubmitting and keeping a record for observation.

2026-11-01

On the day of replacing the host, the domain resolution needs to be moved, and how long in advance should the cache time be reduced to be safe.

The key to migrating domain name resolution is not on the day of the switch, but in advance, by lowering the caching time of the resolution to make both new and old sides converge to the same record as soon as possible. Generally, adjust the cache value one to two days in advance, let the old environment run for a few days after the switch, and hand over the redirection and site map to the new address. Email records are easiest to miss, the effective window is uncertain, and after the switch, you need to check the inclusion status with each search engine separately.

2026-11-01