Advanced Custom Fields For WP All Import 3.3.8-beta-1.4

Advanced Custom Fields For WP All Import Overview

Advanced Custom Fields For WP All Import 3.3.8-beta-1.4 connects ACF field groups to the drag-and-drop import workflow in WP All Import. It is designed for projects that receive structured content from CSV, XML, Excel, Google Sheets, or another source supported by the main importer. Instead of writing values into generic meta keys manually, administrators can map incoming data to the ACF fields already attached to a post type.

This matters because Advanced Custom Fields stores more than a visible value. ACF also uses field definitions and reference information to understand how data should be formatted. Importing through the dedicated addon helps the destination records behave like content entered through the ACF interface, including supported images, galleries, relationship data, and repeater structures.

The addon is not a standalone importer. It requires a compatible WP All Import installation and Advanced Custom Fields. The destination ACF field groups must already exist and be assigned to the content type being imported. It imports values into fields; it does not create the ACF field definitions themselves.

What The ACF Import Addon Does

• Recognises ACF Field Groups: Shows relevant groups and fields for the selected destination post type.
• Maps Source Data Visually: Drag elements from the import file into the matching ACF fields.
• Supports Multiple File Formats: Work with CSV, XML, Excel, Google Sheets, and other inputs handled by WP All Import.
• Handles Structured Fields: Import supported images, galleries, relationships, repeaters, and other ACF data.
• Provides Repeater Modes: Choose a structure suited to fixed columns, sibling XML elements, or delimited CSV values.
• Allows Data Transformation: Use built-in functions or controlled inline PHP when source values need conversion.
• Updates Existing Records: Use a unique identifier to match imported items during later runs.
• Supports Scheduled Workflows: Run recurring imports through supported WP All Import scheduling options.

Prepare ACF Before Starting The Import

Field design comes before mapping. In Advanced Custom Fields, create the field group, add the required fields, set each name and return format, and assign the group to the correct post type through location rules. Publish the field group and create a sample destination record manually.

The sample record provides a reference for expected behaviour. If an image field returns an attachment ID, a relationship field returns post objects, or a date field expects a particular stored format, the import should reproduce a value that ACF can interpret the same way. Testing one manual record before importing thousands makes troubleshooting much easier.

For the primary premium field framework, see Advanced Custom Fields ACF Pro V6.8.4. Pro field types such as Repeater, Flexible Content, Gallery, and Clone require an appropriate ACF Pro installation in addition to the importer addon.

Start A New ACF Import

Open All Import, create a new import, and provide the source file or feed. WP All Import analyses the structure and asks which WordPress content type should receive the records. Choose the post, page, product, or custom post type whose ACF field group was prepared.

Review the source file before mapping. Confirm that the importer selected the correct record node, headings or element names are consistent, character encoding is correct, and one preview item contains enough data to test. An XML file may have several nested nodes, while a CSV file may hide structure inside delimiters.

Use import filters when only part of the source should be processed. Filtering early is safer than importing everything and deleting unwanted records later. Preserve a copy of the unmodified source file so every transformation can be traced.

Map Incoming Elements To ACF Fields

In the drag-and-drop screen, expand the Advanced Custom Fields Add-On section and enable the relevant field group. The visible fields can then receive source elements. A text column might map directly to an ACF text field, while a date, relationship, image, or repeater requires more detailed configuration.

Map fields by meaning, not merely by similar names. A source column labelled Status may represent an internal workflow value that does not match the choices configured in ACF. A price value may include a currency symbol while the destination number field expects only digits and a decimal separator. Document every transformation.

Use the preview feature after mapping. The preview simulates how a source record will appear and can reveal missing values, misplaced elements, or incorrect formatting before the database is changed. Check several source records when the data is inconsistent.

Import Text, Numbers, Choices, And Dates

Basic text and textarea fields are usually direct, but encoding and whitespace still matter. Normalise unexpected line breaks only when they are not meaningful, preserve non-English characters, and decide whether the source contains trusted HTML or plain text.

Number and range fields should receive a consistent decimal format without decorative currency or unit text unless the field was intentionally designed to store it. Selection fields normally expect the saved value configured in ACF rather than the human-readable label. A Yes or No field may require a specific truthy value.

WP All Import documentation states that date values can use formats understood by PHP’s date parsing, with a simple ISO-style format such as YYYY-MM-DD often easier to verify. Ambiguous values such as 03/04/2026 can mean different dates in different regions. Convert them explicitly before import.

Import Images And Gallery Fields

Image fields can use source URLs, file names, or other media references according to the main import configuration. Determine whether WP All Import should download a new attachment, find an existing Media Library item, or use a supplied attachment identifier. Test duplicate handling so recurring imports do not create another copy of the same image every time.

