❌

Normal view

There are new articles available, click to refresh the page.
Before yesterdayMain stream

TUC’s Paul Nowak and John Amaechi perfectly dismantle anti-immigration rhetoric on Question Time

The general secretary of the Trades Union Congress, Paul Nowak, and psychologist John Amaechi delivered powerful rebuttals of anti-immigration narratives on Question Time last night. 

In a discussion about whether Labour’s new immigration policy is ‘yet another U-turn’, Nowak highlighted the importance of treating migrants with dignity. 

Nowak welcomed the home secretary Shabana Mahmood’s decision to scrap plans to make foreign care workers who are already in the UK wait 15 years to qualify for settlement.

Under the revised policy, care workers who earn at least £25,000 a year and arrived in the UK before May 2025 will continue to qualify for settlement after five years.

Nowak said: “It was a welcome step back, 200,000 people responded to the government’s consultation, I think it’s the second biggest consultation response in history after equal marriage.”

Turning to the debate around immigration, the TUC boss said: “I’ll get to the policy issues in a moment but I’ll tell you this about migration. Quite often it turns into a political ping pong match, and what we’re actually talking about is people.”

Speaking about Liverpool, where Question Time was held yesterday, he added: “This is a city that was built on migration. Both my grandads came to this country during the Second World War, one with the Polish RAF, one from Hong Kong.”

Nowak said both of his grandfathers had met Liverpool Irish women and they stayed and settled in the UK.

“I think it would have been untenable for them to be in a situation when they were in Liverpool and told, well it doesn’t matter, you could be here 15 years, 20 years and we’ll decide when you can stay,” he said.

Nowak questioned: “How do you plan your life, buy a house, put the kids in school, decide what you’re going to do about work?”.

He said Mahmood was “right” to “take a step back” and said it was “untenable” for the government to change the rules for migrants already living in the UK. 

Nowak said he’d like to see the government extend the policy for prison and transport workers and those working in research and development.

Host Fiona Bruce asked Nowak who should not be allowed to enter the country. 

Nowak said “I think people should be able to apply to come to this country and then the government has got to set the guidelines for who can stay and work.”

Amaechi, a former basketball player and psychologist, also challenged anti-migrant rhetoric during the discussion.

He said: “Can I suggest that when we have this conversation sometimes no one I think is arguing there should be just an open door for anybody, but at the same time you listen to this conversation and it’s like the policy was made for the apocryphal grotesque stereotype of what an immigrant is.”

To a round of applause, Amaechi added: “Yes there are fraudsters in this world and guess what they aren’t all just black and brown people coming to this country.”

Speaking about having worked in the NHS for 10 years, Amaechi said that many people doing the jobs “we would find the most undesirable did it with passion and we stood by as they protected our loved ones in their most vulnerable moments”.

He added: “And I’m not saying that that is the picture of all migrants too, but surely a more charitable picture than the fraudsters and the connivers and the criminals, as if we do not have them here in aplenty”.

Amaechi also challenged government policies that require migrants to earn a certain amount to be able to settle.

He said: “Any time that you look at a policy that starts to tell people coming here that they’re only valuable if you make more than this amount of money, then all of us here should look out.”

A young woman in the audience said Amaechi had “hit the nail on the head” with his comments, and asked: “When do we stop scapegoating immigrants in general?”.

She added: “When is there a reflection on the government to put out to people that ‘hang on, immigration isn’t actually this massive issue that it’s made out to be, there’s a lot of fearmongering going on.”

The audience member said that as a student her issue isn’t “someone who is coming here as a migrant to work hard, my issue is getting graduate roles”.

She said she doesn’t view an immigrant “as the reason why I can’t get a graduate job” or “the reason why mincemeat costs £7 and petrol prices are constantly increasing”.

She finished by asking: “So is the government ever going to do something to sort of stop that narrative and tell people ‘actually immigrants are regular people like you and me’?”.

Olivia Barber is a reporter at Left Foot Forward

The post TUC’s Paul Nowak and John Amaechi perfectly dismantle anti-immigration rhetoric on Question Time appeared first on Left Foot Forward: Leading the UK's progressive debate.

What are the Right-Wing press and think tanks up to this week?

The big themes of the week

1. Immigration and asylum: keeping the pressure on

The asylum debate remains a major focus, with coverage of proposed accommodation for asylum seekers near Piddington and Bicester, residents’ concerns and calls for tougher action. The Daily Express framed local objections around whether women were being listened to, while the wider debate has included proposals from Reform UK to suspend the asylum system for five years.

2. Tax, spending and the case for a smaller state

With the Chancellor’s Budget approaching on 28 October, arguments about taxation, welfare and business costs are intensifying. The Sun has attacked the prospect of further tax rises and argued for welfare cuts, while business groups have called for changes to employer National Insurance to encourage recruitment.

3. Andy Burnham under sustained political attack

The Sun‘s 15 October editorial attacked Burnham over sluggish economic growth, welfare reform, his dealings with Manchester City executives and the prospect of tourist taxes. The Daily Mail has also pursued questions about his relationship with the club’s ownership. They are so ratteld by Labour’s improvement in the polls they’re doing all they can to smear him.

4. Culture-war issues remain part of the agenda

On 16 October, the Daily Mail led with criticism of government proposals to improve pupils’ speaking skills.

Rather than welcoming the improvement, promoted by Lucy Powell, which aims to reform the national curriculum so that verbal fluency and communication skills are embedded alongside traditional academic subjects, the Mail is having a meltdown.

5. The future of the Telegraph and media ownership

On 16 October, Reuters reported that the UK government had cleared Axel Springer’s planned acquisition of Telegraph Media Group from a further competition investigation. This is a significant development for the ownership of one of Britain’s most influential right-leaning newspaper groups.

Why it matters: newspaper ownership affects the long-term institutional landscape in which political arguments are produced. The immediate question is what the change means for editorial independence, newsroom priorities and the paper’s future direction.

The blogs, campaign groups and think tanks behind the headlines

The newspaper stories are only one part of the picture. Campaign organisations and policy institutes help develop the arguments, statistics and proposals that can subsequently enter political debate and media coverage.

TaxPayers’ Alliance — welfare and the public finances

The organisation’s recent output includes a report arguing that Britain’s fiscal problems are worse than those of the 1970s, a critique of tax rises and constituency-level analysis of benefit spending. Its 12 October material claimed benefit costs had risen faster than median pay in 502 of 526 constituencies across England and Wales.

The argument to watch: welfare spending is becoming unaffordable and tax increases risk undermining growth.

The questions to ask: which benefits are included, how the figures are calculated, whether higher spending reflects inflation or increased need, and how the proposed alternatives would affect household incomes.

Read: TaxPayers’ Alliance blog  · Fiscal policy report 

Migration Watch UK — immigration and border control

Campaign and research organisation

Migration Watch’s recent commentary has returned to the question of whether the post-Brexit immigration system has delivered meaningful control over migration. Its September analysis, Ten Years Since Brexit, We Still Have Not Taken Back Control, questions the record on immigration numbers.

The argument to watch: governments have failed to deliver the immigration controls promised after Brexit.

The questions to ask: are the figures about net migration, work visas, asylum applications or settlement? These measure different things, and a claim about one should not automatically be treated as a claim about all the others.

Read: Migration Watch UK blogs 

Policy Exchange — the policy development pipeline

Policy institute · Public services and the economy

Policy Exchange’s recent publications include The Rural Penalty, examining how NHS funding formulas affect rural and coastal communities, and Legislating for Candour?, published on 14 October. Its broader programme addresses productivity, housing, healthcare and regulatory reform.

The argument to watch: how institutional reform, changes to public-service delivery and economic restructuring might improve outcomes.

The questions to ask: what evidence supports each proposed reform, who gains or loses from it, and whether the analysis adequately accounts for regional inequalities.

This newsletter is produced with the assistance AI

