Well, if you're only concerned with how to get around this partitioning issue you have, and are sure you won't face performance issues after you move to a single partition, then you could try to collapse all of your partitions into 1, and there's lots of ways to do.
If you feel your system can handle it, you could dump all the data into another table and give it a max ID number to dump into. Then when the bulk of the data is copied into there, you could note the ID, find any new records that came in. If it's a huge amount of records, dump those new records in the new table as well. After the 2nd dump you should be almost caught up. At that point you do not allow new data to come in for a few seconds/minutes while you run pre-scripted out commands to:
-move the remaining data into the new table that doesn't have partitioning enabled after making sure the schemas match.
-rename the old table. Make sure you don't have blocking issues.
-rename the new table to the old table.
You might want to avoid adding indexes at the beginning, and do those at the very end.
If doing this on the live system isn't an option, you could move the data to another system and do all these steps there.
Perhaps you could use this opportunity to archive your old data. You could consider creating a view and have your old data in a different archive read only database and have it referenced with a view.
How much data is it anyways, with and without indexes?
Community Wiki answer compiled from comments to the question†
Jon Seigel:
It isn't possible to restore a database that uses Enterprise edition
features on an instance that doesn't support those features. You'll
have to either remove partitioning and then use backup/restore, or
export/import the data.
Kin
See this answer on another question that shows how to use bcp
out and BULK INSERT in native mode to transfer the data quickly.
†Comments may be deleted and are not searchable.
Best Answer
This is an older question. But Microsoft just gave you a great new answer if you are using SQL Server 2016 and still in Standard.
Partitioning (among many other features like Compression, Columnstore, In-Memory OLTP, Row Level Security, etc.) is available in SQL Server standard.
Probably too late for this question. But not too late for someone finding this question today. SQL Server 2016 Service Pack 1 is where this change was introduced.
You can read more on Microsoft's post about it.