An ACF Gallery field contains multiple attachments in a defined order. The source must clearly separate the image values, and the mapping should preserve that order. Check file availability, MIME type, dimensions, titles, captions, and alternative text where the workflow provides them.

Remote image imports depend on the source server. Timeouts, blocked hotlinks, redirects, expired URLs, and large files can cause partial results. Run a small batch first, check the Media Library, and review logs before launching the complete import.

Import ACF Repeater Fields

Repeaters are one of the strongest reasons to use the dedicated addon. A repeater contains an unknown or predefined number of rows, with one or more subfields in each row. The import must preserve the row boundaries so values remain associated correctly.

Official documentation describes three approaches:

• Fixed Repeater Mode: Use separate source columns or elements when the number of rows is predetermined. This is suitable for a small fixed set such as three feature blocks.
• Variable Repeater Mode For XML: Read repeating sibling elements when each source record can contain a different number of child nodes.
• Variable Repeater Mode For CSV: Split multiple values stored in columns using a chosen delimiter, with consistent item counts across related subfields.

A delimiter must not also appear inside the data unless it is escaped or transformed. If names are separated by a vertical bar and one legitimate value contains that character, rows can shift. For several repeater subfields, every list needs the same logical order and number of items.

Work With Flexible Content And Other Layout Fields

Flexible Content can hold different layouts, each with its own subfields. A successful import therefore needs both the layout identity and the values belonging to that layout. Map source data to the expected ACF layout names and test every variation, including records that contain several layouts.

Group and Clone fields can also introduce nested paths. Review how the installed addon version presents them and compare the imported database result with a manually created record. Historical beta builds may not support every field introduced in newer ACF releases.

Do not flatten complex content merely to make the importer accept it if the front-end template expects a structured value. Adjust the source, mapping, or destination field model so the saved data remains coherent.

Map Relationship, Post Object, User, And Taxonomy Data

Relational fields must identify the correct WordPress object. A human-readable title is convenient but may not be unique. Use a stable identifier such as a known post ID, slug, email, username, or external key according to the field and import configuration.

Related records may need to exist before they can be selected. Plan the import order: create authors, locations, categories, or parent records first, then import items that reference them. For feeds containing both sides of a relationship, use external identifiers and a staged process rather than relying on database IDs from another site.

Multiple-value relationships need a clear delimiter or repeated XML node. Confirm whether ACF returns IDs, objects, or another format after import. The storage may be correct even when a custom template expects a different return type.

Use A Unique Identifier For Safe Updates

WP All Import tracks records with a unique identifier. This is the key to rerunning an import without creating duplicates. Choose a stable source value such as a supplier ID, catalogue number, external record key, or other identifier that will not change when the title or URL changes.

Do not use a temporary row number unless the source guarantees its permanence. If the unique key changes, the importer may create a new WordPress item instead of updating the existing one. If two source records share a key, one can overwrite or collide with the other.

Before the second run, define which ACF fields may be updated, which must be preserved, and how missing source records should be handled. A blank field may mean delete the existing value, leave it unchanged, or report an error; the correct choice depends on the business process.

Transform Source Data With Functions

Incoming values do not always match their destination. WP All Import can apply supported functions or controlled PHP to clean dates, combine fields, split lists, replace labels, create URLs, or convert units during mapping. This is powerful but should remain simple and documented.

Inline PHP executes during an import and can affect every record. Use trusted code only, escape unexpected input, and avoid network calls inside a large loop unless they are necessary and resilient. A slow function multiplied by thousands of items can exceed server limits.

When transformation rules become complex, process the source into a clean intermediate file or use a maintained helper plugin. This keeps the import template readable and makes validation easier.

Preview, Test, And Verify

1. Back Up The Database: Create a tested restore point before changing production content.
2. Run A Small Sample: Import records that cover simple values, images, repeaters, relationships, and empty fields.
3. Use The Mapping Preview: Compare source elements with the simulated destination.
4. Inspect The WordPress Editor: Open imported records and confirm that ACF fields display correct values.
5. Inspect The Front End: Test templates that call ACF functions and compare them with a manual record.
6. Rerun The Sample: Confirm that the unique identifier updates records rather than duplicating them.
7. Review Media: Check attachments, duplicates, captions, alternative text, and gallery order.
8. Read Import Logs: Investigate skipped, failed, or transformed values before the full run.
9. Scale Gradually: Increase the batch size only after memory, timeouts, and data quality are stable.

Scheduled Imports And Ongoing Feeds

WP All Import can support scheduled workflows through its scheduling service or server cron configuration, depending on the installed product and plan. A schedule is useful for supplier feeds, listings, directories, and other regularly refreshed datasets.

Recurring imports require monitoring. Notify an administrator when the source cannot be downloaded, the record count changes unexpectedly, required columns disappear, or the run produces errors. A schedule that silently imports empty or malformed data can damage many ACF values.