The post What are the Right-Wing press and think tanks up to this week? appeared first on Left Foot Forward: Leading the UK's progressive debate.

Right-Wing Media Watch: The right-wing press has already written Sánchez’s political obituary

Spain is heading for a snap general election on November 29, and the right-wing press has wasted no time celebrating what it clearly projects to be the beginning of the end for Pedro Sánchez’s Socialist government.

Sánchez announced the early election after his minority government suffered a parliamentary defeat over emergency measures designed to tackle Spain’s housing crisis, following intense public outrage after a high-profile eviction of an 87-year-old woman in Madrid. The proposals, which included stronger protections against evictions and measures aimed at increasing access to affordable housing, were voted down after the conservative People’s Party (PP), the far-right Vox and the Catalan pro-independence party Junts opposed them.

The PP is currently ahead of Sánchez’s Spanish Socialist Workers’ Party (PSOE) in the polls, while support for Vox has also been rising. If those numbers translate into parliamentary seats, the PP could need Vox’s support to form a government, potentially bringing the far-right party into national government for the first time since the end of Franco’s dictatorship.

For the right-wing media, however, the result is apparently already written.

‘European Left on verge of collapse’

No sooner had the election been announced than the knives were out.

The Telegraph splashed: “European Left on verge of collapse as Spain’s Pedro Sanchez calls snap election.”

Its article presents Sánchez as an increasingly isolated figure on the European Left, highlighting his criticism of Israel’s war in Gaza, his migration policies and his confrontations with Donald Trump over the war in Iran and Nato defence spending.

It also notes Sánchez’s emergence as a prominent figure on the European Left, including how Andy Burnham sought him out at the UN General Assembly in New York, where the two leaders strolled through Central Park.

The piece points to Sánchez’s political survival after previous electoral setbacks, but argues that, this time, the stakes are higher.

“If Mr Sanchez’s gamble backfires this time,” it writes, “the already small number of centre-Left leaders in Europe will be reduced to Mr Burnham, Denmark’s Mette Frederiksen and Malta’s Robert Abela.”

And should the PP and Vox prevail, the Telegraph predicts it would “build momentum behind Europe’s insurgent populist parties”.

The piece looks ahead to elections in France, Italy and Poland, arguing that victories for Marine Le Pen, Giorgia Meloni and Poland’s Law and Justice party would see the EU “swing further to the Right and the Left further diminished”.

The Spectator declares victory before the votes are counted

The Spectator is similarly confident.

Its headline declares: “Sánchez is heading for defeat in Spain’s snap election.”

The right-wing magazine argues Spain now faces the prospect of a “markedly more right-wing government, dependent on Vox’s support”.

It highlights Vox’s calls for “national priority” in access to social housing and benefits, deportation of people living in Spain illegally, and the deportation of legal immigrants who commit crimes.

The article concludes that Sánchez is relying on voters’ fear of bringing a party he describes as “far right” into government overcoming dissatisfaction with his own record.

“On present evidence,” it says, “that looks a forlorn hope.”

There are, of course, serious reasons why Sánchez faces a difficult election.

His minority government has struggled to pass legislation, and his administration has been hit by political and corruption controversies. Social and housing tensions are high following the Ceuta incident with 80,000 migrants from Morocco and rising rents and evictions fuelling large demonstrations across the country.

But there is an important detail that rather gets lost amid the right-wing media’s celebrations.

The election has not happened yet.

Sánchez is undoubtedly taking a political gamble. But the immediate trigger for the election was a housing crisis that has generated huge public anger, and which the right-wing parties themselves helped prevent his government from addressing through the proposed emergency measures.

Sánchez has explicitly framed the election as a choice about whether Spain can continue pursuing progressive policies and secure a broader parliamentary majority capable of delivering reforms on inequality, public services and housing.

The Telegraph and Spectator may have already written Sánchez’s political obituary but on November 29, Spanish voters, not the right-wing press, will decide whether it was premature.

The post Right-Wing Media Watch: The right-wing press has already written Sánchez’s political obituary appeared first on Left Foot Forward: Leading the UK's progressive debate.

Isabel Oakeshott’s Arabic lesson comes with a hefty dose of double standards

Isabel Oakeshott recently took to the pages of the Telegraph to proudly announce that she is learning Arabic.

“I’m a foreigner in someone else’s country. It’s only polite that I’m learning Arabic,” was her headline, followed by the pre-header:

“Britons who move overseas should not treat places like Dubai as English-speaking platforms for sunshine and low tax.”

The right-wing journalist and partner of Reform UK deputy Richard Tice begins by explaining that she has lived in Dubai for two years, where she has perfected the art of speaking English in a variety of accents, reflecting the city’s population of “about 200 nationalities.”

“Day to day, Dubai conspires with remarkable efficiency to protect its huge expat population from speaking the official language: Arabic,” she writes.

In other words, Dubai’s knowledge of English is why she hasn’t mastered Arabic but “it seems only right to make an effort in their language.”

And there, of course, is the real point of the article.

Oakeshott is not merely documenting her own linguistic struggles. She is drawing a comparison with immigrants in Britain, and she barely bothers to disguise it.

“Nonetheless, there is a principle at stake when living in someone else’s country – one I am always going on about in relation to immigrants to Britain.”

So far, so predictable.

But rather than simply making the case for learning the language of the country in which you live, Oakeshott spends much of the article taking a swipe at Arabic itself.

Its letters, she complains, “resemble a toddler’s random dots and squiggles,” while its numerals “might as well be hieroglyphics.”

“As for pronunciation, getting it right seems to require the kind of guttural noises an Englishwoman would ordinarily reserve for dislodging a fishbone,” she adds.

She then informs readers of her respectable GCSE grades in two foreign languages and explains that she should have learned Arabic long ago, before admitting that her previous attempts had ended in failure.

While there is of course nothing wrong with admitting that learning another language is difficult, or encouraging people who move abroad to make an effort to communicate in the local language, there is an extraordinary double standard with Oakeshott’s piece.

Oakeshott has chosen to live in Dubai, where she acknowledges that English is widely spoken and that she can comfortably navigate daily life without Arabic. Yet she presents her belated attempt to learn the language as evidence of a moral principle that she routinely invokes when discussing immigrants to Britain.

And while making that point, she cannot resist ridiculing the very language she is supposedly making an effort to respect.

There is also an important fact conspicuously absent from her argument: the overwhelming majority of migrants in Britain do speak English.

Figures from the University of Oxford Migration Observatory show that in 2021, 90%, around nine million, of immigrants living in England and Wales reported that they could speak English without difficulty. Just over half spoke English as their main language, while a further 38% had another main language but spoke English well or very well. Only 1% said they could not speak English at all.

That reality rather complicates the familiar right-wing narrative of immigrants supposedly refusing to learn English.

Oakeshott’s argument might have carried considerably more weight if she had simply reflected on the challenges of learning Arabic as an English speaker and acknowledged the effort involved in adapting to life in another country.

Instead, she manages to turn her own difficulty into a lecture about immigrants, while simultaneously mocking the language she claims to be learning.

Unsurprisingly, the contradiction did not go unnoticed.

Truth Against Hate pointed out the absurdity of moving to an Arab country, waiting two years to learn the language and then describing its alphabet as “a toddler’s random dots and squiggles” and its pronunciation as “guttural noises.”

The campaign group also noted another parallel.

“Imagine an immigrant to Britain writing an article about finally bothering to learn English, while mocking the language and congratulating themselves for making the effort. The Telegraph comments section would spontaneously combust.

“Arabic has been written, studied and used to produce extraordinary works of literature, philosophy, mathematics and science for centuries. It doesn’t become primitive because Isabel Oakeshott finds it difficult.”

Another commenter joked: “I assume she’s learned the Arabic for ‘tax avoider’, then.”

The post Isabel Oakeshott’s Arabic lesson comes with a hefty dose of double standards appeared first on Left Foot Forward: Leading the UK's progressive debate.

Curiouser and curiouser. A year’s update on the Curious Edinburgh project

It’s been a year (and two months) since I started to migrate Curious Edinburgh, and the newborn website is live!

To re-introduce, Curious Edinburgh is an open access platform which houses digital tours of Edinburgh and the Lothians. The tours are broken down into Community, Coastal and tours on the History of Science, Technology and Medicine. All 26 of them, long and short, highlight a particular dimension of Edinburgh’s cultural and scientific heritage. Users can walk the tours physically, using Curious Edinburgh as their guide, or virtually. 

Here’s an overview of how Curious Edinburgh migration progressed throughout this time and the discoveries I’ve made along the way.

What changed

My assignment was to migrate CE tours from WordPress to ArcGIS StoryMaps. As with any digital migration, I sought to improve content and functionality – not simply transfer them. I particularly focused on upgrading the project’s digital accessibility and user experience. On top of designing a new layout for the webpages, I incorporated interactive maps into each tour. They follow along with the text, situating the user geographically, and allow for easier navigation. All tour points are also assembled into interactive Maps of Contents at the head of each tour. Maps apart, I smoothed the creases and filled in the gaps: proofread every line, sourced new images, replaced or enhanced sources, created feedback sections, and wrote alt text to each image, video, map and embed. Besides accessibility, this has enhanced CE’s cohesiveness and visual appeal. 

Excitingly, just as I was wrapping up migration in early June, Curious Edinburgh received a request from the Consulate General of the US in Edinburgh to host a new tour. The tour would celebrate the 250 years since the Declaration of Independence was signed and the United States founded in 1776. 

This task marked a change of pace, giving me an opportunity to create a tour directly on StoryMaps. I was happy to be more actively involved with the content planning side of CE. In a back-and-forth with the Consulate, we’ve outlined the tour’s contents. The stop order in particular took careful arranging, since the trail spans the architectural heritage of Old Town, New Town and Leith. By 4 July 2026, we delivered a new publicly available tour, the USA 250 Anniversary Trail. It highlights the diplomatic, intellectual and labour connections between Edinburgh and the United States.

Rapid-fire stats 

Tours on CE: 26

Tours migrated: 25

Tours created: 1

Best tour (highly subjective): Granton, all the Coastal tours, History of Public Health

Maps created: 422 

ArcGIS products used: 4 (and more by the EDINA team, who created the landing website of the new platform).

Content highlights

Out of all trails, the tour around Granton was the largest and most daunting to migrate. Granton is one of Edinburgh’s northern waterfront districts – less visited than Leith, less gentrified than Newhaven. It has many new apartment buildings and a B&M home store. What could there be to see?

That’s what I thought, too. 

Turns out, Granton is a remarkable hub of Scottish industrial heritage. From quarries to street art, this tour takes the reader through centuries of history and modern-day change. Besides, the tour is assembled by Grantonians themselves, narrated with warmth and illustrated by archival images and local artwork. I migrated it with great pleasure, if gritting my teeth at 100-something images that needed fresh alt text. 

History evidently doesn’t discriminate – it happens everywhere. Yet, if you ask an Edinburgh resident ‘Have you ever been to Granton?’ chances are they will say no and maybe follow up with ‘Is that in Fife?’

Maybe the Granton tour will make amends. 

 

Impressionist painting showing a large, circular, metal framework of a gasholder visible behind a lush, overgrown line of red, pink and yellow flowers and greenery

Gasworks by Harry Mafuji depict the Granton Gas Holder

 

People highlights 

Luckily I have crossed paths with many new people during my internship. I would like to highlight two things.

The first one happened when I reached out to an independent Edinburgh tour guide, asking to reuse his photo for the History of Public Health tour. I expected a ‘no’ or a ‘sure’. What I didn’t expect was an enthusiastic response which acknowledged the significance of CE for Edinburgh’s heritage and tourism experts. I got my copyright permission and positive feedback to boot. It’s nice to be working on something people actually use.

My second highlight is last summer’s cohort of interns, many of whom returned to LTW this summer. Apart from being great company, they were also the first test subjects for my working webpage designs. Throughout last summer, upon my request, they submitted ingenious test comments for the tours (through Survey123), so that I could create initial data sets for setting up feedback moderation (in Experience Builder). In fact, these test comments were so creative that one of the CE team members asked me, very apprehensively, if we had accidentally catapulted the webpages into public access.

 

Data table with three columns, 'Leave a comment', 'Your name', and 'Moderated', populated with test comments and moderated 'No'

Data table chaos on a feature layer of the History of Witchcraft comment section

 

What’s next for Curious Edinburgh?

As the migration breathes new life into the project, Curious Edinburgh remains a living database for the Scottish capital’s past and present. A tour on the history of AI, currently in the works, should make a good addition to its history of technology section. I am also hopeful that soon CE users will be able to explore Edinburgh’s volcano more closely as a tour on Arthur’s Seat geology is integrated into the project. Finally, as 2026 marks the 300th anniversary of the Edinburgh Medical School, CE stays an excellent place to explore the history of the city’s healthcare sector.

Parts of the migration process were out of my scope, but could be tackled in the future. Here is just a glimpse of them. Digital sustainability: compared to the WordPress version, many webpages have increased in weight (mainly from heavy scripts). Mobile-friendliness: CE has an app which was not migrated/renovated, which leaves the question of a truly mobile-adapted Curious Edinburgh in the air. And a user-friendly mobile version is quite important for a walking guide. Digital preservation: how should the WordPress version be managed and maintained?

Waving goodbye

With the handover documentation completed, editing access transferred, and the latest tour completed, it is time for me to wave goodbye to a year’s work and ISG, and move on with a new project. We’ll see what that’ll be. (Exciting.) 

There is a lot of knowledge to be gained from Curious Edinburgh, and more still from its creators and contributors. I’m certainly grateful for the opportunity to find out.

You can pay Curious Edinburgh a visit here.

 

Beige caption on dark teal background reading 'Comments' above a white text book, which is a comment submitted by an Anonymous Rock saying that they and their wife have loved learning about Edinburgh's geology (apart from conglomerates)

A test comment on the History of Geology tour

 

Curious links

My first month as a Web Content Intern

By: evincent
1 July 2026 at 09:42

Hi! I’m Elisa, a Web Content Intern this summer at the Information Services Group (ISG). I realise this isn’t the most descriptive of job titles; my work mostly consists of rebuilding content that was migrated from our old website platform, EdWeb1, to the new platform, EdWeb2.  

Today marks the completion of my first month at ISG. To be honest, the first few days on the job were slightly intimidating. Updating websites that people actually visit on such a large domain can feel like a lot of pressure. Something as small as switching a simple toggle could have a big impact, and at the beginning, I was nervous I’d make some horrible mistake. I also don’t have a computer science background at all, unlike most of my team, so when they were showing each other the websites they had built and discussing their favourite programming language, I definitely felt like a fish out of water.  

Once we actually started working on the rebuilds, I realised there was no need to be nervous. EdWeb2 is a pretty intuitive platform to use, and my supervisors and line manager have patiently answered the thousands of questions I bombard them with every day. As I had used EdWeb2 at a previous internship at the University, it was more so a matter of jogging my memory and getting reaccustomed to how the system works. 

So, what does rebuilding sites actually consist of? To be truthful, it’s a lot of copying and pasting content from the old system into the new system, and building out what had previously been chunks of HTML into items like feature boxes, accordions, and body text. Everything you see when you visit a university website – all the buttons and links you click, every accordion you expand – has to be built out in EdWeb2. We also liaise with the sites’ lead publishers if we run into any issues. For example, some of the formatting that had been built out in EdWeb1 can’t be replicated in EdWeb2. In this case, we’ll suggest new ways of formatting page content, while still keeping in mind functionality and accessibility.  