Keep a record of the source owner, expected frequency, identifier, field mappings, last successful run, and rollback method. Rotate credentials securely if the feed is protected.

Bulk Editing Through Export And Reimport

A related WP All Import workflow exports records and ACF data, edits the file in a spreadsheet, and imports it back with the matching identifier. This can support carefully controlled bulk updates. The ACF Import Addon handles the import side, while WP All Export and its appropriate ACF integration handle extraction.

Spreadsheet applications can alter dates, leading zeros, long identifiers, and character encoding. Import a copy into staging first and compare every field type. Never use a title as the only match when several records can share it.

After an import, the Admin Columns Pro ACF AddOn V2.6.7 can provide table views for auditing supported ACF values. It serves a different role: WP All Import moves data into fields, while Admin Columns helps inspect and manage it in WordPress.

Beta Version And Compatibility Notes

The supplied version string is 3.3.8-beta-1.4. A beta-labelled build is a pre-release and may contain unfinished changes or compatibility issues. It should not be described as the latest stable version. Later packages exist, and current WP All Import documentation may reflect capabilities beyond this historical build.

Match the addon with documented versions of WP All Import and ACF. A mismatch can cause missing field groups, failed repeaters, unsupported layouts, PHP errors, or values that save without the required ACF reference. Use staging and inspect the exact archive before committing to a migration.

The addon imports ACF values but does not import standalone ACF field definitions. To move field groups themselves, use the export and import tools provided by Advanced Custom Fields, then run the content import after the structure exists.

Performance And Server Planning

Large imports can consume memory, CPU, disk space, and network bandwidth. Image downloads and complex repeaters are more demanding than simple text fields. Use batch processing, avoid unnecessary transformations, and coordinate long jobs with the hosting provider.

Do not run a heavy feed during peak traffic without measuring its impact. Monitor PHP errors, database size, Media Library growth, cron queues, and available storage. Remove failed test data only after confirming the exact records to avoid deleting unrelated user content.

Installation And Requirements

Create a backup and staging copy. Install Advanced Custom Fields and a compatible WP All Import edition, then upload and activate the ACF Import Addon ZIP. Prepare the destination field groups, create a new import, select the correct post type, and map a small sample.

This addon is specialised for ACF data. For a WooCommerce-focused product CSV workflow, the Product Import Export Plugin For WooCommerce V3.8.3 is a separate option with a different mapping model. Choose according to the source data and destination fields rather than using overlapping importers on the same feed.

GPL Download And Support Expectations

The GPL licence permits use, study, modification, and redistribution of covered code under its terms. A GPL package can be useful for development, staging, testing, and migration planning. It does not automatically include the original developer’s account, automatic scheduling service, licence key, updates, or direct premium support.

Confirm which WP All Import services and addons the workflow requires. Obtain a current official package when reliable updates or vendor support are essential. Browse the WordPress Plugins Collection for more downloadable tools.

Frequently Asked Questions

Does The Addon Create ACF Field Groups?

No. The field groups and fields must already exist and be assigned to the selected destination content type. The addon imports values into that structure.

Which File Formats Can Be Used?

WP All Import documentation describes CSV, XML, Excel, Google Sheets, and other supported sources. The main importer parses the file, while the ACF addon maps its elements to fields.

Can It Import ACF Repeater Data?

Yes. Official documentation describes fixed repeater mode, variable XML mode, and variable CSV mode. The source structure must preserve row boundaries and subfield alignment.

Can It Import Images And Galleries?

The current product documentation includes images and galleries among supported ACF data. Test file download, matching, attachment creation, duplicates, order, and metadata with the supplied beta version.

Can I Import ACF Fields Without Posts?

No. ACF values belong to posts, users, terms, options, or another object. For this workflow, import the content type that holds the fields. Use ACF’s own tools to move field definitions.

How Are Existing Records Updated?

WP All Import uses a unique identifier to match source items with imported WordPress records. Choose a stable key and configure which fields are updated or preserved on later runs.

Is 3.3.8-Beta-1.4 A Stable Release?

The version label explicitly includes beta, so treat it as pre-release software. Test it on staging and use a documented stable version for critical production migrations when possible.

Import Structured ACF Data With A Controlled Process

Advanced Custom Fields For WP All Import 3.3.8-beta-1.4 provides a purpose-built mapping layer for moving external data into established ACF structures. It can handle simple fields, media, galleries, repeaters, relationships, and transformed values while WP All Import manages record creation, matching, scheduling, and reruns.

The quality of the result depends on preparation. Define the field groups first, clean the source, select a stable identifier, preview mappings, run a representative sample, and verify both WordPress and front-end output. With that process—and with appropriate caution for a beta build—the addon can turn a complex manual migration into a repeatable import workflow.