I’ve also had the chance to do more in ISG alongside my role. My first week, I attended a training day for Drupal, a software used to build websites. This was quite outside my comfort zone, and the installation itself was really tricky (I do not do well with coding) but in the end, it ended up providing some useful insight into the website building process, and I felt pretty accomplished looking at my (very amateur-looking) website at the end of the session. I’ve also volunteered to help organise the blog you’re reading right now! We’ve been brainstorming ways to make it more engaging and accessible, as well as working on making sure all the interns are aware of the blog and know how they can contribute.  

I’m looking forward to the rest of my time at ISG and contributing to ensuring the university’s websites are running smoothly and efficiently.  

Revealed: Morocco forcibly displaced Black migrants ahead of AFCON tournament

Revealed: Morocco forcibly displaced Black migrants ahead of AFCON tournament

Who won the 2025 African Cup of Nations depends on who you ask. On the pitch, Senegal. On paper, Morocco – the football tournament’s host. But beyond the disputed result, AFCON has revealed a story of how a host country managed its image – and who it pushed out of sight to do so.

Late last year, Morocco forcibly displaced hundreds of Black migrants as it prepared to welcome more than 600,000 tourists for AFCON. While such operations are not uncommon in the country, the Moroccan Human Rights Association (AMDH) told openDemocracy that there was a significant spike ahead of the tournament.

Displacements often “intensify” when the world’s eyes are on Morocco for international sports tournaments, diplomatic summits, or big cultural festivals, according to AMDH president Souad Brahma.

Moving WordPress to a New Domain: A Step-by-Step Guide Without Breaking Links

31 July 2025 at 19:36

Relocating a WordPress website to a new domain is a frequent task for developers, but it often comes with the risk of broken links and lost content. Ensuring a seamless transition where every URL, image, and internal reference correctly points to your new domain is critical for user experience and SEO.

In this article, we outline the steps required to move your WordPress site to a new domain without breaking links. We will primarily utilize WP Migrate Lite for the core migration process, demonstrating precise database and file handling. We’ll also explore how WP Migrate can further streamline and accelerate these domain transfer workflows.

Understanding the Domain Migration Challenge: Why Links Break

Moving a WordPress website to a new domain often results in broken links. This happens because WordPress stores absolute URLs and file paths directly within its database. It doesn’t rely solely on relative paths.

A WordPress site’s primary address is stored in the siteurl and home options within the wp_options table. However, beyond these obvious locations, your old domain’s URL is embedded in countless other places:

  • Within the content of your posts and pages in the wp_posts table.
  • In custom fields managed by plugins or themes (often in wp_postmeta).
  • In widget settings, navigation menus, and various plugin configurations, which are frequently stored as complex, serialized data within the wp_options table or custom tables.
  • Direct links to media files, which also contain the domain name.

The challenge with this deep embedding, particularly with serialized data, is that a simple text-based search and replace on a raw SQL file can corrupt these complex data structures. If the length of the string changes during a simple replacement, it can break the serialization, rendering menus, widgets, and many plugin settings nonfunctional. The solution is to use a tool that can intelligently find and replace these URLs and paths while preserving data integrity.

Pre-Migration Checklist: Preparing for a Smooth Transition

A successful WordPress domain migration relies heavily on thorough preparation. Taking the time to complete a few key steps before you begin the transfer process can save you from significant headaches, unexpected downtime, and data loss. This checklist ensures your source site is ready for export and your destination environment is prepared to receive the data.

Full Backup: Your Essential Safety Net

Before making any changes to your live site, the single most critical step is to create a complete and verified backup of your entire WordPress installation. This includes both your database and all your website files (themes, plugins, media uploads, and core WordPress files). This backup serves as your absolute failsafe. If anything goes wrong during the migration, you can revert to the original state of your site without permanent data loss. Store this backup securely in an off-site location, not on the same server.

Update Everything

Outdated WordPress core files, themes, or plugins can introduce compatibility issues or unexpected behavior during a migration. Before you begin the export, ensure that all components of your source WordPress site are updated to their latest stable versions. This minimizes the chances of encountering errors related to old code when the site is transferred to a new environment.

Clean Up Your Site

To reduce the size of your migration package and streamline the transfer process, it’s beneficial to perform a site cleanup. This involves:

  • Deleting unused themes and plugins: Remove any themes or plugins that are no longer active or necessary.
  • Removing old media: Consider deleting any unused images or media files from your Media Library that are no longer relevant to your site.
  • Cleaning your database: Utilize a database optimization plugin or manually clear old post revisions, spam comments, and transient options. A smaller, cleaner database will export and import faster.

Prepare Your New Domain and Hosting Environment

Before initiating any export from your old site, ensure your new destination is ready.

Make sure the new domain name is registered and accessible and have your new hosting account provisioned and ready. It is generally recommended to start with a completely fresh, default WordPress installation on your new domain. This provides a clean slate to import your old site’s data and files into. You’ll replace its database and wp-content folder with your old site’s data.

Step-by-Step: Moving Your Site with WP Migrate Lite

This section looks at the steps required to export your site’s database and files from your old domain and successfully import them onto your new one, ensuring all internal links are correctly updated.

WP Migrate Lite offers a Full Site export option that bundles both your database and files, but in this case we’re going to export the database and files separately. For a domain migration, this approach emphasizes the critical URL replacement within the database, provides greater control over each component for precise execution, simplifies troubleshooting if issues arise, and can make managing larger site transfers more efficient than a single, massive archive.

Install WP Migrate Lite on Your Old Domain’s WordPress Site

First, ensure the WP Migrate Lite plugin is installed and activated on the WordPress installation running on your old domain. You’ll find it by navigating to Tools .> WP Migrate in your WordPress admin sidebar.

Export Your Database with Domain Replacement

This is the most critical part of a domain migration, as it handles the updating of all old URLs to the new ones directly within your database. WP Migrate Lite’s intelligent Find and Replace feature is essential here.

From your old domain’s WordPress admin, access WP Migrate Lite’s main interface, select the Migrate tab, and then click Export

The Migrate tab in WP Migrate Lite, showing various options including "Export."

The “Database” checkbox should be checked by default. Next, click Tables, and ensure that the radio button “Export all tables with prefix “wp_”” is selected. This ensures every piece of data stored in the database is included, including site options, post content, and plugin settings.

Selecting database tables to migrate in WP Migrate Lite.

The next step is to configure a “Standard Find & Replace.” The “Find” field should be automatically pre-filled with your current (i.e., old) domain’s URL. In the “Replace” field, carefully enter the full URL of your new domain, ensuring you include the correct protocol (http or https).

WP Migrate Lite will intelligently handle serialized data within your database during this process, which is crucial for preventing data corruption that a simple text search-and-replace often causes.

You can also set a different path for your new domain. This isn’t necessary in most cases, as WP Migrate Lite will automatically set up the new path for you.

Once configured, click the Export button. WP Migrate Lite will process your database, perform the replacements, and generate a SQL file containing your database.

Running a find and replace in WP Migrate Lite.

Export Your WordPress Files

After exporting your database, the next step is to export all the necessary files from your old WordPress installation. This includes your themes, plugins, media uploads, and potentially other custom files or WordPress core itself.

Click on the Migrate tab and then select Export again. The “Database” section will be checked by default. Since you’ve already exported and handled your database in the previous step, the first action here is to uncheck the Database box.

Next, we’ll configure the file exports from the remaining sections.

Media Uploads

This section handles the files within your wp-content/uploads folder. Check the Media Uploads box. A dropdown will then appear offering three options for how to export these files. For a full domain migration where you want all your media to be on the new site, you should select “Export all media uploads”. This option ensures all files from your uploads folder are copied. The other options, “Export new and updated media uploads” and “Export media uploads by date,” are generally more suited for partial content syncs rather than a complete domain transfer.

Themes

This section allows you to export your theme files located in wp-content/themes. Check the Themes box. The accompanying dropdown provides several choices. For a complete domain migration, select Export all themes to ensure every theme from your old site is included. Other options like “Export only active themes” or “Export only selected themes” are available if you have specific needs.

Plugins

Similar to themes, this section manages the export of your plugin files from wp-content/plugins. Check the Plugins box. From the dropdown, select Export all plugins to include all plugins from your old site in the migration package. This section offers the same options as “Themes”, but for plugins.

Other Files

The “Other Files” section is for selecting any additional files or folders found directly within your wp-content directory that are not covered by the “Media Uploads,” “Themes,” or “Plugins” sections. Check the Other Files box. A checklist will then appear, allowing you to manually select individual files or folders you wish to include. These might be custom configurations, uploads outside the standard directory, or other specific assets. None are selected by default, so you must carefully choose any you need.

Each of the “Media Uploads,” “Themes,” “Plugins,” and “Other Files” sections also provides an advanced option to use gitignore patterns to exclude specific files relative to their respective directories. This is useful for highly customized exports where certain files (like cache files or development-specific assets) should not be migrated.

WordPress Core Files

The “WordPress Core Files” section addresses the core WordPress installation itself. Check the “WordPress Core Files” box. Including WordPress core files ensures that the exported archive contains the exact version of WordPress installed on your site, which is particularly helpful when replicating the site precisely in a new environment. This option includes the wp-admin and wp-includes directories, along with various root WordPress files such as index.php, license.txt, readme.html, and crucial configuration files like wp-config.php and wp-config-sample.php.

Once all your desired file sections are configured, click the “Export” button. WP Migrate Lite will package your selected files into a single ZIP archive.

.

Prepare Your New Domain’s WordPress Installation

Before importing your old site’s content, you need a fresh WordPress installation on your new domain to serve as the destination. Ensure your new domain name is pointed to your new hosting environment’s server, and then set up a completely fresh, default WordPress installation on your new domain.

Once the new WordPress site is accessible via your new domain, log in to its admin dashboard and delete any default content (e.g., “Hello world!” post, sample page, sample comment) to provide a cleaner slate for your imported data.

Manually Import the Database to Your New Domain

Now you will replace the fresh WordPress installation’s database on your new domain with the one you exported and modified from your old site.

Access your new domain’s database, typically through a tool like phpMyAdmin via your hosting control panel, or a command-line interface (CLI) if you have SSH access.

If using phpMyAdmin, select the database associated with your new WordPress installation from the left sidebar. Click on the Structure tab. Scroll to the bottom of the list and click the checkbox labeled Check all. From the “With selected:” dropdown menu, choose “Drop”. You will receive a confirmation prompt asking if you truly want to execute the DROP TABLE query. Confirm the action. This step is crucial as it clears out the default WordPress tables to make way for your imported data.

Next, go to the Import tab. Click Choose File and select the SQL file you exported with WP Migrate Lite. Ensure the character set and other options are correct (usually the default is fine). Click Import to begin the import.

If using WP-CLI, SSH into your new hosting environment and navigate to your new WordPress installation’s root directory. Ensure your wp-config.php file has the correct database credentials for the new database. Then, run the command: wp db import /path/to/your/downloaded/database.sql (remember to replace /path/to/your/downloaded/database.sql with the actual path to your SQL file, which you’d need to upload via SFTP first). This command will automatically drop existing tables and import your new data.

Manually Transfer Files to Your New Domain

With the database imported, the final step for WP Migrate Lite is to transfer your themes, plugins, and media files to the new domain.

Extract the contents of the ZIP file you downloaded from WP Migrate Lite. This will give you a “wp-content” folder and potentially other root WordPress files. Using an FTP or SFTP client, connect to your new hosting environment and navigate to the root directory of your new WordPress installation.

Upload the wp-content folder from your extracted ZIP file to your new WordPress installation’s root. When prompted, instruct your FTP/SFTP client to overwrite any existing files and folders within wp-content. This will replace the default themes, plugins, and empty uploads folder with those from your old site.

If your old site had custom .htaccess rules, a robots.txt file, or specific modifications to wp-config.php (beyond database credentials), you may need to transfer these files individually from your extracted ZIP’s root directory to the new site’s root. Exercise extreme caution when transferring or merging wp-config.php, as incorrect details will break your site. It is often safer to manually re-add specific customizations to the new wp-config.php rather than replacing the entire file.

Post-Migration Checks and Final Steps

Even with careful execution, some final checks are essential to ensure your site is fully functional on its new domain.

Log in to the new domain’s WordPress admin and navigate to Settings > Permalinks. Without making any changes to the permalink structure itself, simply scroll to the bottom of the page and click the Save Changes button twice. This action flushes WordPress’s rewrite rules, ensuring all your posts and pages are accessible at their new URLs.

Ensure you clear all caches if you had any caching plugins active on your old site, or if your new hosting uses server-side caching. This prevents the site from serving outdated information or getting stuck in redirect loops.

Finally, thoroughly test your new site. Systematically navigate through it, clicking on various posts, pages, and custom post types, testing all navigation menus, checking all images and media files, submitting forms, and verifying plugin functionalities.

Once you are completely satisfied that your site is working perfectly on the new domain, update your domain’s DNS records to point to your new hosting environment’s server. This is the final step that makes your new domain the primary live address for your website. DNS propagation can take up to 24-48 hours.

If your old domain was previously indexed by search engines and you wish to preserve SEO value, it is highly recommended to set up 301 permanent redirects from every URL on your old domain to its corresponding URL on the new domain. This tells search engines that your content has permanently moved.

Streamlining Domain Migrations with WP Migrate

While WP Migrate Lite provides the necessary tools for a successful manual domain migration, the multi-step process involving file transfers, database imports, and manual configurations can be time-consuming and prone to human error, especially for larger sites or frequent domain changes. WP Migrate directly addresses these challenges, offering a highly streamlined and automated workflow that significantly reduces effort and risk.

One advantage of WP Migrate is its direct push and pull functionality for both databases and files. This feature completely bypasses the need for manual download, upload, and import steps. Instead, you establish a secure, direct connection between your source and destination site. From the source site, you can “push” the entire site directly to the new domain, complete with its database, themes, plugins, and media uploads. WP Migrate handles all the underlying complexities, including intelligently performing the necessary URL and path replacements and correctly dealing with serialized data, all in one coordinated operation. This capability dramatically accelerates the migration process and virtually eliminates the risk of errors associated with manual transfers.

WP Migrate’s WP-CLI integration provides a powerful avenue for automation. This means you can initiate and control domain migrations directly from your command line. For those utilizing version control and continuous integration/continuous delivery (CI/CD) pipelines, this allows domain migration steps to be scripted and integrated into automated deployment processes, enhancing efficiency and reliability across your development ecosystem.

Collectively, these premium features transform a potentially tedious and error-prone domain migration into a fast, reliable, and often automated task. By eliminating manual steps and leveraging intelligent, direct site-to-site communication, WP Migrate significantly reduces both the time commitment and the inherent risks involved in moving your WordPress site to a new domain.

Wrapping Up

Relocating a WordPress website to a new domain doesn’t need to be fraught with broken links or lost content. Ensuring a seamless transition where every URL, image, and internal reference correctly points to your new domain is a matter of using the right processes and tools. A systematic approach allows you to confidently manage your WordPress site’s evolution and ensure it thrives on its new home.

Have you migrated a site to a new domain with WP Migrate or another tool? How was the process? Let us know in the comments!

The post Moving WordPress to a New Domain: A Step-by-Step Guide Without Breaking Links appeared first on Delicious Brains.

The Power of Partial Migrations: Syncing Only What You Need

24 July 2025 at 21:32

Managing WordPress sites across different environments often requires moving data and files. A partial migration involves selectively transferring only specific components of your WordPress installation. Instead of cloning an entire site, you might move just new database entries, an updated theme, or recently added media.

In this article, we look at the intricacies of partial migrations and explore practical scenarios where syncing only what you need can save significant time, prevent workflow disruptions, and streamline deployments.

What Are Partial Migrations?

The traditional approach of moving an entire website, a “full site migration,” involves copying every file and database entry. While necessary for initial deployments or major overhauls, this method can be inefficient and risky for ongoing development.

This is where partial migrations become essential. Instead of an all-encompassing transfer, a partial migration is the selective movement of specific components. This might involve targeting individual database tables, such as the wp_posts table to deploy new articles, or moving only new media uploads, an updated theme, or a single plugin.

The benefits of this granular approach are substantial. First, limiting the scope of the transfer reduces data volume, which translates to faster operations and less server load. Second, partial migrations minimize the risk of inadvertently overwriting critical data or configurations that may have diverged between your environments. This prevents unwanted regressions and simplifies troubleshooting. Finally, it enables truly targeted updates, allowing you to deploy isolated changes confidently, knowing you are only affecting the intended components of your site.

How to Perform Partial Migrations

WP Migrate Lite provides a straightforward interface for executing granular exports. While the subsequent import or file transfer steps are manual, the plugin significantly simplifies the data extraction process. Here, we’ll walk through common partial migration scenarios, detailing how to configure WP Migrate Lite for each.

To begin, ensure WP Migrate Lite is installed and activated on your source WordPress site, and then navigate to Tools > WP Migrate.

Scenario 1: Syncing New Content

This scenario is common when new articles, landing pages, or product entries are developed on a staging site and need to be published to a live production environment without affecting other data.

Navigate to the Export Tab

In your source site’s WordPress admin, access WP Migrate Lite’s interface. From there, select the Migrate tab and then click Export.

The Migrate tab in WP Migrate Lite, showing various options including "Export."

Configure the Export

WP Migrate defaults to a database export, without exporting WordPress core, media files, etc. Leave the “Database” checkbox checked, and then click the Tables dropdown.

In the Tables section, click Export only selected tables below, and then carefully select only the tables relevant to your content. At a minimum, this includes wp_posts (assuming wp_ is your table prefix). If your content utilizes custom fields, you should also select wp_postmeta. For new content involving categories or tags, ensure wp_terms, wp_term_relationships, and wp_term_taxonomy are also chosen. It is important to avoid tables like wp_users, wp_options (unless specific modifications are intended), or unrelated plugin tables to prevent unintended overwrites.

Configure Find and Replace

A crucial step for maintaining correct internal links and asset paths is configuring a Standard Find & Replace function. The “Find” fields should already contain the relevant URL and file paths of your source site. In the “Replace” field, input the URL of your destination site. This ensures internal links or embedded media URLs within your exported content are accurately updated for the live environment, with WP Migrate Lite intelligently handling serialized data.

Once all configurations are set, click Export. WP Migrate Lite will then process the selected tables, execute the find and replace operations, and generate a SQL file.

WP Migrate Lite's Find & Replace function.

Manual Import

After downloading the generated SQL file, the next step is manual import. You will need to access your destination site’s database using a tool such as phpMyAdmin or through a command-line interface like WP-CLI. Import the SQL file into the destination database. Exercise caution if your new content might have conflicting IDs with existing content on the destination site. This method is generally most suitable for importing entirely new content.

Scenario 2: Synchronizing Media Library Additions

When new images, videos, or documents are uploaded to a development or staging environment and need to be moved to production, you can transfer only the new files and their associated database entries.

In your source site’s WP Migrate Lite interface, navigate to the Migrate tab and click Export.

Select Media Files Only

Select Media Uploads. This instructs the plugin to include only the contents of your wp-content/uploads directory in the export package. Within the “Media Uploads” options, you’ll be presented with choices for which files to copy. For synchronizing additions, you will typically choose Export new and updated media uploads. This option intelligently identifies and includes only those media files that have been added or modified since your last sync.

Alternatively, if you need to transfer media uploaded after a specific point in time, you could select Export media uploads by date and provide the exact date. This instructs the plugin to include only the contents of your wp-content/uploads directory in the export package based on your selection.

Configuring media exports in WP Migrate Lite.

Configure Database for Media

In the Database section, choose Export only selected tables below. Media items also have corresponding entries in the database. In the “Post Types” subsection, select Export only post types selected below, and then choose attachment from the list. This ensures that only the database entries specifically related to your media library items (found within wp_posts and wp_postmeta) are exported. You will also want to ensure wp_posts and wp_postmeta tables are selected under the “Tables” section.

Configure Find and Replace

As with content, set up Find and Replace rules to update URLs from your source site to your destination site (e.g., https://staging.example.com to https://www.example.com). This step is vital to ensure media URLs are correctly reflected in the database.

Start the Export

Click Export. This action will generate a ZIP file that contains both the selected media uploads and the accompanying SQL database file.

Manual Transfer and Import

Once the export is complete, download the generated ZIP file. Extract the wp-content/uploads folder from this archive. Using an FTP or SFTP client, manually upload only the new or updated media files and folders to the wp-content/uploads directory on your destination server. Exercise care to avoid inadvertently overwriting existing files unless that is your explicit intention.

Concurrently, import the exported SQL file into your destination database using phpMyAdmin or WP-CLI. This dual action ensures the new media items are both physically present and correctly registered within your WordPress Media Library, making them accessible via the admin interface.

Scenario 3: Deploying a Specific Theme or Plugin Update

Deploying a specific theme or plugin update using a partial migration is particularly useful for custom code or when changes involve database updates, ensuring precise deployment without affecting other site components. When you’ve developed or updated a specific theme or plugin and want to push only those changes, a partial file export is the way to go. This avoids deploying an entire site archive when only one component has changed.

Navigate to the Migrate tab and click Export. In the Files section of the export configuration, select Themes or Plugins, depending on which you want to export,. Then, select only the folder of the theme or plugin you wish to export.

You usually don’t have to include the database as part of this export, unless your theme or plugin update specifically entails database changes that have not been managed separately. If database modifications are necessary, you would combine this file transfer with a corresponding selective database export and import process, as outlined in Scenario 1 or 2.

Finally, click the Export button to generate a ZIP file containing only the selected theme or plugin folder, and any database tables you’ve determined are needed.

Manual Transfer

Download the generated ZIP file, and extract the specific theme or plugin directory from within this archive. Then, utilizing an FTP or SFTP client, manually upload this extracted directory to the corresponding wp-content/themes or wp-content/plugins directory on your destination server. This action will typically overwrite the existing folder. It is always prudent to create a backup of the destination theme/plugin before proceeding.

Elevating Partial Migrations with Greater Capabilities

While WP Migrate Lite provides effective tools for granular exports, its capabilities are confined to the source site. The process of integrating those exports into a destination environment consistently requires manual effort. This reliance on manual download, upload, and import steps—whether for database files via phpMyAdmin or file transfers via FTP—quickly becomes a bottleneck for professional workflows.

This manual overhead significantly reduces efficiency for frequent synchronizations, particularly when dealing with large sites or complex data. It also prevents the automation crucial for modern development pipelines and lacks the direct bidirectional syncing needed to pull fresh data from a live site to a development environment. For occasional, simple exports, WP Migrate Lite is functional, but the limitations of manual processes become apparent when speed, automation, and integrated workflows are required.

When the demands of your workflow exceed the manual capabilities of WP Migrate Lite, WP Migrate offers a comprehensive solution. It transforms partial migrations into a direct, automated process, providing granular control and efficiency.

The core enhancement is its direct push and pull feature, allowing seamless, secure database and file transfers between WordPress sites without manual intermediate steps. This includes precise file synchronization, enabling direct transfer of only new or updated media, themes, or plugins through intelligent comparison of source and destination files. For WordPress Multisite networks, it provides specialized tools that simplify complex tasks like exporting individual subsites or migrating them between networks. Command-line interface integration via WP-CLI allows developers to script partial migrations, integrate them into CI/CD pipelines, and automate routine synchronization tasks.

To further streamline recurring operations, migration profiles can be saved, enabling quick, consistent execution of predefined partial migration settings.

Wrapping Up

A partial migration involves selectively transferring only specific components of your WordPress installation. Instead of cloning an entire site, you can now move just new database entries, an updated theme, or recently added media. This strategic approach to moving data and files is key for managing WordPress sites efficiently across different environments.

While partial migrations have their intricacies, there are scenarios where syncing only what you need can save significant time, prevent workflow disruptions, and streamline deployments. WP Migrate saves even more time by automating the steps you need to do manually when using WP Migrate Lite.

The post The Power of Partial Migrations: Syncing Only What You Need appeared first on Delicious Brains.

Merging WordPress Sites: Consolidating Multiple Installs into a Multisite Network

18 July 2025 at 18:46

WordPress Multisite is a powerful tool, highly useful for things like client sites managed by an agency, school or university departments, or large corporate structures where many related sites are needed. However, moving existing standalone sites into that network can be a real headache, with tricky database merges and file juggling.

In this article, we look at two ways to approach this migration: the manual way with a bit of assistance from WP Migrate Lite, and the practically automatic way with WP Migrate.

What is WordPress Multisite?

Multisite is a WordPress feature that allows you to run multiple independent WordPress websites from a single WordPress installation. It allows you to:

  • Manage everything centrally: Handle core updates, themes, and plugins for your entire network from one admin dashboard.
  • Share resources: Themes and plugins can be installed once and activated across multiple sites within the network.
  • Streamline user management: Users can often have accounts across different sites in the network.

Subdomains vs. Subdirectories

A critical choice you’ll make when setting up your multisite network is how the URLs for your individual subsites will be structured.

  • Subdomains: Your subsites will appear as subdomains of your main network domain (e.g., site1.yourdomain.com, site2.yourdomain.com). This often requires your web host to support “wildcard subdomains” and can involve specific DNS configurations.

  • Subdirectories: Your subsites will appear as subfolders of your main network domain (e.g., yourdomain.com/site1, yourdomain.com/site2). This typically relies more on .htaccess rules and is often simpler to set up initially on shared hosting.

This decision is made early in the Multisite setup process and is generally very difficult to change later, so choose wisely based on your hosting capabilities and desired URL structure.

Why Converting to Multisite Can Be Complex

Bringing existing single WordPress sites into the multisite fold isn’t a simple drag-and-drop. The biggest challenges are merging database tables, file organizations, and making sure URLs and serialized strings aren’t broken.

  • Database Structure: Single sites use a straightforward set of database tables (e.g., wp_posts, wp_options). Multisite, however, uses global tables (like wp_users and wp_usermeta for the entire network) alongside site-specific tables, each with a unique prefix (e.g., wp_2_posts, wp_3_options). Merging these correctly without data corruption is the biggest hurdle.
  • File Organization: Media uploads in a single site live in a simple wp-content/uploads/ folder. In a multisite, each subsite gets its own dedicated folder, typically wp-content/uploads/sites/[site_ID]/.
  • URLs and Serialized Data: A single site’s database contains its old URL everywhere. When you move it to a multisite subsite, the URL changes. WordPress also stores complex data (like widget settings, theme options) in a serialized format. A simple find-and-replace on these strings can break them, leading to broken functionality.

Setting Up WordPress Multisite

The first thing you need is a functional WordPress Multisite network. We recommend testing everything on a staging site or in local development before rolling it out to production. Creating a [WordPress Multisite in Local(https://localwp.com/help-docs/advanced/wordpress-multisite-with-local/#Creating-a-new-Multisite-in-Local) is one way to get up and running quickly. Local also integrates with WP Migrate, the tool we’re going to use to transfer our database and files.

Next, create complete backups of all your sites, the single sites you plan to migrate and your fresh WordPress install that will become the multisite network. You never know when you’ll need a backup.

Migrating a Single Site to Multisite the Hard Way

This section outlines the process of converting a single WordPress site into a multisite subsite with a heavy reliance on manual effort. While WP Migrate Lite can help with providing a raw database export, the vast majority of the complex, multisite-specific adjustments will fall squarely on your shoulders.

Preparing the Source Site

Before you begin extracting data, it’s always a good practice to prepare your source site. A clean database will make things slightly less chaotic down the line. We recommend first taking the time to clean up your database by deleting unnecessary data like spam comments, old post revisions, expired transients, and any unused themes or plugins. This can be done directly in your database via a tool like phpMyAdmin or by using a dedicated cleanup plugin.

Once your database is tidied up, you’ll need to export its contents. Install and activate WP Migrate Lite on your single WordPress site, navigate to Tools > WP Migrate, and then click on the Migrate tab. Next, click on Export. From there, you have options to export just the database, or perform a “Full-Site Export” which bundles your database, media uploads, themes, plugins, and other wp-content files into a downloadable ZIP archive.

The Export settings in WP Migrate Lite, allowing you to export the database, the whole site, or any portion thereof.

While WP Migrate Lite does offer a “Find & Replace” feature that can safely handle serialized data for general site moves (e.g., changing http://olddomain.com to http://newdomain.com when moving a single site to a new domain), for this specific Multisite scenario, you’ll ultimately need to access the raw .sql file for intricate manual editing. Whether you export just the database or a full site ZIP, you’ll then proceed to the next, most challenging step.

Manual Database Transformation

This is where the real challenge begins, and where even a single misstep can lead to a completely broken site. You’ll be working directly with the raw SQL file that contains your site’s database, so it’s absolutely crucial to have a fresh backup of that file before you start. For this intricate process, you’ll need a powerful text editor, like VS Code, Sublime Text, or Notepad++, that can handle large files and perform advanced find-and-replace operations.

The first major task involves manually adjusting your database table prefixes. Your single site’s database tables likely started with wp_ (for example, wp_posts, wp_options). In a Multisite environment, each subsite needs a unique prefix, typically wp_[subsite_ID]_ (such as wp_2_posts or wp_3_options). You must go into your database’s .sql file and meticulously perform a global find-and-replace for every instance of your old table prefix, replacing it with the new subsite’s prefix.

Now, here’s the huge, critical risk: while WP Migrate Lite’s built-in find-and-replace can handle serialized data safely when you’re just changing URLs within a single site context, it is not designed to automatically adapt serialized data for the complex table prefix changes required when moving a single site into a multisite subsite. WordPress stores complex data, like widget settings, plugin options, and various array data, in a serialized format. If you perform a simple text replacement on a serialized string that changes its length, you will corrupt that data. This often results in broken widgets, non-functional plugins, and missing settings on your new subsite, as standard text editors don’t understand the intricacies of serialized data lengths.

Following the prefix changes, you’ll face a similar challenge with URLs and paths. Your exported database is littered with references to your old single site’s URL. You’ll need to perform another series of global find-and-replace operations to update all these instances to reflect your new subsite’s URL (like http://multisite.com/subsite1 or http://subsite1.multisite.com). Be sure your target URL matches your multisite’s chosen structure, whether it’s http://multisite.com/subsite1 for subdirectories or http://subsite1.multisite.com for subdomains.

Once more, the danger of corrupting serialized data that contains these URLs looms large if you’re not using a specialized tool designed for these complex, length-sensitive replacements across various database structures within a multisite context.

Next comes the particularly thorny issue of user data merging. Multisite utilizes global wp_users and wp_usermeta tables, meaning all users across the entire network share these two tables. Your single site, of course, has its own dedicated wp_users and wp_usermeta tables. You absolutely cannot just import these directly.

Instead, you’ll need to carefully export only the user tables from your single site. Then, you must manually review them. If any user IDs from your single site conflict with existing user IDs on your multisite network, you’ll have to manually reassign new, unique IDs to the single site’s users within their wp_users and wp_usermeta rows. After that, these modified user rows must be meticulously merged into the Multisite’s global wp_users and wp_usermeta tables.

Finally, and this is a step that often requires writing complex custom SQL queries, you’ll need to update the post_author fields in your newly prefixed wp_X_posts table to ensure they correctly reference the new user IDs in the Multisite’s global wp_users table. Beyond these major structural changes, you might also find yourself manually adjusting site_id values in certain option tables to ensure everything correctly points to the new subsite.

Importing the Modified Database

Once you’ve painstakingly edited your SQL file, and double-checked (and triple-checked!) your work, it’s time to import it. It’s important to note that WP Migrate Lite does not provide an in-dashboard import feature for arbitrary SQL files or full-site ZIP archives back into a live WordPress site; its export is designed to be imported using external tools (or specifically into Local). Therefore, you’ll typically use a database management tool like phpMyAdmin. Log in, select the database associated with your multisite installation, and then use the “Import” function to upload your manually edited SQL file. This is often the moment of truth, where you’ll be hoping no errors appear.

Manual File Transfer and Reorganization

With the database n place, your next major task is to sort out the files. Even if you generated a full-site export ZIP with WP Migrate Lite, the manual database edits mean you’ll likely still be managing files externally.

First, connect to your multisite via FTP/SFTP. Navigate to the wp-content/uploads/ directory. You’ll notice a sites/ folder there, and inside sites/, you’ll find folders named after your subsite IDs (e.g., 2/, 3/). You’ll then take all the media files from your single site’s wp-content/uploads/ folder and manually upload them into the correct subsite’s designated directory (e.g., wp-content/uploads/sites/[subsite_ID]/). Even after moving the files, they might not immediately appear in your subsite’s media library. You might need to activate a specific plugin on the subsite to rescan and register these files in its database.

Beyond media, you’ll also need to manually upload any specific themes or plugins that your old single site used, if they aren’t already available network-wide on your multisite. Once uploaded, you’ll then activate the necessary themes and plugins for your new subsite from its dashboard.

Post-Migration Cleanup and Testing

Even if you’ve done everything perfectly, you need to thoroughly check the newly migrated subsite. Begin by clearing any caching plugins on your multisite, as well as any server-side or CDN caches. After that, go to the new subsite’s dashboard, navigate to Settings > Permalinks, and click Save Changes. This can often help re-write the permalink rules for the subsite and resolve potential routing issues.

Now comes the most critical part: extensive testing. Do not assume everything works just because the site loads. You must systematically visit all pages and posts to check that content displays correctly, images load, and all internal links function. Test any forms present on the site, verify that widgets and customizer settings are as expected, and ensure all plugins are functioning without errors. Crucially, test user logins and permissions on the new subsite, and double-check that all media links are correct and images display properly.

As you can see, performing this migration manually is a monumental undertaking. Even with a tool like WP Migrate Lite assisting with the initial database export and its general serialized data handling, the lack of specific multisite integration means you’re left with immensely complex manual tasks. It demands deep technical expertise, meticulous attention to detail, and a significant time investment for each and every site you plan to migrate. The risk of data corruption, especially with serialized data after table prefix and URL changes, and the complexities of merging user tables, remains extremely high. While it’s technically possible, it’s impractical for most, and certainly not scalable if you have more than one or two sites to migrate.

Simplify Your Life: Migrating a Single Site to Multisite with WP Migrate

This method leverages WP Migrate’s powerful premium features, specifically its “Multisite Tools” addon, to automate the most complex and error-prone aspects of migrating a single site into a multisite network. You’ll quickly see a dramatic reduction in the time, effort, and technical expertise required.

Install WP Migrate

The first thing you’ll need is a “Plus” or “Premier” license for WP Migrate, as these licenses include Multisite Tools.

Once you have your license, install and activate the WP Migrate plugin on both your source single WordPress site and your destination Multisite network. This dual installation allows the plugin to establish a secure connection between the two sites, enabling direct data transfer.

Prepare Your Source Site

Compared to the arduous manual method, source site preparation here is significantly simpler. While a general cleanup (like deleting spam comments or old revisions) is always good practice for a leaner migration, WP Migrate’s robust capabilities mean you don’t need to manually export databases or files. The plugin intelligently handles the find-and-replace for URLs and file paths, safely managing all serialized data without corruption.

Prepare the Destination Multisite

The foundational steps of setting up your WordPress Multisite network are still essential. You’ll need to have your multisite environment properly configured and running. Additionally, just as with the manual method, you’ll need to create a new, empty subsite within your multisite network that will serve as the destination for your incoming single site. This provides WP Migrate with the designated slot to pull your site’s data into.

Perform the Automated Pull Migration

This is where WP Migrate truly shines, automating tasks that were previously hours of painstaking manual labor. From your Multisite Network Admin dashboard:

  1. Navigate to the WP Migrate plugin interface.
  2. Select the “Pull” option. This tells the plugin you want to pull data from a remote site to your current multisite network.
  3. You’ll then be prompted to connect to your remote source site (your original single WordPress installation). Once connected, WP Migrate will intelligently detect your multisite setup.
  4. The plugin will offer you precise options for the migration. You’ll be able to select the specific single site you want to pull from, choose the newly created subsite on your multisite network as the exact destination for this migration, and select which components you wish to migrate: the database, media files, themes, and plugins.
  5. With your selections made, you’ll initiate the migration. WP Migrate then takes over, performing a series of automated, complex tasks. It intelligently handles the find-and-replace for URLs and file paths, safely managing all serialized data without corruption. The plugin also correctly adjusts all database table prefixes from your single site to match the unique prefix of the target subsite (e.g., wp_ becomes wp_2_). It also merges your single site’s user data into the multisite’s global wp_users and wp_usermeta tables, correctly handling user ID assignments and references. Media files directly to the correct subsite-specific wp-content/uploads/sites/[subsite_ID]/ directory, and it even transfers your selected themes and plugins, making them available for activation on your new subsite.
  6. You can monitor the progress of the migration directly within the WP Migrate interface, which provides clear feedback as it processes your data.

Post-Migration Testing is Still Important

Even with the automation provided by WP Migrate, thorough testing remains a critical step. While the likelihood of fundamental errors is drastically reduced, it’s always wise to verify everything works as expected.

  • Clear Caches: As always, clear any caching plugins on your Multisite, along with server-side and CDN caches.
  • Resave Permalinks: Navigate to your new subsite’s dashboard (Settings > Permalinks) and click Save Changes. This helps ensure the permalink structure is correctly refreshed within the multisite environment.
  • Comprehensive Testing: Systematically check all aspects of your newly migrated subsite. Visit all pages and posts, verify images and media links, test forms, ensure widgets and customizer settings are correct, and confirm that all plugins are functioning as intended.

Comparing Methods

The contrast between the two methods is stark. The second way, powered by WP Migrate, transforms a labor-intensive, technically precarious process into a few clicks. What could take hours or even days of manual debugging and highly specialized knowledge is condensed into minutes, with a dramatically lower risk of error and data corruption. This powerful automation means less stress, more reliability, and ultimately, a much more efficient use of your time.

Wrapping Up

We’ve explored two distinct paths for migrating a single WordPress site into a multisite network. On one hand, the meticulous manual approach demands deep technical knowledge and carries a high risk of data corruption. On the other, a specialized tool transforms this complex process into an efficient and reliable operation.

The difference in effort and risk is striking. What could be a multi-day debugging nightmare becomes a matter of a few clicks, drastically reducing your time and stress.

This contrast clearly highlights a choice: tackle an incredibly intricate task with painstaking manual effort, or leverage automation designed to handle its complexities safely. For most, the investment in a solution that provides such efficiency, reliability, and peace of mind is invaluable.

The post Merging WordPress Sites: Consolidating Multiple Installs into a Multisite Network appeared first on Delicious Brains.

❌
❌